Attachment 32951 Details for Bug 26352 – lspci

lspci

lspci.txt (text/plain), 1.58 KB, created by Sachin Garg on 2010-01-31 12:03:33 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Sachin Garg

Created: 2010-01-31 12:03:33 UTC

Size: 1.58 KB

patch

obsolete

>00:00.0 Host bridge: Intel Corporation Device 0044 (rev 12)
>00:02.0 VGA compatible controller: Intel Corporation Device 0046 (rev 12)
>00:16.0 Communication controller: Intel Corporation Ibex Peak HECI Controller (rev 06)
>00:1a.0 USB Controller: Intel Corporation Ibex Peak USB2 Enhanced Host Controller (rev 05)
>00:1b.0 Audio device: Intel Corporation Ibex Peak High Definition Audio (rev 05)
>00:1c.0 PCI bridge: Intel Corporation Ibex Peak PCI Express Root Port 1 (rev 05)
>00:1c.1 PCI bridge: Intel Corporation Ibex Peak PCI Express Root Port 2 (rev 05)
>00:1d.0 USB Controller: Intel Corporation Ibex Peak USB2 Enhanced Host Controller (rev 05)
>00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev a5)
>00:1f.0 ISA bridge: Intel Corporation Ibex Peak LPC Interface Controller (rev 05)
>00:1f.2 SATA controller: Intel Corporation Ibex Peak 4 port SATA AHCI Controller (rev 05)
>00:1f.3 SMBus: Intel Corporation Ibex Peak SMBus Controller (rev 05)
>00:1f.6 Signal processing controller: Intel Corporation Ibex Peak Thermal Subsystem (rev 05)
>02:00.0 Ethernet controller: Broadcom Corporation NetLink BCM57780 Gigabit Ethernet PCIe (rev 01)
>04:00.0 Network controller: Atheros Communications Inc. AR928X Wireless Network Adapter (PCI-Express) (rev 01)
>ff:00.0 Host bridge: Intel Corporation Device 2c62 (rev 02)
>ff:00.1 Host bridge: Intel Corporation Device 2d01 (rev 02)
>ff:02.0 Host bridge: Intel Corporation Device 2d10 (rev 02)
>ff:02.1 Host bridge: Intel Corporation Device 2d11 (rev 02)
>ff:02.2 Host bridge: Intel Corporation Device 2d12 (rev 02)
>ff:02.3 Host bridge: Intel Corporation Device 2d13 (rev 02)

Actions: View

Attachments on bug 26352: 32951 | 32952 | 32955 | 33914

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.