From owner-freebsd-arch@FreeBSD.ORG  Wed Feb 23 20:51:04 2005
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
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 1672916A4CE; Wed, 23 Feb 2005 20:51:04 +0000 (GMT)
Received: from harmony.village.org (rover.village.org [168.103.84.182])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 391D943D5C; Wed, 23 Feb 2005 20:51:03 +0000 (GMT)
	(envelope-from imp@bsdimp.com)
Received: from localhost (localhost.village.org [127.0.0.1])
	by harmony.village.org (8.13.1/8.13.1) with ESMTP id j1NKoH8h045182;
	Wed, 23 Feb 2005 13:50:17 -0700 (MST)
	(envelope-from imp@bsdimp.com)
Date: Wed, 23 Feb 2005 13:50:17 -0700 (MST)
Message-Id: <20050223.135017.74708574.imp@bsdimp.com>
To: jhb@FreeBSD.ORG
From: Warner Losh <imp@bsdimp.com>
In-Reply-To: <200502231257.12798.jhb@FreeBSD.org>
References: <20050222.143230.41648746.imp@bsdimp.com>
	<200502231257.12798.jhb@FreeBSD.org>
X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
cc: arch@FreeBSD.ORG
cc: freebsd-arch@FreeBSD.ORG
Subject: Re: Better device probe values
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussion related to FreeBSD architecture
	<freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Feb 2005 20:51:04 -0000

> Several typos, but that's minor.  Sounds ok to me.  Note that I think 
> BUS_PROBE_GENERIC might not really be enough though (PCI bridge drivers are 
> actually somewhat tricky, on x86 for PCI-PCI you have ACPI, PCIBIOS, MPTable, 
> and generic for example), but for more tricky cases we can still use numeric 
> values.
> 

Well, on x86 we have 3 different pci busses, but they aren't in any
more complicated a heirarchy than 'generic' or something that replaces
'generic.'  You won't have PCIBIOS and MPTable fighting for control of
a system, will you?

> s/HOOVER/ROOBA/ :)

:-)

Warner