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

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

[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.

Signed-off-by: Vivien Didelot <vivien.didelot@gmail.com>
---
 arch/arm/boards/zii-imx6q-rdu2/defaultenv-rdu2/nv/dev.eth0.mode | 1 +
 arch/arm/boards/zii-imx6q-rdu2/defaultenv-rdu2/nv/dev.eth1.mode | 1 +
 2 files changed, 2 insertions(+)
 create mode 100644 arch/arm/boards/zii-imx6q-rdu2/defaultenv-rdu2/nv/dev.eth0.mode
 create mode 100644 arch/arm/boards/zii-imx6q-rdu2/defaultenv-rdu2/nv/dev.eth1.mode

diff --git a/arch/arm/boards/zii-imx6q-rdu2/defaultenv-rdu2/nv/dev.eth0.mode b/arch/arm/boards/zii-imx6q-rdu2/defaultenv-rdu2/nv/dev.eth0.mode
new file mode 100644
index 000000000..87e7bdaae
--- /dev/null
+++ b/arch/arm/boards/zii-imx6q-rdu2/defaultenv-rdu2/nv/dev.eth0.mode
@@ -0,0 +1 @@
+disabled
\ No newline at end of file
diff --git a/arch/arm/boards/zii-imx6q-rdu2/defaultenv-rdu2/nv/dev.eth1.mode b/arch/arm/boards/zii-imx6q-rdu2/defaultenv-rdu2/nv/dev.eth1.mode
new file mode 100644
index 000000000..87e7bdaae
--- /dev/null
+++ b/arch/arm/boards/zii-imx6q-rdu2/defaultenv-rdu2/nv/dev.eth1.mode
@@ -0,0 +1 @@
+disabled
\ No newline at end of file
-- 
2.21.0


_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

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

[Andrey Smirnov]

On Mon, Jun 10, 2019 at 8:59 AM Vivien Didelot <vivien.didelot@gmail.com> wrote:
>
> 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.
>

I personally don't have any preference as far as this is concerned,
since I usually override all of those settings and disable DSA in the
switch anyway. However we might want to wait to hear back from Lucas
or other folks at Pengutronix who dealt with RDU2, since this patch
might go against how they use it.

Thanks,
Andrey Smirnov

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

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

[Lucas Stach]

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.

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.

Regards,
Lucas

> Signed-off-by: Vivien Didelot <vivien.didelot@gmail.com>
> ---
>  arch/arm/boards/zii-imx6q-rdu2/defaultenv-rdu2/nv/dev.eth0.mode | 1 +
>  arch/arm/boards/zii-imx6q-rdu2/defaultenv-rdu2/nv/dev.eth1.mode | 1 +
>  2 files changed, 2 insertions(+)
>  create mode 100644 arch/arm/boards/zii-imx6q-rdu2/defaultenv-rdu2/nv/dev.eth0.mode
>  create mode 100644 arch/arm/boards/zii-imx6q-rdu2/defaultenv-rdu2/nv/dev.eth1.mode
> 
> diff --git a/arch/arm/boards/zii-imx6q-rdu2/defaultenv-rdu2/nv/dev.eth0.mode b/arch/arm/boards/zii-imx6q-rdu2/defaultenv-rdu2/nv/dev.eth0.mode
> new file mode 100644
> index 000000000..87e7bdaae
> --- /dev/null
> +++ b/arch/arm/boards/zii-imx6q-rdu2/defaultenv-rdu2/nv/dev.eth0.mode
> @@ -0,0 +1 @@
> +disabled
> \ No newline at end of file
> diff --git a/arch/arm/boards/zii-imx6q-rdu2/defaultenv-rdu2/nv/dev.eth1.mode b/arch/arm/boards/zii-imx6q-rdu2/defaultenv-rdu2/nv/dev.eth1.mode
> new file mode 100644
> index 000000000..87e7bdaae
> --- /dev/null
> +++ b/arch/arm/boards/zii-imx6q-rdu2/defaultenv-rdu2/nv/dev.eth1.mode
> @@ -0,0 +1 @@
> +disabled
> \ No newline at end of file


_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

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

[Vivien Didelot]

Hi Lucas,

On Tue, 11 Jun 2019 13:45:13 +0200, Lucas Stach <l.stach@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?

> 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.


Thanks,
Vivien

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

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

[Lucas Stach]

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@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.

Regards,
Lucas


_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

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

[Vivien Didelot]

Hi Lucas,

On Tue, 11 Jun 2019 20:02:48 +0200, Lucas Stach <l.stach@pengutronix.de> wrote:
> > > 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.

For that reason I agree with you to keep this patch out-of-tree.


Thank you,
Vivien

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox