Messages in this thread |  | | | Date | Mon, 18 Oct 2004 22:21:47 +0200 | | Subject | Re: [Linux-fbdev-devel] Generic VESA framebuffer driver and Video card BOOT? | | From | Helge Hafting <> |
| |
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: > > hi :) > > > > > 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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |