Messages in this thread | | | Date | Sun, 12 Aug 2018 11:28:37 +0200 | From | Martin Mares <> | Subject | Re: lspci: Display path to device |
| |
Hello!
> One is that using -P and -s together doesn't work because we haven't > scanned the entire topology. > > $ ./lspci-mw -PF tests/fujitsu-p8010.lspci -s 1d:00.0 > 00:1e.0/03.0/00.0 Network controller: 3Com Corporation 3com 3CRWE154G72 [Office Connect Wireless LAN Adapter] (rev 01) > $ ./lspci-mm -PF tests/fujitsu-p8010.lspci -s 1d:00.0 > 1d:00.0 Network controller: 3Com Corporation 3com 3CRWE154G72 [Office Connect Wireless LAN Adapter] (rev 01)
Fixed. When topology is required, we now scan all devices and apply the filters later.
> The other is that even when not using -s, the topology isn't fully represented: > > $ ./lspci-mm -PF tests/fujitsu-p8010.lspci |grep 3com > 00:1e.0/00.0 Network controller: 3Com Corporation 3com 3CRWE154G72 [Office Connect Wireless LAN Adapter] (rev 01)
Ah well, it seems that the tree mode never worked with CardBus bridges. Fixed.
After some pondering, I changed the format of the paths to include bus numbers in all steps. I think it is more intuitive.
Please give it a try. If it works, I will merge the branch to master.
Martin
| |