From: Bob Ham
Date: Tue, 12 Apr 2016 09:58:12 +0100
> On Mon, 2016-04-11 at 15:46 -0700, Stefan Agner wrote:
>
>> Or in other words: Is this a Kernel or systemd issue?
>
> From what I recall, both; an issue with the FEC driver, and issues in
> systemd/udevd's handling of
From: Stefan Agner
Date: Mon, 11 Apr 2016 15:46:08 -0700
> What is the expectation/definition when link configuration should be
> possible? Only after the network device got opened or before?
Only after it is open. Drivers almost always have the entire chip in
powerdown state
From: Doug Goldstein car...@cardoe.com
Date: Sun, 4 Nov 2012 23:45:56 -0600
As Ben Greear pointed out this would allow shell scripts and other
scripting languages to better detect vlans. Kay pointed out that this
would allow better uevent filters in the future as well. So there are
some
From: Doug Goldstein car...@cardoe.com
Date: Mon, 5 Nov 2012 00:19:19 -0600
By this argument we shouldn't ever improve any API or add new syscalls
since we'll have to have fallback code to handle the old interfaces
when the new ones aren't available.
It makes sense to add new APIs when
From: Doug Goldstein car...@cardoe.com
Date: Mon, 22 Oct 2012 00:53:57 -0500
Sets the sysfs device_type to 'vlan' for udev. This makes it easier for
applications that query network information via udev to identify vlans
instead of using strrchr().
Signed-off-by: Doug Goldstein
From: Kay Sievers k...@vrfy.org
Date: Tue, 23 Oct 2012 12:34:11 +0200
On Tue, Oct 23, 2012 at 8:36 AM, David Miller da...@davemloft.net wrote:
From: Doug Goldstein car...@cardoe.com
Date: Mon, 22 Oct 2012 00:53:57 -0500
Sets the sysfs device_type to 'vlan' for udev. This makes it easier