Subject: splash screen stuff as a device driver....
To: Jared D. McNeill <firstname.lastname@example.org>
From: Garrett D'Amore <email@example.com>
Date: 04/06/2006 22:24:44
Right now splash screen is an attribute that must be defined on the
driver (e.g. machfb) to get it included.
it seems like this is better done if it is a "device", and, e.g:
splash0 at machfb0, or even
splash0 at wsdisplay0
The benefit of this is that then I don't have to conditionally decide
device radeonfb: wsemuldisplaydev, videomode, rasops32, vcons, splash
device radeonfb: wsemuldisplaydev, videomode, rasops32, vcons
should be used. Additionally, some of the #ifdef code in things like my
radeonfb could get cleaned up, so that I just format a standard
structure and then pass it to config_found().
This could also move some of the special IOCTL handling out of the
drivers and have them get called in central splash device handling.
What do people think? Am I insane?
Garrett D'Amore, Principal Software Engineer
Tadpole Computer / Computing Technologies Division,
General Dynamics C4 Systems
Phone: 951 325-2134 Fax: 951 325-2191