Quote:
Originally Posted by Godzil
But maybe they does not use the PVI eInk driver and use their own proprietary driver? and for me its look like it is present. There are a FB driver for eInk but it seems to not be compiled by default on the configurations they provide.
And I don't think the code may need to be compiled inside the kernel, the driver can be in the userland.
|
Sorry, compiling kernels is quite above my head. I know the theory but haven't really done that myself so I can't really see for myself. The information I have about them being in violation of the GPL is a bit dated but I supposed that if something had changed in the meantime that I would have heard about it in the forums here. But if you have first hand experience that everything is there now that's great news!
About the driver: Yes, you are right, it does not have to be in the kernel. That's what dynamically linking is and in that case you don't have to provide your source code as that does not count as a change to the GPLed code. Statically linking, however, is more efficient as your code is directly compiled into the kernel and therefore usually if you are tight on RAM, CPU power, etc. you would rather like to statically link. But unless you plan to release your source code that's a forbidden road :-)