Onboard network controllers are not always on PCI domain 0.
---
src/udev/udev-builtin-net_id.c | 22 +-
1 file changed, 17 insertions(+), 5 deletions(-)
diff --git a/src/udev/udev-builtin-net_id.c b/src/udev/udev-builtin-net_id.c
index 5719021..c8d3ad3 100644
---
Here is my new attempt for interface naming for cards in non-zero domains.
Oddly enough, I still get an f0 at the end of mine even though it is not
PCI multifunction.
sean@hanyuu ~ $ udevadm test-builtin net_id /sys/class/net/enP2p32s15f0
2/dev/null | grep PATH
ID_NET_NAME_PATH=enP2p32s15
On Monday, June 10, 2013, Kay Sievers k...@vrfy.org wrote:
On Fri, Jun 7, 2013 at 11:46 PM, Sean McGovern gsean...@gmail.com 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
Onboard network controllers are not always on PCI domain 0.
---
src/udev/udev-builtin-net_id.c | 14 --
1 file changed, 12 insertions(+), 2 deletions(-)
diff --git a/src/udev/udev-builtin-net_id.c b/src/udev/udev-builtin-net_id.c
index 5719021..3e77f30 100644
---
Ignore this patch then -- I can't change the PCI geography of my older G4 Mac
Mini, and without this patch predictable interface naming does not work for it.
I'll just keep it locally.
-- Sean McGovern
--Original Message--
From: Kay Sievers
To: McGovern, Sean
Cc: systemd-devel
: systemd-devel@lists.freedesktop.org
Subject: Re: [systemd-devel] [PATCH] udev: make net_id more robust
Sent: Jun 7, 2013 17:20
On Fri, Jun 7, 2013 at 10:58 PM, Sean McGovern gsean...@gmail.com wrote:
Ignore this patch then -- I can't change the PCI geography of my older G4 Mac
Mini, and without
