[added Tom Gundersen as he seemed to have worked on udev's net link
built-in]
On 2016-04-12 08:44, David Miller wrote:
> 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
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
On Mon, 2016-04-11 at 15:46 -0700, Stefan Agner wrote:
> The FEC driver (fec_main.c) does not initialize phy_dev until the
> device
> has been opened, and therefor the callback
> fec_enet_(get|set)_settings
> returns -19.
I saw the same problem with the FEC driver. From what I recall, it
became
On 2016-04-11 18:29, David Miller wrote:
> 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
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
Hi All,
I traced an issue in which we tried configuring duplex mode and speed in
a systemd-udevd .link file failed with the following error:
"Could not set speed or duplex of eth0 to 0 Mbps (half): No such device"
The FEC driver (fec_main.c) does not initialize phy_dev until the device
has been