From owner-freebsd-current  Thu Feb 26 15:12:07 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id PAA18836
          for freebsd-current-outgoing; Thu, 26 Feb 1998 15:12:07 -0800 (PST)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA18823
          for <freebsd-current@FreeBSD.ORG>; Thu, 26 Feb 1998 15:12:01 -0800 (PST)
          (envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
	by godzilla.zeta.org.au (8.8.7/8.8.7) id KAA18123;
	Fri, 27 Feb 1998 10:03:08 +1100
Date: Fri, 27 Feb 1998 10:03:08 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199802262303.KAA18123@godzilla.zeta.org.au>
To: jkh@time.cdrom.com, ken@plutotech.com
Subject: Re: pciconf broken?
Cc: freebsd-current@FreeBSD.ORG, jwd@unx.sas.com, mark@vmunix.com
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>And I'm still wondering why /dev/pci is reusing a major number that
>majors.i386 claims it can't have... :)

pci has been using it since rev.1.57 (1996/10/22) of pci.c.  It was
not registered properly, and some vaporware reused the number.

Bruce

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