From owner-freebsd-current Thu Feb 26 10:31:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA29100 for freebsd-current-outgoing; Thu, 26 Feb 1998 10:31:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from vnode.vmunix.com (vnode.vmunix.com [209.112.4.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA29085 for ; Thu, 26 Feb 1998 10:31:35 -0800 (PST) (envelope-from mark@vnode.vmunix.com) Received: (from mark@localhost) by vnode.vmunix.com (8.8.8/8.8.8) id NAA12740; Thu, 26 Feb 1998 13:40:35 -0500 (EST) (envelope-from mark) Message-ID: <19980226134034.12061@vmunix.com> Date: Thu, 26 Feb 1998 13:40:34 -0500 From: Mark Mayo To: "Kenneth D. Merry" , "John W. DeBoskey" Cc: freebsd-current@FreeBSD.ORG Subject: Re: pciconf broken? References: <199802260316.AA06482@iluvatar.unx.sas.com> <199802260602.XAA11787@panzer.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199802260602.XAA11787@panzer.plutotech.com>; from Kenneth D. Merry on Wed, Feb 25, 1998 at 11:02:09PM -0700 X-Operating-System: FreeBSD 2.2.5-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 :-) -Mark > > I have a fixed version of that ioctl in the CAM code. It also > passes back the device name (e.g. ahc, fxp, de..) and the unit number of > the device in question. > > Stefan and I have yet to fully work out how the new version should > look, so that's why it isn't in -current or anything. > > > Ken > -- > Kenneth Merry > ken@plutotech.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- ------------------------------------------------------------------------ Mark Mayo mark@vmunix.com RingZero Comp. http://www.vmunix.com/mark finger mark@vmunix.com for my PGP key and GCS code ------------------------------------------------------------------------ "The problem is how do you build tools that understand your programs at a deeper semantic level." - James Gosling To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message