mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Gavin Schenk <g.schenk@eckelmann.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] Add linux.devname property to eth device
Date: Thu, 23 Nov 2017 08:51:41 +0100	[thread overview]
Message-ID: <20171123075141.in7vc75sqlho7vvy@pengutronix.de> (raw)
In-Reply-To: <20171121154047.27334-1-g.schenk@eckelmann.de>

On Tue, Nov 21, 2017 at 04:40:47PM +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 property linux.devname to eth devices.
> The value is added to bootargs per interface and can be changed in
> env/network/INTF
> 
> Note that the device name is also used when dhcp is in use.
> 
> Signed-off-by: Gavin Schenk <g.schenk@eckelmann.de>
> ---
> 
> This is V2 of "[PATCH] Configure network device for nfsboot via nv var"

After first thinking that the former patch was a good idea, seeing this
now I agree with Sascha this new approach is better.

Maybe add the following (in a separate commit?):

diff --git a/defaultenv/defaultenv-2-base/network/eth0 b/defaultenv/defaultenv-2-base/network/eth0
index 33fe7c1b2b48..992e37a35deb 100644
--- a/defaultenv/defaultenv-2-base/network/eth0
+++ b/defaultenv/defaultenv-2-base/network/eth0
@@ -13,6 +13,10 @@ serverip=
 # MAC address if needed
 #ethaddr=xx:xx:xx:xx:xx:xx
 
+# device name under Linux (needed for static setups with more than
+# one network adapter)
+#linuxdevname=eth0
+
 # put code to discover eth0 (i.e. 'usb') to /env/network/eth0-discover
 
 exit 0

Other than that:

Acked-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>

Thanks
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

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

  reply	other threads:[~2017-11-23  7:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-21 15:40 Gavin Schenk
2017-11-23  7:51 ` Uwe Kleine-König [this message]
2017-11-24  8:15 ` Sascha 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=20171123075141.in7vc75sqlho7vvy@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=g.schenk@eckelmann.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