Thread (56 messages) 56 messages, 13 authors, 2004-10-21

Re: [Linux-fbdev-devel] Generic VESA framebuffer driver and Video card BOOT?

From: Helge Hafting <hidden>
Date: 2004-10-18 20:18:30
Also in: lkml

On Mon, Oct 18, 2004 at 02:10:33PM +0200, Gerd Knorr wrote:
On Mon, Oct 18, 2004 at 01:39:29PM +0200, Martin Waitz wrote:
quoted
hi :)
quoted
Whenever writing to the gfx memory before finishing the initialization
is harmless or not probably depends on the hardware, I'd better not
count on it ...
when the application tries to access the framebuffer memory then
the driver is asked to map the corresponding page.
On first access only, and even that only if the driver doesn't map the
pages at mmap() time already.  Not a single fb driver seems to map the
pages lazy today, grepping in drivers/video for nopage handles shows
nothing.  I'm not sure you can actually do that for iomem mappings.
Isn't it possible for the driver to unmap the mapping when
suspending?  Then you're guaranteed to get that first access.

This can be simplified to a all-or-nothing approach, it is not
necessary to fault the pages in individually.

Helge Hafting
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help