From owner-freebsd-current Sun Aug 23 19:29:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA02238 for freebsd-current-outgoing; Sun, 23 Aug 1998 19:29:00 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA02211 for ; Sun, 23 Aug 1998 19:28:51 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.8.8/8.8.5) id UAA05491; Sun, 23 Aug 1998 20:27:57 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199808240227.UAA05491@panzer.plutotech.com> Subject: Re: pciconf In-Reply-To: from Chuck Robey at "Aug 23, 98 07:58:31 pm" To: chuckr@glue.umd.edu (Chuck Robey) Date: Sun, 23 Aug 1998 20:27:57 -0600 (MDT) Cc: freebsd-current@FreeBSD.ORG 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 Chuck Robey wrote... > While investigating pci stuff (for an audio driver) I saw a man page for > pciconf. It says that there's a -l option, so I tried that, as both a > regular user and root, and both times I got: > > picnic:/usr2/chuckr:55 >pciconf -l > pciconf: ioctl(PCIOCGETCONF): Operation not supported by device > > I figured to use the pciconf utility (the source code) to educate myself > as to what pci functions might work like, so this is unsettling. Does > anyone know what's going on here? Below, I'm excerpting the part of my > dmesg that I figure might be relevant: The problem is that the PCIOCGETCONF ioctl isn't supported in -current. There's nothing wrong with your machine. I've modified the PCI code in the CAM tree to support that ioctl again. So 'pciconf -l' now produces output like: {panzer:/usr/home/ken:7:0} pciconf -l ahc1@pci1:5:0: class=0x010000 card=0x00000000 chip=0x82789004 rev=0x00 hdr=0x00 ahc0@pci1:4:0: class=0x010000 card=0x00000000 chip=0x82789004 rev=0x00 hdr=0x00 vga0@pci0:13:0: class=0x030000 card=0x00000000 chip=0x0519102b rev=0x01 hdr=0x00 de1@pci0:12:0: class=0x020000 card=0x00000000 chip=0x00091011 rev=0x12 hdr=0x00 bktr0@pci0:11:0: class=0x040000 card=0x00000000 chip=0x0350109e rev=0x11 hdr=0x00 de0@pci0:10:0: class=0x020000 card=0x00000000 chip=0x00091011 rev=0x11 hdr=0x00 chip2@pci0:9:0: class=0x060400 card=0x00000000 chip=0x00011011 rev=0x02 hdr=0x01 chip1@pci0:1:0: class=0x060100 card=0x00000000 chip=0x70008086 rev=0x01 hdr=0x00 chip0@pci0:0:0: class=0x060000 card=0x00000000 chip=0x12378086 rev=0x02 hdr=0x00 The new version of that ioctl also supports matching against bus, device, function, device name and unit number. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message