Thread (3 messages) 3 messages, 2 authors, 2006-11-16

Re: [RFC 2.6.18.1 1/1] Framebuffer driver for Hecuba/E-Ink display

From: Jaya Kumar (ஜெயாகுமார்) <hidden>
Date: 2006-11-16 03:49:13

On 11/16/06, Geert Uytterhoeven [off-list ref] wrote:
Yep, sounds like a nice idea to try, and compare with other methods, like e.g.
copying the frame buffer to the external device every vsync.

But I guess the `every vsync' is not a good idea for e-ink, as it's very slow
to update?
Yes, you are right. The typical display update for this particular
display is about 500ms to 800 ms. To clarify, the display is static
(non-volatile pixels basically) and thereby is not refresh associated.

One of the common concerns when using this display is power. This is
where I think the method of only updating the display (and waking up
the controller) when triggered by the page fault may help. Also
differencing is made easier because we would know which pages have
been touched.

Thanks,
jaya

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help