linux-kernel - Re: Understanding lspci output

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID:  <mj+md-20071017.110231.1634.nikam@ucw.cz>
Date:	Wed, 17 Oct 2007 13:07:02 +0200
From:	Martin Mares <mj@....cz>
To:	John Sigler <linux.kernel@...e.fr>
Cc:	linux-kernel@...r.kernel.org, linux-pci@...ey.karlin.mff.cuni.cz
Subject: Re: Understanding lspci output

Hello!

> 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.

> 2. Do any of the PCI buses support 66 MHz operation?

Yes, PCI-X does.

> 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.

				Have a nice fortnight
-- 
Martin `MJ' Mares                          <mj@....cz>   http://mj.ucw.cz/
Faculty of Math and Physics, Charles University, Prague, Czech Rep., Earth
hAS ANYONE SEEN MY cAPSLOCK KEY?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/