Date: Thu, 26 Feb 1998 11:44:59 -0700 (MST) From: "Kenneth D. Merry" <ken@plutotech.com> To: mark@vmunix.com (Mark Mayo) Cc: ken@plutotech.com, jwd@unx.sas.com, freebsd-current@FreeBSD.ORG Subject: Re: pciconf broken? Message-ID: <199802261844.LAA14199@panzer.plutotech.com> In-Reply-To: <19980226134034.12061@vmunix.com> from Mark Mayo at "Feb 26, 98 01:40:34 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
Mark Mayo wrote... > On Wed, Feb 25, 1998 at 11:02:09PM -0700, Kenneth D. Merry wrote: > > John W. DeBoskey wrote... > > > Hi, > > > > > > I'm running FreeBSD 3.0-980223-SNAP (GENERIC). > > > > > > When I run pciconf, I get the following: > > > > > > # pciconf -l > > > pciconf: ioctl(PCIOCGETCONF): Operation not supported by device > > > > > > > > > Does anyone have any info about this? Should it work? Is it > > > a known problem? > > > > This is a known problem. I believe it has been broken since around > > April 1997. > > Hmm. It was working on my -CURRENT box from Dec. 8th, but I > just cvsup'ed and made the world last night and now pciconf > doesn't work... > > So I would guess it broke somewhere in between :-) That doesn't make any sense. The only change between December 8th and today to pci.c is: Index: pci.c =================================================================== RCS file: /usr/local/cvs/src/sys/pci/pci.c,v retrieving revision 1.80 retrieving revision 1.81 diff -r1.80 -r1.81 26c26 < * $Id: pci.c,v 1.80 1997/11/07 08:53:28 phk Exp $ --- > * $Id: pci.c,v 1.81 1998/01/24 02:54:47 eivind Exp $ 31a32,33 > > #include "opt_devfs.h" And that certainly wouldn't affect the PCIOCGETCONF ioctl. Are you sure you haven't tried CAM at all? If you have, that would probably explain why pciconf -l worked for you before. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199802261844.LAA14199>