From owner-freebsd-current  Thu Dec 10 01:11:28 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id BAA25385
          for freebsd-current-outgoing; Thu, 10 Dec 1998 01:11:28 -0800 (PST)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA25380
          for <current@FreeBSD.ORG>; Thu, 10 Dec 1998 01:11:27 -0800 (PST)
          (envelope-from jkh@zippy.cdrom.com)
Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1])
	by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id BAA29664;
	Thu, 10 Dec 1998 01:10:33 -0800 (PST)
To: NAKAGAWA Yoshihisa <y-nakaga@nwsl.mesh.ad.jp>
cc: Nate Williams <nate@mt.sri.com>, Mike Smith <mike@smith.net.au>,
        Nathan Dorfman <nathan@rtfm.net>, current@FreeBSD.ORG
Subject: Re: PAO Integration? 
In-reply-to: Your message of "Thu, 10 Dec 1998 15:53:26 +0900."
             <199812100653.PAA02808@chandra.eatell.msr.prug.or.jp> 
Date: Thu, 10 Dec 1998 01:10:32 -0800
Message-ID: <29660.913281032@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> I disagree 3.0-RELEASE style. ISA device, shuld be attach as ISA
> device. PCI PCIC, like CardBus controller, shuld be attach as PCI
> device. It should be separate PCIC core code from bus depend and
> bus independ.

FWIW, I think Yoshihisa-san is quite correct here.  There's nothing
keeping one from writing a separate bus attach function for each
ISA/PCI/etc PCIC just as we do for many of our "ISA" drivers which
have since evolved into PCI market models.

- Jordan

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message