Date: Sat, 09 Jan 1999 02:58:44 +0900 From: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp> To: Mike Smith <mike@smith.net.au> Cc: current@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: syscons update - when? Message-ID: <199901081758.CAA18279@zodiac.mech.utsunomiya-u.ac.jp> In-Reply-To: Your message of "Fri, 08 Jan 1999 08:34:31 PST." <199901081634.IAA03132@dingo.cdrom.com> References: <199901081634.IAA03132@dingo.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>> dev/fb/fb.c >> dev/fb/fbreg.c >> dev/fb/splash.c >> dev/fb/splashreg.c >> dev/fb/vgareg.c > >Do we want to go ahead with the splash separate from the screensaver >architecture? I guess it costs us nothing to back it out. The above splash.c file contains glue funcions only. The actual decoder function is implemented in another file, such as modules/splash/bmp/splash_bmp.c. The decoder and the glue functions together will act like a screen saver. The decoder is expected to be preloaded by the boot loader so that the splash screen is put up at very early stage. But, if the decoder module is loaded after the boot procedure is completed, it will act just as another screen saver. >> The new drivers are not yet activated. The users will be still using >> existing syscons at this point. >> >> Stage 1. ------------------------------------------------------ >> >> On Sunday evening, the new keyboard driver will be activated. >... >> The users are REQUIRED to update their kernel configuration files >> to include the new keyboard driver. I will send out "HEADS UP" on >> this. >... >> Stage 2. ------------------------------------------------------ >> >> On 14, the new video card driver (and splash screen) will be >> activated. >... >> The users are REQUIRED to update their kernel configuration files to >> include the new driver, again. I will send out "HEADS UP" on this >> too. > >Is there a good reason not to group these two change sets together? I >realise that they separate neatly, but it would seem from here that you >could probably just group them together and be done with it. What I worried about is that if we do things in one go and a serious bug/flow is found in the new code, we may have to back out everything. So, I wanted a bit of breathing space... Well, what the heck. One "HEADS UP" is simpler and better than two! Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199901081758.CAA18279>