All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Sigler <linux.kernel@free.fr>
To: Martin Mares <mj@ucw.cz>
Cc: linux-kernel@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz
Subject: Re: Understanding lspci output
Date: Wed, 17 Oct 2007 13:57:36 +0200	[thread overview]
Message-ID: <4715F8B0.6080107@free.fr> (raw)
In-Reply-To: <mj+md-20071017.110231.1634.nikam@ucw.cz>

Hello Martin,

Martin Mares wrote:

>> I ran lspci -vvv on a system:
>> http://linux.kernel.free.fr/halt/lspci.txt
>>
>> (I used lspci version 2.2.5 in case it matters.)
>>
>> But I'm having a hard time making sense of the output.
>>
>> 1. How many PCI buses are there in the system?
> 
> Two, just see the bus numbers of the devices. (However, there might be
> additional buses with no devices present and in case these are connected
> to a separate host bridge, they need not be visible.)
> 
>> 4. Does the system have a PCI-X bus?
> 
> Yes, the devices on bus 01 are PCI-X devices, so there is a PCI-X bus.

I thought PCI-X devices could operate on a PCI bus? If that is true, 
then the presence of a PCI-X device would not necessarily imply the 
presence of a PCI-X bus, right?

There are no external PCI-X slots in the system, only 2 PCI slots.
The 4 NICs are integrated to the motherboard.
http://advantech.com/products/1U-Rackmount-Intel-Pentium-4Processor-based-Platform-with-4PCI-LAN-Ports-2-PCI-Expansion-Slots/mod_1-23A2W4.aspx

>> 2. Do any of the PCI buses support 66 MHz operation?
> 
> Yes, PCI-X does.

So the 01:0f.0 device (Multimedia video controller) is on the same bus 
as the 4 PCI-X devices and will have to share the bus bandwidth?

Does 66MHz+ in the Status line means this device is running at 66 MHz?

>> 3. Do any of the PCI slots support 64-bit data path?
> 
> This cannot be inferred from the lspci output -- there is no way how to
> tell if a bus has physical slots or it exists only internally.

Can I use lspci to see whether a specific PCI device is using a 64-bit 
data path? (e.g. the 01:0f.0 device)

Regards.

  reply	other threads:[~2007-10-17 11:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-17  9:08 Understanding lspci output John Sigler
2007-10-17 11:07 ` Martin Mares
2007-10-17 11:57   ` John Sigler [this message]
     [not found] <fa.l0Y1Suv/oOMZej6qugSY8HCfo78@ifi.uio.no>
     [not found] ` <fa.5QGRWM6v1/dwLaQe8D1zMU1KZeM@ifi.uio.no>
     [not found]   ` <fa.FcCntqDHRe76qrRi4OjUjOq2ak4@ifi.uio.no>
2007-10-17 23:37     ` Robert Hancock

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4715F8B0.6080107@free.fr \
    --to=linux.kernel@free.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    --cc=mj@ucw.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.