From owner-freebsd-current  Wed Feb 25 22:02:15 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id WAA25483
          for freebsd-current-outgoing; Wed, 25 Feb 1998 22:02:15 -0800 (PST)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from thunderdome.plutotech.com (root@thunderdome.plutotech.com [206.168.67.122])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA25477
          for <freebsd-current@freebsd.org>; Wed, 25 Feb 1998 22:02:13 -0800 (PST)
          (envelope-from ken@panzer.plutotech.com)
Received: from panzer.plutotech.com (ken@panzer.plutotech.com [206.168.67.125])
          by thunderdome.plutotech.com (8.8.7/8.8.5) with ESMTP id XAA00308;
          Wed, 25 Feb 1998 23:02:11 -0700 (MST)
Received: (from ken@localhost)
          by panzer.plutotech.com (8.8.8/8.8.5) id XAA11787;
          Wed, 25 Feb 1998 23:02:09 -0700 (MST)
From: "Kenneth D. Merry" <ken@plutotech.com>
Message-Id: <199802260602.XAA11787@panzer.plutotech.com>
Subject: Re: pciconf broken?
In-Reply-To: <199802260316.AA06482@iluvatar.unx.sas.com> from "John W. DeBoskey" at "Feb 25, 98 10:16:54 pm"
To: jwd@unx.sas.com (John W. DeBoskey)
Date: Wed, 25 Feb 1998 23:02:09 -0700 (MST)
Cc: freebsd-current@FreeBSD.ORG, jwd@unx.sas.com
X-Mailer: ELM [version 2.4ME+ PL28s (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

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.

	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