From owner-freebsd-current Mon May 12 18:46:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA19572 for current-outgoing; Mon, 12 May 1997 18:46:40 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA19563; Mon, 12 May 1997 18:46:27 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id LAA12203; Tue, 13 May 1997 11:16:24 +0930 (CST) From: Michael Smith Message-Id: <199705130146.LAA12203@genesis.atrad.adelaide.edu.au> Subject: Re: Backwards compatibiliy for isa_driver In-Reply-To: <19970512220244.64858@x14.mi.uni-koeln.de> from Stefan Esser at "May 12, 97 10:02:44 pm" To: se@FreeBSD.ORG (Stefan Esser) Date: Tue, 13 May 1997 11:16:23 +0930 (CST) Cc: dfr@nlsystems.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Stefan Esser stands accused of saying: > > I have for some time been thinking about better > support for different bus types in FreeBSD. Before you go any further with this, you should check with the Alpha people, and have a look at the NetBSD code for the same thing. Whilst I found the documentation for the NetBSD approach to be pathetic (read: nonexistent), it was relatively easy to find enough examples to get something going. The NetBSD approach blurs the distinction between "bus" and "device", which I think is _the_ critical point. A nested bus is a "device" on its parent bus, but a "bus" to devices below it. > I have code to check for resource conflicts between > PCI and ISA, for example, that could take advantage > of such a change. Since I'm currently rewriting the > PCI code from scratch (for userconfig support, for > example), I'd like to see a possible change to the > device structures go into FreeBSD now ... Hmm, Doug R. and I are just opening a discussion on a "resource manager" (someone just threw a PnP card at me, heh) which might well be relevant in this context. There was mention of a NetBSD "extent allocator" which I need to follow through. Jason T., are you reading this? A few quick words in summary would be handy... -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[