Re: fbdev upstream

On Tue, 2004-01-06 at 11:51, James Simmons wrote:

quoted

Of course, that means we'll have to update more drivers, and platforms
with fixed display, like embedded etc... will need some way to deal
with that properly in their drivers.

Fixed screen size drivers should provide there own modedb. 

Or just single mode... currently drivers don't export a modedb, they
keep one internally and do the validation... though it would make sense
to expose a modedb to userland, so we can have some nice GUI tools
showing you the available modes :) It would make sense for MacOnLinux
too which currently rely on the user to setup the list of modes
available to MacOS.

quoted

I don't know about that one. It would be interesting to redo some
comparison between XFree CVS "nv" driver and rivafb. I don't have any
nvidia HW at hand for now though. 

The changes have been alot. It would require me reworking the driver 
again.

Heh, been there, done that in 2.4... quite painful indeed. We can
probably first get what we have merged upstream now, and think about
it later...

quoted

Also, we just completely lack proper locking, we should at least take
the console semaphore around all these operations, which we don't do
and thus are racy as hell... the HW cursor and blanking timers are
by definition racy too, we need to fix that some way.

The fbcon system has always lacked locking :-( Now it can be fixed.
k

-- 
Benjamin Herrenschmidt [off-list ref]



-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click