How about making a small driver with all of it's code marked __init that
initializes the mode on boxes with absolutely no support? That would be enough
to get us to the point where we can run user mode code and provide a more full
featured driver. The user mode driver would have full support for mode
setting/edid in user space libraries.

That would need proper synchronisation with whatever kernel driver does
command processing (something we +/- lack today as well) since we must
stop it when doing mode switching.

Actually, I much prefer keeping the mode setting driver in the kernel
(like any other OS btw). While the accel stuffs location is debatable
(best option beeing what DRI does imho, that is a kernel module taking
care of sending the command blocks & dealing with irqs, while the actual
constuct of the command blocks goes to userland).

Ben.




-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php