Re: [PATCH 0/3] fb accel capabilities (aka fast radeon fb, the right way)

[Benjamin Herrenschmidt <benh@kernel.crashing.org>]

> Well, we still need a way to know when the fbdev has to reinitialize its accel
> engine, when switching the console from graphics mode (user space does accel)
> to text mode (kernel uses accel). Currently this is done when FB_ACCELF_TEXT is
> set.

Current fbcon should do a set_var with FB_ACTIVATE_FORCE (thus forcing a
call to set_par) when switching from KD_TEXT to KD_GRAPHICS

> BTW, we've been talking about allowing kernel messages (mainly oops and panic)
> to show up under X. Since we cannot use the accel engine for that, perhaps we
> need different routines for fb_{fillrect,copyarea,imageblit}() for the
> accelerated vs. non-accelerated cases? And fbcon could compare the function
> pointers, instead of looking at .hwaccel.
> 
> (Yes, I know it's still possible to lock up your card when using unaccelerated
>  drawing while an accelerated operation is in progress on some cards).

Comparing function pointers ? That's evil ;)

Ben.




-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click