From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC PATCH] net: rtl8169: allow multiple devices
Date: Mon, 25 Apr 2016 10:43:16 -0600 [thread overview]
Message-ID: <571E4924.1030908@wwwdotorg.org> (raw)
In-Reply-To: <1461195110-11119-1-git-send-email-swarren@wwwdotorg.org>
On 04/20/2016 05:31 PM, Stephen Warren wrote:
> From: Stephen Warren <swarren@nvidia.com>
>
> Currently, if multiple rtl8169 devices exist on the PCI bus, they all
> get the same name, which prevents the user from selecting which to use
> via the ethact environment variable. Port the auto-naming code from the
> e1000 driver to solve this.
>
> Signed-off-by: Stephen Warren <swarren@nvidia.com>
> ---
> Having to put this code into each Ethernet driver seems a bit odd. Surely
> the core should handle this; should eth_get_dev_by_name() parse "#n" out
> of the ethact value and compare it to the device sequence number?
>
> It looks like I should be able to set ethprime to e.g. eth0, eth1, etc.
> and this should work. However, I couldn't get ethprime to behave sensibly,
> and I'm not sure what its semantics are supposed to be. Specifically,
> ethprime seems to only be used if ethact isn't set, yet accessing the
> network (e.g. running "dhcp zImage") seems to set ethact, thus preventing
> any further modification to ethprime from having any effect. Equally,
> simply running e.g. "dhcp zImage" twice in a row doesn't seem to work;
> perhaps the subsequent attempts perform another lookup by name from ethact
> rather than just using the same device pointer from before? Is ethprime
> intended to be functional at present, or is it some legacy feature that's
> bit-rotted and should be removed?
Simon, Joe, any thoughts on those questions re: this patch?
next prev parent reply other threads:[~2016-04-25 16:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-20 23:31 [U-Boot] [RFC PATCH] net: rtl8169: allow multiple devices Stephen Warren
2016-04-25 16:43 ` Stephen Warren [this message]
2016-04-25 17:08 ` Joe Hershberger
2016-04-26 16:53 ` Stephen Warren
2016-04-26 17:14 ` Stephen Warren
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=571E4924.1030908@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=u-boot@lists.denx.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