Re: [U-Boot] [RFC PATCH] net: rtl8169: allow multiple devices

2016-04-26 Thread Stephen Warren
On 04/26/2016 10:53 AM, Stephen Warren wrote: On 04/25/2016 11:08 AM, Joe Hershberger wrote: Hi Stephen, On Wed, Apr 20, 2016 at 6:31 PM, Stephen Warren wrote: From: Stephen Warren Currently, if multiple rtl8169 devices exist on the PCI bus, they all get the same name, which prevents the us

Re: [U-Boot] [RFC PATCH] net: rtl8169: allow multiple devices

2016-04-26 Thread Stephen Warren
On 04/25/2016 11:08 AM, Joe Hershberger wrote: Hi Stephen, On Wed, Apr 20, 2016 at 6:31 PM, Stephen Warren wrote: From: Stephen Warren 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 e

Re: [U-Boot] [RFC PATCH] net: rtl8169: allow multiple devices

2016-04-25 Thread Joe Hershberger
Hi Stephen, On Wed, Apr 20, 2016 at 6:31 PM, Stephen Warren wrote: > From: Stephen Warren > > 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

Re: [U-Boot] [RFC PATCH] net: rtl8169: allow multiple devices

2016-04-25 Thread Stephen Warren
On 04/20/2016 05:31 PM, Stephen Warren wrote: From: Stephen Warren 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

[U-Boot] [RFC PATCH] net: rtl8169: allow multiple devices

2016-04-20 Thread Stephen Warren
From: Stephen Warren 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 ---