mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Vivien Didelot <vivien.didelot@gmail.com>
To: Lucas Stach <l.stach@pengutronix.de>
Cc: Andrey Smirnov <andrew.smirnov@gmail.com>, barebox@lists.infradead.org
Subject: Re: [PATCH] ARM: zii-rdu2: disable eth0 and eth1
Date: Tue, 11 Jun 2019 10:46:03 -0400	[thread overview]
Message-ID: <20190611104603.GC6199@t480s.localdomain> (raw)
In-Reply-To: <429f1bb0f0ae5c86d2d11be2e105eb5de6f59d1d.camel@pengutronix.de>

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

  reply	other threads:[~2019-06-11 14:46 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
2019-06-11 14:46   ` Vivien Didelot [this message]
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=20190611104603.GC6199@t480s.localdomain \
    --to=vivien.didelot@gmail.com \
    --cc=andrew.smirnov@gmail.com \
    --cc=barebox@lists.infradead.org \
    --cc=l.stach@pengutronix.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