Re: Advice sought on approach.

[Antonino Daplas <adaplas@pol.net>]

On Wed, 2003-03-05 at 22:40, Alex Bennee wrote:
> 
> I think I understand now. When the fb_set_disp function is called I fill
> in the display struction with the console display operations. I've got
> two choices now:
> 
> 1. Create a new fbcon_cfb16 file which notes the changed areas before
> calling the generic function.
> 
> 2. Patch the current fbcon_cfb16 (with a CONFIG option) to add the
> change tracking facility in a more generic way.
> 
> I guess the question is is it worth doing 2 as a potential upstream
> patch? Or is this sort of thing so specialised I should just keep it all
> packed in my own fb driver?
> 

Either do #1 (create your own set -- check the popular drivers which has
acceleration, they have their own set), or you can generically implement
#2, I think.  It may even become useful for devices without mappable
graphics memory.

Or as Geert suggested, just write a console driver if you don't need
GUI.

Tony




-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger 
for complex code. Debugging C/C++ programs can leave you feeling lost and 
disoriented. TotalView can help you find your way. Available on major UNIX 
and Linux platforms. Try it free. www.etnus.com