Date: Sun, 23 Aug 1998 19:58:31 -0400 (EDT) From: Chuck Robey <chuckr@glue.umd.edu> To: freebsd-current@FreeBSD.ORG Subject: pciconf Message-ID: <Pine.BSF.4.00.9808231954390.361-100000@picnic.mat.net>
next in thread | raw e-mail | index | archive | help
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: FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Probing for devices on PCI bus 0: chip0: <Intel 82440FX (Natoma) PCI and memory controller> rev 0x02 on pci0.0.0 chip1: <Intel 82371SB PCI to ISA bridge> rev 0x01 on pci0.7.0 vga0: <Cirrus Logic GD5434 SVGA controller> rev 0xfc on pci0.11.0 ncr0: <ncr 53c875 fast20 wide scsi> rev 0x03 int a irq 17 on pci0.13.0 ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- 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?Pine.BSF.4.00.9808231954390.361-100000>