View Single Post
Old 02-27-2013, 08:10 AM   #4
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Quote:
Originally Posted by twobob View Post
*scratch head* so... did you simply retro-fit the code that emerged in the later kernels to the DX...

as-in later devices could ALREADY be convinced to do what you are indicating.. ?

Am code diving and attempting to figure out what might be done to convince later device to go monochrome natively...

Anyone???
The code posted by the O.P. certainly looks clean enough, and the user can effectively disable it.

Will have to see how it would all fit into the newer devices e-ink driver before making any additional comment.

@twobob: Just one patch, to one module, does not sound like much of a reason to ask the O.P. to setup a repo for it - - -
Do you want to push it to the */systems repo or shall I give it a public repo on my system ?
I can give the O.P. write access to the repo for it on my system.

@twobob: We need another chat on that */systems tree structure - I think we missed something in our last planning.
knc1 is offline   Reply With Quote