From: Lucas Stach <l.stach@pengutronix.de>
To: Vivien Didelot <vivien.didelot@gmail.com>, barebox@lists.infradead.org
Cc: Andrey Smirnov <andrew.smirnov@gmail.com>
Subject: Re: [PATCH] ARM: zii-rdu2: disable eth0 and eth1
Date: Tue, 11 Jun 2019 13:45:13 +0200 [thread overview]
Message-ID: <429f1bb0f0ae5c86d2d11be2e105eb5de6f59d1d.camel@pengutronix.de> (raw)
In-Reply-To: <20190610155835.18304-1-vivien.didelot@gmail.com>
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
next prev parent reply other threads:[~2019-06-11 11:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-10 15:58 Vivien Didelot
2019-06-11 6:24 ` Andrey Smirnov
2019-06-11 11:45 ` Lucas Stach [this message]
2019-06-11 14:46 ` Vivien Didelot
2019-06-11 18:02 ` Lucas Stach
2019-06-11 18:11 ` Vivien Didelot
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=429f1bb0f0ae5c86d2d11be2e105eb5de6f59d1d.camel@pengutronix.de \
--to=l.stach@pengutronix.de \
--cc=andrew.smirnov@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=vivien.didelot@gmail.com \
/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