On Fri, Aug 10, 2018 at 12:30:35PM +0200, Martin Mares wrote: > Hello! > > > ... the more I think about it, the more I am convinced that we want to > > re-use the bus topology builder from ls-tree.c. I will give it a try, > > stay tuned. > > Please see the "topology" branch in pciutils.git. Thanks. I found two problems so far. 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) 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) I've attached a compressed form of the fujitsu-p8010.lspci dump for your testing.
Attachment:
fujitsu-p8010.lspci.xz
Description: application/xz
