[PATCH] ARM: zii-rdu2: disable eth0 and eth1

Lucas Stach l.stach at pengutronix.de
Tue Jun 11 11:02:48 PDT 2019

Hi Vivien,

Am Dienstag, den 11.06.2019, 10:46 -0400 schrieb Vivien Didelot:
> Hi Lucas,
> On Tue, 11 Jun 2019 13:45:13 +0200, Lucas Stach <l.stach at pengutronix.de> wrote:
> > Am Montag, den 10.06.2019, 11:58 -0400 schrieb Vivien Didelot:
> > > The current support for the ZII RDU2 Board times out on eth0 and eth1
> > > when booting 'net' from an alternative interface, like a USB Ethernet
> > > dongle. eth0 is the DSA master interface and has no use within barebox,
> > > as well as the gigabit interface eth1 which is wired to the switch
> > > port 0. Disable them to allow Barebox to boot right away from network.
> > 
> > NACK.
> > 
> > With the just merged patches to the RDU2 environment the FEC interface
> > is fully usable for regular network boot, which is what I use for my
> > development setups.
> Do you mean we can now use one of netleft, netaux or netright to tftpboot?

The default switch config on my units is pass-through. I don't know if
this is true for all units, it may have changed at some point. The
patches in barebox/next make sure that the switch is reset when trying
to bring the network interface up. With this configuration you can use
any of the netleft/netright/netaux connectors to do regular netboot.

> > As USB network boot requires additional hardware, I would say it's fair
> > to require to change the environment on the boards used for DSA
> > development.
> I'd certainly agree with that if booting from a DSA slave is now possible.

For DSA development you will still need a USB network dongle, but for
all development that hasn't to do with the ethernet switch, netbooting
from Barebox works fine with the default configuration.


More information about the barebox mailing list