From owner-freebsd-arch Sun Jan 19 17:10:31 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 082D937B401 for ; Sun, 19 Jan 2003 17:10:30 -0800 (PST) Received: from ns1.xcllnt.net (209-128-86-226.BAYAREA.NET [209.128.86.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3215E43F18 for ; Sun, 19 Jan 2003 17:10:29 -0800 (PST) (envelope-from marcel@xcllnt.net) Received: from athlon.pn.xcllnt.net (athlon.pn.xcllnt.net [192.168.4.3]) by ns1.xcllnt.net (8.12.6/8.12.6) with ESMTP id h0K1AEMW013734; Sun, 19 Jan 2003 17:10:14 -0800 (PST) (envelope-from marcel@piii.pn.xcllnt.net) Received: from athlon.pn.xcllnt.net (localhost [127.0.0.1]) by athlon.pn.xcllnt.net (8.12.6/8.12.6) with ESMTP id h0K1AEMa001125; Sun, 19 Jan 2003 17:10:14 -0800 (PST) (envelope-from marcel@athlon.pn.xcllnt.net) Received: (from marcel@localhost) by athlon.pn.xcllnt.net (8.12.6/8.12.6/Submit) id h0K1AElS001124; Sun, 19 Jan 2003 17:10:14 -0800 (PST) Date: Sun, 19 Jan 2003 17:10:14 -0800 From: Marcel Moolenaar To: "M. Warner Losh" Cc: nsouch@free.fr, arch@FreeBSD.ORG Subject: Re: Newbusifying kbd? Message-ID: <20030120011014.GB989@athlon.pn.xcllnt.net> References: <20030119225129.A6948@armor.fastether> <20030119233031.GA24377@dhcp01.pn.xcllnt.net> <20030119.172331.11474060.imp@bsdimp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030119.172331.11474060.imp@bsdimp.com> User-Agent: Mutt/1.5.3i 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 Sun, Jan 19, 2003 at 05:23:31PM -0700, M. Warner Losh wrote: > In message: <20030119233031.GA24377@dhcp01.pn.xcllnt.net> > Marcel Moolenaar writes: > : On Sun, Jan 19, 2003 at 10:51:29PM +0100, Nicolas Souchu wrote: > : > > : > Has anyone already thought about newbusifying kbd? > : > : I've been playing with the scary thought of redoing syscons completely; > : whether rewriting or importing. It's not only kbd that needs > : newbusification and fb(4) is really full of ISA/BIOS stuff. > : > : Anyway: this is beyond just newbusification... > > We can't support the various PCMCIA/CardBus docking stations easily in > FreeBSD right now because kbd and other 'basic' things haven't been > newbusified. > > Maybe we should just do a wscons port, now that it has shown its use > in NetBSD. wscons is very portable, but a little less user friendly > than syscons. syscons gives a better user experience, but tends to be > a little x86 centric. Yes. The sparc64 port also struggles with this. Jake was thinking about importing wscons from NetBSD as well. I decided to replace the x86/ISA centric VGA driver on the ia64 branch with a new PCI driver and to make sc(4) itself not dependent on ISA. For some strange reason we attach sc(4) to ISA, even though sc(4) itself is not an ISA device. It sort of works, but no really. It's a hack in any case... I like to call for a console project where all the issues can be raised and discussed so that we have a good understanding of requirements and problems before we do anything else. At the same time I realize that we're all busy enough for yet another project... -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message