quoted

It's used to indicate that the frame buffer device uses hardware acceleration
for rectangle fill/copy and imageblit.

It must be explicitly disabled before a user space application can mmap the
MMIO registers to do its own hardware acceleration, to avoid accelerator access
conflicts.

I think we should stick to KD_TEXT/KD_GRAPHICS for who owns the engine.

I wouldn't bank on that. I seen this solution fall short. Consider a system 
where we have a serial console, vgacon, and fbcon (say hgafb). Well I 
leave it to the imagination what can go wrong. 
 

I don't think fbdev should expose any "acclerated" API to userland, that
is a hopeless goal and will lead to nothing. We need some arbitration
layer at one point between whatever accel stuff we use (DRI, userland
accel library) and somebody changing mode though. Lots of stuffs I've
tried to figure out and didn't end up with anything reasonable yet, lack
of time doesn't help...

I agree we need arbitration. Eventually fbdev and dri have to merge. Mode 
setting is still best handled kernel side. That is just a reality.






-------------------------------------------------------
This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek
For a limited time only, get FREE Ground shipping on all orders of $35
or more. Hurry up and shop folks, this offer expires April 30th!
http://www.thinkgeek.com/freeshipping/?cpg=12297