Quote:
Originally Posted by dboddie
The standard stack writes directly to the framebuffer (no X11) using the Qt library. One running program is the display manager and the others are clients. The kernel is a modified version of 2.6.35.3 with support for the e-ink screen.
The stacks produced by members of this forum seem to be based on familiar desktop environments available for Linux distributions, such as Debian, and use X11 as a result.
I based my stack on Debian, too, but also use the Qt library to write directly to the framebuffer, so I'm running a kind of hybrid system. I use a kernel modified by Marek (who also produced a Debian-based image for the Kobo) that improves the level of support for the screen, and which works very well. 
Does that make sense? I can provide links to various resources if you are interested. |
Hm, sounds good. So these e-ink modifications to the kernel, they are a hand-written patch?
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?)
Any idea about how well written the eink part is (regarding energy efficiency, for example)?
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
).
Sure, any links and resources would be greatly appreciated!