From owner-freebsd-arch Thu Jan 23 12:58:14 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 955C937B401 for ; Thu, 23 Jan 2003 12:58:13 -0800 (PST) Received: from cirb503493.alcatel.com.au (c18609.belrs1.nsw.optusnet.com.au [210.49.80.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 86BB943EB2 for ; Thu, 23 Jan 2003 12:58:11 -0800 (PST) (envelope-from peterjeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1]) by cirb503493.alcatel.com.au (8.12.5/8.12.5) with ESMTP id h0NKw9LZ017317; Fri, 24 Jan 2003 07:58:09 +1100 (EST) (envelope-from jeremyp@cirb503493.alcatel.com.au) Received: (from jeremyp@localhost) by cirb503493.alcatel.com.au (8.12.6/8.12.5/Submit) id h0NKw8tH017316; Fri, 24 Jan 2003 07:58:08 +1100 (EST) Date: Fri, 24 Jan 2003 07:58:08 +1100 From: Peter Jeremy To: Marcel Moolenaar Cc: arch@FreeBSD.ORG Subject: Re: the mythical syscons redesign document ( was Re: Porting wscons ) Message-ID: <20030123205808.GA17281@cirb503493.alcatel.com.au> References: <20030122010246.52789.qmail@web13404.mail.yahoo.com> <1043236066.28124.6.camel@builder02.qubesoft.com> <20030122223626.B8449@armor.fastether> <20030122220029.GD590@dhcp01.pn.xcllnt.net> <20030123075556.A10370@armor.fastether> <20030123071232.GA80532@dhcp01.pn.xcllnt.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030123071232.GA80532@dhcp01.pn.xcllnt.net> User-Agent: Mutt/1.4i 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:12:32PM -0800, Marcel Moolenaar wrote: >On Thu, Jan 23, 2003 at 07:55:56AM +0100, Nicolas Souchu wrote: >> I agree. But booting a true PCI/AGP (and not ISA) graphic card without >> the bus stuff initialized seems very hard. > >Yes and no. The PCI standard has defined the legacy memory address of >the frame buffer and the legacy I/O port range for compatibility. I >expect that we can safely probe that. I don't know how this works in >non-PCI system though... I think this is only true of VGA devices. Definitely the DEC TGA does not have any legacy address support - it has to be initialised as a generic PCI device and then written to using its proprietary command set. And based on other comments in this thread, I think that USB keyboards don't have legacy AT-keyboard support either. >The approach I took on the ia64 branch is to have a xxx_machdep.c in >sys/$ARCH/$ARCH for every device xxx that can be a low level console. Whilst I don't see any alternative, this is a fairly expensive approach since the number of MD files starts growing alarmingly as the number of architectures and console devices increases. (Though it's definitely better than having lots of MD code buried in supposedly MI files). Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message