Re: Mapping the framebuffer into kernel space

Started by James Simmons on May 4, 2005

open the first message on its own page

Message details and related content
I don't see a good solution here for implementing fb_read/write for
the framebuffer. I would still vote for removing all kernel
framebuffer mapping from the fbdev driver. Then fbconsole would kernel
map just the piece it needs to implement the console.
I like to see the mappings go away as well. The solution is for fb_read 
and fb_write to use fb_imageblit. We don't need to touch the framebuffer 
memory in that case. The logic is a little tricky. You could have 1 to 3 
images blitted to the display.



-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
Keyboard shortcuts
hback out one level
jnext message in thread / next series-diff position
kprevious message in thread / previous series-diff position
ldrill in
Escclose help / fold thread tree
?toggle this help