From owner-cvs-all Wed Nov 4 15:02:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA25481 for cvs-all-outgoing; Wed, 4 Nov 1998 15:02:48 -0800 (PST) (envelope-from owner-cvs-all@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA25463; Wed, 4 Nov 1998 15:02:41 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.9.1/8.8.5) with SMTP id XAA21521; Wed, 4 Nov 1998 23:00:51 GMT Date: Wed, 4 Nov 1998 23:00:51 +0000 (GMT) From: Doug Rabson To: Garrett Wollman cc: Peter Wemm , Kazutaka YOKOTA , sos@FreeBSD.ORG, cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: src/sys/modules/syscons saver.h ... In-Reply-To: <199811041602.LAA21681@khavrinen.lcs.mit.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk On Wed, 4 Nov 1998, Garrett Wollman wrote: > < said: > > > I'm really hoping that Garrett comes up with something useful for a real > > isa configuration system under the new framework. > > syscons and psm compile and appear to work (at least, probe and attach > succeed) on my laptop. > > I'm also a bit unhappy with the organization. The soft configuration > of syscons is splattered out all over a bajillion static variables, > and the interfaces to things like kbdio are not at all clean. (I > didn't make any effort to allow configuration of the keyboard > controller port or IRQs.) There are a few things that are totally > missing because the code doesn't supply them to me -- for example, I'd > like to reserve the entire VGA frame buffer, but the code which > might tell me never initializes that part of the data structure. > We still don't usefully deal with PCI graphics cards (but I haven't > gotten that far anyway). > > What I'd like to see is the following: > > device kbd0 at isa? port ? irq 1 > device kbd1 at usb? > device fb0 at isa? port ? maddr ? msize ? > device fb1 at pci? > pseudo-device sc0 > > ...where sc0 knows how to poke around and find the appropriate > keyboard and framebuffer devices and graft itself on top. This would be really nice (but I think the unit numbers should be '?' instead of explicitly specified) and I have daydreamed in this direction before. I always wake up when I try to think about how to get the console working. The console is probed and initialised well before the device tree is configured. For debugging, we really need a working console with keyboard before main() gets called. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message