On Monday, June 10, 2013, Kay Sievers <<a href="mailto:kay@vrfy.org">kay@vrfy.org</a>> wrote: > On Fri, Jun 7, 2013 at 11:46 PM, Sean McGovern <<a href="mailto:gseanmcg@gmail.com">gseanmcg@gmail.com</a>> wrote: >> This is definitely not a common case as almost all of the other Linux machines I have access to expose a network controller in domain 0. > > Yeah, I've only seen domains used on huge SGI machines. 256 PCI buses > are quite a lot for a normal machine. :) > >> At least in my case each of the domains has a bus ID unique to amongst all of the domains, but I'm reasonably sure this isn't mandated by the PCI specifications. > > They don't share the numbers, yeah. > >> 0002:20:0f.0 Ethernet controller: Apple Inc. UniNorth 2 GMAC (Sun GEM) (rev 80) > > We could add a P<domain> or m<domain> in front: > enP2p32s15 > enm2p32s15 > > Or something else, we just have to pick one. :) > > And we would suppress that for all the common domain == 0x0000 cases. > > Kay OK. Would you like me to cook up a better patch with this suggestion? -- Sean McG