From owner-freebsd-current  Thu Feb 26 22:07:48 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id WAA28616
          for freebsd-current-outgoing; Thu, 26 Feb 1998 22:07:48 -0800 (PST)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA28584
          for <freebsd-current@FreeBSD.ORG>; Thu, 26 Feb 1998 22:07:42 -0800 (PST)
          (envelope-from jkh@time.cdrom.com)
Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.6.9) with ESMTP id WAA29104; Thu, 26 Feb 1998 22:07:09 -0800 (PST)
To: "John W. DeBoskey" <jwd@unx.sas.com>
cc: ken@plutotech.com, mark@vmunix.com, freebsd-current@FreeBSD.ORG
Subject: Re: pciconf broken? 
In-reply-to: Your message of "Thu, 26 Feb 1998 17:49:06 EST."
             <199802262249.AA07958@iluvatar.unx.sas.com> 
Date: Thu, 26 Feb 1998 22:07:09 -0800
Message-ID: <29101.888559629@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Well, apparently the Plutotech people are working on it already, so I
guess the answer to that question is "wait" :-)

				Jordan

> Well....
> 
>    What might it take to simply get the mechanism fixed in -current?
> 
> Thanks,
> John
> 
> > And I'm still wondering why /dev/pci is reusing a major number that
> > majors.i386 claims it can't have... :)
> >
> > 					Jordan
> 
> 
> -- 
> jwd@unx.sas.com       (w) John W. De Boskey          (919) 677-8000 x6915
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message


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