Peter Stuge wrote:
Run lspci -h and look under "Selection of devices" - it should work. But the sh fu may be broken by now.
I tested again and it's just that the complete line does not work. I just copied and pasted this into a shell, and it did not work, unsure if this was the right way. If I insert the output of the one command by hand, it works as expected. Maybe this command line could be improved. Just for the case you still need the output, it is attached.
It's interesting that you have two EHCI devices with a debug port each. I don't know what coreboot does in this case. Not much to do since you can't test, but you could look around at the port registers to see if you can locate if the debug port(s!) actually go(es) anywhere on the board.
I don't know how to find out, whether those debug ports go anywhere on the board. If it is easy, could you help me with that? Thanks!
Yul Rottmann
$ lspci|grep EHCI|cut -f1 -d' ' 00:12.2 00:13.2
# lspci -vs 00:12.2 00:12.2 USB Controller: ATI Technologies Inc SB700/SB800 USB EHCI Controller (prog-if 20) Subsystem: Giga-byte Technology Device 5004 Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 17 Memory at fe02c000 (32-bit, non-prefetchable) [size=256] Capabilities: [c0] Power Management version 2 Capabilities: [e4] Debug port: BAR=1 offset=00e0 Kernel driver in use: ehci_hcd Kernel modules: ehci-hcd
# lspci -ns 00:12.2 00:12.2 0c03: 1002:4396
# lspci -vs 00:13.2 00:13.2 USB Controller: ATI Technologies Inc SB700/SB800 USB EHCI Controller (prog-if 20) Subsystem: Giga-byte Technology Device 5004 Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 19 Memory at fe029000 (32-bit, non-prefetchable) [size=256] Capabilities: [c0] Power Management version 2 Capabilities: [e4] Debug port: BAR=1 offset=00e0 Kernel driver in use: ehci_hcd Kernel modules: ehci-hcd
# lspci -ns 00:13.2 00:13.2 0c03: 1002:4396
The following does not work:
# lspci -vs $(lspci|grep EHCI|cut -f1 -d' ') Usage: lspci [<switches>]