From owner-freebsd-current Fri Jan 8 08:38:03 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA16406 for freebsd-current-outgoing; Fri, 8 Jan 1999 08:38:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles244.castles.com [208.214.165.244]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA16386 for ; Fri, 8 Jan 1999 08:38:01 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id IAA03132; Fri, 8 Jan 1999 08:34:32 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901081634.IAA03132@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Kazutaka YOKOTA cc: current@FreeBSD.ORG Subject: Re: syscons update - when? In-reply-to: Your message of "Fri, 08 Jan 1999 21:34:33 +0900." <199901081234.VAA13287@zodiac.mech.utsunomiya-u.ac.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 08 Jan 1999 08:34:31 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Ok, here is my plan. This all looks pretty good. > Stage 0. ------------------------------------------------------ > > This weekend I will commit the following new files. ... > 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 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. Apart from that: Yay! Go Kazu! -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message