mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: "Schenk, Gavin" <G.Schenk@eckelmann.de>
To: "s.hauer@pengutronix.de" <s.hauer@pengutronix.de>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: AW: [PATCH] Configure network device for nfsboot via nv var
Date: Thu, 16 Nov 2017 07:20:14 +0000	[thread overview]
Message-ID: <1510816812.1406.2.camel@eckelmann.de> (raw)
In-Reply-To: <20171110070008.p6gsmknadybwq6ug@pengutronix.de>

Hi,

> On Wed, Nov 08, 2017 at 04:05:17PM +0100, Gavin Schenk wrote:
> > When you have a static network environment but more than one
> > network
> > device on your machine it is necessary to provide the <device>
> > parameter to the ip parameter at kernel cmd line.
> > 
> > The device name assigned by Linux cannot in general be predicted as
> > it
> > depends on driver bind order.
> > 
> > This patch introduces a new global variable
> > "global.linux.nfsroot.device" which when set is feed to the ip=
> > kernel
> > parameter as device name.
> 
> Maybe we should rather add a linuxname property to the ethernet
> device
> instead. That way we could specify multiple names in case we have
> multiple ethernet devices in barebox aswell.
> 

maybe I am missing something important, but is this useful for anything
besides nfsboot?

If linuxname is a property of the device, how do we decide between
eth0.linuxname and eth1.linuxname when doing a "boot /mnt/nfs"? 
In this case we need additionally a global variable like nfsboot-
device=eth0 to switch between nfsboot devices and to make the decision
when filling the ip parameter?

Best regards
Gavin

Eckelmann AG
Vorstand: Dipl.-Ing. Peter Frankenbach (Sprecher) Dipl.-Wi.-Ing. Philipp Eckelmann
Dr.-Ing. Marco Münchhof Dr.-Ing. Frank Uhlemann
Vorsitzender des Aufsichtsrats: Hubertus G. Krossa
Stv. Vorsitzender des Aufsichtsrats: Dr.-Ing. Gerd Eckelmann
Sitz der Gesellschaft: Berliner Str. 161, 65205 Wiesbaden, Amtsgericht Wiesbaden HRB 12636
http://www.eckelmann.de 

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

  reply	other threads:[~2017-11-16  7:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-08 15:05 Gavin Schenk
2017-11-10  7:00 ` Sascha Hauer
2017-11-16  7:20   ` Schenk, Gavin [this message]
2017-11-17  9:26     ` Uwe Kleine-König
2017-11-17  9:32     ` s.hauer

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=1510816812.1406.2.camel@eckelmann.de \
    --to=g.schenk@eckelmann.de \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@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