Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 22 Jan 2003 22:36:26 +0100
From:      Nicolas Souchu <nsouch@free.fr>
To:        Doug Rabson <dfr@nlsystems.com>
Cc:        "Pedro F. Giffuni" <giffunip@yahoo.com>, Marcel Moolenaar <marcel@xcllnt.net>, arch@FreeBSD.ORG
Subject:   Re: the mythical syscons redesign document ( was Re: Porting wscons )
Message-ID:  <20030122223626.B8449@armor.fastether>
In-Reply-To: <1043236066.28124.6.camel@builder02.qubesoft.com>; from dfr@nlsystems.com on Wed, Jan 22, 2003 at 11:47:46AM %2B0000
References:  <20030122010246.52789.qmail@web13404.mail.yahoo.com> <1043236066.28124.6.camel@builder02.qubesoft.com>

next in thread | previous in thread | raw e-mail | index | archive | help
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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030122223626.B8449>