From: Stefan Agner <stefan@agner.ch>
To: David Miller <davem@davemloft.net>
Cc: systemd-devel@lists.freedesktop.org, netdev@vger.kernel.org,
fabio.estevam@freescale.com, l.stach@pengutronix.de,
u.kleine-koenig@pengutronix.de, bryan.wu@canonical.com,
bob.ham@collabora.com
Subject: Re: Configuring ethernet link fails with No such device
Date: Tue, 12 Apr 2016 00:25:02 -0700 [thread overview]
Message-ID: <ed0d524976663f40412b1852e16099f8@agner.ch> (raw)
In-Reply-To: <20160411.212900.1164760179761034053.davem@davemloft.net>
On 2016-04-11 18:29, David Miller wrote:
> From: Stefan Agner <stefan@agner.ch>
> 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 when it is not open, so we wouldn't be able to
> properly do link settings even if we wanted to when the device is
> closed.
I see. Afact it is a udev rule which triggers the built-in link setup
code:
https://github.com/systemd/systemd/blob/09541e49ebd17b41482e447dd8194942f39788c0/rules/80-net-setup-link.rules
The udev rule is triggering on action add (=> probe on driver level). At
least on the device I tested, it seems that there is no event on open...
Any other ideas what could be used as trigger to configure the link?
next prev parent reply other threads:[~2016-04-12 7:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-11 22:46 Configuring ethernet link fails with No such device Stefan Agner
2016-04-11 23:10 ` Florian Fainelli
2016-04-12 1:29 ` David Miller
2016-04-12 7:25 ` Stefan Agner [this message]
2016-04-12 8:58 ` Bob Ham
2016-04-12 15:44 ` David Miller
2016-04-13 1:29 ` Stefan Agner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ed0d524976663f40412b1852e16099f8@agner.ch \
--to=stefan@agner.ch \
--cc=bob.ham@collabora.com \
--cc=bryan.wu@canonical.com \
--cc=davem@davemloft.net \
--cc=fabio.estevam@freescale.com \
--cc=l.stach@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=systemd-devel@lists.freedesktop.org \
--cc=u.kleine-koenig@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).