From: Bob Ham <bob.ham@collabora.com>
To: Stefan Agner <stefan@agner.ch>,
systemd-devel@lists.freedesktop.org, netdev@vger.kernel.org,
davem@davemloft.net
Cc: fabio.estevam@freescale.com, bryan.wu@canonical.com,
u.kleine-koenig@pengutronix.de, l.stach@pengutronix.de
Subject: Re: Configuring ethernet link fails with No such device
Date: Tue, 12 Apr 2016 09:58:12 +0100 [thread overview]
Message-ID: <1460451492.6333.6.camel@collabora.com> (raw)
In-Reply-To: <67b662523c63277fa95a59472cbf018f@agner.ch>
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 clear that there was a problem with the driver returning from
the eth device initialisation before the PHY was initialised, which
apparently is Bad and Wrong.
> 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 link-level settings.
--
Bob Ham <bob.ham@collabora.com>
Software Engineer
>>>>>>>>
Open First
Collabora is hiring!
Please check out our latest opportunities here:
http://bit.ly/Collabora-Careers
<<<<<<<<
_______________________________________________
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
next prev parent reply other threads:[~2016-04-12 8:58 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
2016-04-12 8:58 ` Bob Ham [this message]
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=1460451492.6333.6.camel@collabora.com \
--to=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=stefan@agner.ch \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.