From owner-freebsd-current Mon Sep 28 09:13:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA03080 for freebsd-current-outgoing; Mon, 28 Sep 1998 09:13:45 -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 JAA03059 for ; Mon, 28 Sep 1998 09:13:38 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id KAA16309; Mon, 28 Sep 1998 10:13:20 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199809281613.KAA16309@panzer.plutotech.com> Subject: Re: Is pciconf now fixed? In-Reply-To: <360F828F.446B@cs.strath.ac.uk> from Roger Hardiman at "Sep 28, 98 01:35:27 pm" To: roger@cs.strath.ac.uk (Roger Hardiman) Date: Mon, 28 Sep 1998 10:13:20 -0600 (MDT) Cc: 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 Roger Hardiman wrote... > the pciconf utility has been broken for ages on 3.0. > (I'm still on SNAP19980804) It's only been broken for *listing* devices. Reading and setting PCI registers has always worked. > Has it been fixed in the Beta? Yes. {bladerunner:/usr/home/ken:4:0} uname -rs FreeBSD 3.0-BETA {bladerunner:/usr/home/ken:5:0} pciconf -l chip0@pci0:0:0: class=0x060000 card=0x00000000 chip=0x122d8086 rev=0x02 hdr=0x00 chip1@pci0:7:0: class=0x060100 card=0x00000000 chip=0x122e8086 rev=0x02 hdr=0x00 ncr0@pci0:17:0: class=0x010000 card=0x80001092 chip=0x008f1000 rev=0x04 hdr=0x00 fxp0@pci0:18:0: class=0x020000 card=0x00098086 chip=0x12298086 rev=0x04 hdr=0x00 vga0@pci0:19:0: class=0x030000 card=0x00000000 chip=0x47581002 rev=0x03 hdr=0x00 ahc0@pci0:20:0: class=0x010000 card=0x00000000 chip=0x81789004 rev=0x00 hdr=0x00 Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message