Quote:
Originally Posted by ManDay
Hm, sounds good. So these e-ink modifications to the kernel, they are a hand-written patch?
|
I think they are additional files. It's a long time since I looked. The source for the modified kernel can be found
in a Github repository.
Quote:
|
What do you mean by the Qt library writes directly to the FB? Is that some userspace driver thing or do you rather mean that the kernel has FB support for the eink (and Qt uses that FB?)
|
As I understand it, the kernel provides a framebuffer device and Qt accesses that to change what is shown on screen. I've also written a simple Python module to do the same thing. The kernel code to handle the e-ink display manages things like updating it correctly. From userspace, libraries and applications are just using a standard framebuffer API.
Marek's version of the kernel can also be found
on Github.
Quote:
|
Any idea about how well written the eink part is (regarding energy efficiency, for example)?
|
I haven't looked very closely at it. I'll do some field testing soon.
Quote:
The way you describe it, it looks like with the according e-ink patch I can have a working kernel with a working FB, which is just perfect (well, perfect would be if Marek could push his patch upsteam  ).
|
Well, he recently replied to
his own thread so maybe he's reading this.