Sponsored Content
Full Discussion: Lspci: PCI Devices?
Special Forums Hardware Lspci: PCI Devices? Post 302866663 by lupin..the..3rd on Tuesday 22nd of October 2013 01:52:39 PM
Old 10-22-2013
Quote:
Originally Posted by Lost in Cyberia
hey everyone, just a general question. I did an lspci on my home computer, and it got me thinking... When I hear pci..I think of the physical slots on your motherboard. usually beige in color.. But the list returned to me is of atleast 20 items. None of which, (besides the graphics card) is plugged into a pci slot... Some things like memory controller, 1,4,5, high definition audio, Address map, DRAM controller, and the most bizarre, Serial ATA Controller... So does this mean, that these devices built onto the motherboard are using the same PCI bus that have the two slots on my board? And why is a SATA controller using a PCI bus? And lastly, how many devices can all comfortably live on 1 bus? Or are all these different PCI buses?
Don't get offended at my suggestion, but you might want to invest in a book that describes how computer hardware works. The concept of a data bus is not new, and a book on the subject would give you a better understanding.

The bus does not need to have any physical slots. Laptops use PCI bus, and have no physical PCI slots. The slot is simply to allow expansion, to add new things onto the bus. Also there is PCI which is a parallel bus with shared bandwidth, and there is PCI-E, which is serial with dedicated bandwidth in a star topology. Lastly, yes a machine can have more than one bus. This is most common in servers, which need to support larger I/O workloads than a desktop.
 

10 More Discussions You Might Find Interesting

1. Solaris

rs232 pci-card

hello mates, do you know a manufactor for rs232 serial pci cards for the sparc architecture? it seems that there is no original product from sun for that purpose. strange, isn't it? problem is that i have a V250 with only one db9 rs232 serial port, and i need it for a modem connection, but i also... (1 Reply)
Discussion started by: pressy
1 Replies

2. Solaris

Pci Id

How do I get the PCI ID for my Realtek adapter? It's a Solaris x86 installation. (5 Replies)
Discussion started by: kuultak
5 Replies

3. UNIX for Dummies Questions & Answers

bad pci slot?

Hi, im having a problem installing my pci wireless card. Im using knoppix, but my problem is with the mobo i think. im using an older laptop, toshiba satellite 2540 and when i plug in the card i get lights on sometimes. this means its getting power right. so then to install the card into the... (0 Replies)
Discussion started by: jestra
0 Replies

4. UNIX for Dummies Questions & Answers

passthrough devices vs. named devices

I am having trouble understanding the difference between a passthrough device and a named device and when you would use one or the other to access equipment. As an example, we have a tape library and giving the command "camcontrol devlist" gives the following output: akx# camcontrol... (1 Reply)
Discussion started by: thumper
1 Replies

5. Solaris

How to look for open pci slots

I'm looking for open PCI slots in our array of sun boxes. I need help on how to distinguish if there's an open slot or not using prtdiag and prtconf. Is there a better tool for this? TIA. Here's my prtdiag -v | grep pci: pci 66 PCI5 SUNW,qlc-pci1077,2312 (scsi-+ ... (9 Replies)
Discussion started by: revzalot
9 Replies

6. Linux

Re: The function of /dev/modules/ and PCI devices

Hello all, I am using openSUSE 11.1 and have an issue with my wireless adapter which I am trying to understand and fix. I just have a quick question about the following image: (It was the output of the lspci command) Why are there two modules being loaded? (ath5k and ath9k) is this a... (2 Replies)
Discussion started by: septima.pars
2 Replies

7. SCO

lspci for SCO?

What is the SCO equivalent to lspci in Linux? This is SCO6 if that matters. (4 Replies)
Discussion started by: dalek
4 Replies

8. Linux

PCI Card recognized

I installed PCI Card HP SC44Ge - SAS1068E on my linux CentOS 5.4 is there a way to find out if the PCI is properly installed and recognized by linux. lspci is enough? just to add that PCI card is connected to a tape... also how can I find out driver and firmware version? thanks a... (1 Reply)
Discussion started by: karlochacon
1 Replies

9. Programming

help writing pci firmware

For a project that I'm working on I want to write a low level PCI driver, but I can't seem to find any free/cheap documentation on PCI firmware specifications. I came across the "pci firmware specification 3.0" manual but this costs USD $1000 :eek:. I am not developing a commercial product... (13 Replies)
Discussion started by: neur0n
13 Replies

10. Hardware

Could USB ever take over PCI

Internally speaking, for your motherboard bus. Would it be possible for a usb standard to be used in place of the PCI or PCIe bus that is now nearly standard on all PC's? If not, why wouldn't this work? (8 Replies)
Discussion started by: Lost in Cyberia
8 Replies
lspci(8)							Linux PCI Utilities							  lspci(8)

NAME
lspci - list all PCI devices SYNOPSIS
lspci [options] DESCRIPTION
lspci is a utility for displaying information about all PCI buses in the system and all devices connected to them. To make use of all the features of this program, you need to have Linux kernel 2.1.82 or newer which supports the /proc/bus/pci interface. With older kernels, the PCI utilities have to use direct hardware access which is available only to root and it suffers from numerous race conditions and other problems. If you are going to report bugs in PCI device drivers or in lspci itself, please include output of "lspci -vvx". OPTIONS
-v Tells lspci to be verbose and display detailed information about all devices. -vv Tells lspci to be very verbose and display even more information (actually everything the PCI device is able to tell). The exact meaning of these data is not explained in this manual page, if you want to know more, consult /usr/include/linux/pci.h or the PCI specs. -n Show PCI vendor and device codes as numbers instead of looking them up in the PCI ID database. -x Show hexadecimal dump of first 64 bytes of the PCI configuration space (the standard header). Useful for debugging of drivers and lspci itself. -xxx Show hexadecimal dump of whole PCI configuration space. Available only for root as several PCI devices crash when you try to read undefined portions of the config space (this behaviour probably doesn't violate the PCI standard, but it's at least very stupid). -b Bus-centric view. Show all IRQ numbers and addresses as seen by the cards on the PCI bus instead of as seen by the kernel. -t Show a tree-like diagram containing all buses, bridges, devices and connections between them. -s [[<bus>]:][<slot>][.[<func>]] Show only devices in specified bus, slot and function. Each component of the device address can be omitted or set as "*" meaning "any value". All numbers are hexadecimal. E.g., "0:" means all devices on bus 0, "0" means all functions of device 0 on any bus, "0.3" selects third function of device 0 on all buses and ".4" shows only fourth function of each device. -d [<vendor>]:[<device>] Show only devices with specified vendor and device ID. Both ID's are given in hexadecimal and may be omitted or given as "*" meaning "any value". -i <file> Use <file> as PCI ID database instead of /usr/share/hwdata/pci.ids. -p <dir> Use <dir> as directory containing PCI bus information instead of /proc/bus/pci. -m Dump PCI device data in machine readable form (both normal and verbose format supported) for easy parsing by scripts. -M Invoke bus mapping mode which scans the bus extensively to find all devices including those behind misconfigured bridges etc. Please note that this is intended only for debugging and as it can crash the machine (only in case of buggy devices, but unfortunately these happen to exist), it's available only to root. Also using -M on PCI access methods which don't directly touch the hardware has no sense since the results are (modulo bugs in lspci) identical to normal listing modes. --version Shows lspci version. This option should be used standalone. PCILIB OPTIONS
The PCI utilities use PCILIB (a portable library providing platform-independent functions for PCI configuration space access) to talk to the PCI cards. The following options control parameters of the library, especially what access method it uses. By default, PCILIB uses the first available access method and displays no debugging messages. Each switch is accompanied by a list of hardware/software configurations it's supported in. -P <dir> Use Linux 2.1 style configuration access to directory <dir> instead of /proc/bus/pci. (Linux 2.1 or newer only) -H1 Use direct hardware access via Intel configuration mechanism 1. (i386 and compatible only) -H2 Use direct hardware access via Intel configuration mechanism 2. Warning: This method is able to address only first 16 devices on any bus and it seems to be very unrealiable in many cases. (i386 and compatible only) -S Use PCI access syscalls. (Linux on Alpha and UltraSparc only) -F <file> Extract all information from given file containing output of lspci -x. This is very useful for analysis of user-supplied bug reports, because you can display the hardware configuration in any way you want without disturbing the user with requests for more dumps. (All systems) -G Increase debug level of the library. (All systems) FILES
/usr/share/hwdata/pci.ids A list of all known PCI ID's (vendors, devices, classes and subclasses). /proc/bus/pci An interface to PCI bus configuration space provided by the post-2.1.82 Linux kernels. Contains per-bus subdirectories with per-card config space files and a devices file containing a list of all PCI devices. SEE ALSO
setpci(8) AUTHOR
The Linux PCI Utilities are maintained by Martin Mares <mj@ucw.cz>. pciutils-2.1.10 30 March 2002 lspci(8)
All times are GMT -4. The time now is 12:59 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy