From owner-freebsd-arch Wed Jan 22 13:22:22 2003 Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BDC2037B401 for ; Wed, 22 Jan 2003 13:22:20 -0800 (PST) Received: from postfix4-2.free.fr (postfix4-2.free.fr [213.228.0.176]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0B15543EB2 for ; Wed, 22 Jan 2003 13:22:20 -0800 (PST) (envelope-from nsouch@free.fr) Received: from armor.fastether (nas-cbv-8-62-147-157-185.dial.proxad.net [62.147.157.185]) by postfix4-2.free.fr (Postfix) with SMTP id 70F3CCC4E for ; Wed, 22 Jan 2003 22:22:18 +0100 (CET) Received: (qmail 8509 invoked by uid 1001); 22 Jan 2003 21:36:26 -0000 Date: Wed, 22 Jan 2003 22:36:26 +0100 From: Nicolas Souchu To: Doug Rabson Cc: "Pedro F. Giffuni" , Marcel Moolenaar , arch@FreeBSD.ORG Subject: Re: the mythical syscons redesign document ( was Re: Porting wscons ) Message-ID: <20030122223626.B8449@armor.fastether> References: <20030122010246.52789.qmail@web13404.mail.yahoo.com> <1043236066.28124.6.camel@builder02.qubesoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <1043236066.28124.6.camel@builder02.qubesoft.com>; from dfr@nlsystems.com on Wed, Jan 22, 2003 at 11:47:46AM +0000 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Jan 22, 2003 at 11:47:46AM +0000, Doug Rabson wrote: > > 1) properly newbussify all the devices used by our > > console. > > 2) newbussify syscons (it doesn't use methods, does > > it?) and clean the PC specifics as much as possible. > > 3) port and newbussify wscons. > > 4) find a way to run the both at the same time. > > The main sticking point for this stuff is that console is needed before > the device tree is probed. The approach of KGI is to provide a very basic/minimal driver for console boot that can be overlaped later by fully probed graphic board drivers. This is somehow how VGA adapter is organized, with the video_switch used immediatly and later the vga_isa.c glue-code for newbus full attachement. Another way could be a memory virtual fb to allow rendering while booting before full graphic init. But I prefer the solution of the minimal driver with included text rendering if needed. > I think the right approach will be to define > a set of interfaces for the video console and then implement those > interfaces using the lower-level kobj system. This allows you to put > together a working console output system before the rest of the system > is up and running. What is called the kobj interface? Nicholas -- Nicholas Souchu - nsouch@free.fr - nsouch@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message