From: Andrew Lunn <andrew@lunn.ch>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH v3] net: e1000e: add MAC address kernel cmd line parameter
Date: Thu, 28 Feb 2019 16:32:45 +0100 [thread overview]
Message-ID: <20190228153245.GA17912@lunn.ch> (raw)
In-Reply-To: <1551361951-1595-1-git-send-email-f.suligoi@asem.it>
On Thu, Feb 28, 2019 at 02:52:31PM +0100, Flavio Suligoi wrote:
> Sometimes, in some embedded systems boards (i.e. ARM boards),
> the NVM eeprom is not mounted, to save cost and space.
>
> In this case it is necessary to bypass the NVM management
> and directly force the MAC address using a kernel command-line
> parameter (macaddr).
Hi Flavio
Why not use device tree, since this is an ARM platform?
Andrew
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Lunn <andrew@lunn.ch>
To: Flavio Suligoi <f.suligoi@asem.it>
Cc: Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
"David S . Miller" <davem@davemloft.net>,
intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] net: e1000e: add MAC address kernel cmd line parameter
Date: Thu, 28 Feb 2019 16:32:45 +0100 [thread overview]
Message-ID: <20190228153245.GA17912@lunn.ch> (raw)
In-Reply-To: <1551361951-1595-1-git-send-email-f.suligoi@asem.it>
On Thu, Feb 28, 2019 at 02:52:31PM +0100, Flavio Suligoi wrote:
> Sometimes, in some embedded systems boards (i.e. ARM boards),
> the NVM eeprom is not mounted, to save cost and space.
>
> In this case it is necessary to bypass the NVM management
> and directly force the MAC address using a kernel command-line
> parameter (macaddr).
Hi Flavio
Why not use device tree, since this is an ARM platform?
Andrew
next prev parent reply other threads:[~2019-02-28 15:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-28 9:20 [PATCH] net: e1000e: add MAC address kernel cmd line parameter Flavio Suligoi
2019-02-28 13:38 ` [Intel-wired-lan] [PATCH v2] " Flavio Suligoi
2019-02-28 13:38 ` Flavio Suligoi
2019-02-28 13:52 ` [Intel-wired-lan] [PATCH v3] " Flavio Suligoi
2019-02-28 13:52 ` Flavio Suligoi
2019-02-28 15:32 ` Andrew Lunn [this message]
2019-02-28 15:32 ` Andrew Lunn
2019-02-28 15:51 ` [Intel-wired-lan] " Flavio Suligoi
2019-02-28 15:51 ` Flavio Suligoi
2019-02-28 16:37 ` [Intel-wired-lan] " Andrew Lunn
2019-02-28 16:37 ` Andrew Lunn
2019-02-28 17:13 ` [Intel-wired-lan] " Flavio Suligoi
2019-02-28 17:13 ` Flavio Suligoi
2019-02-28 19:29 ` [Intel-wired-lan] " Andrew Lunn
2019-02-28 19:29 ` Andrew Lunn
2019-02-28 19:47 ` [Intel-wired-lan] " David Miller
2019-02-28 19:47 ` David Miller
2019-03-01 8:15 ` [Intel-wired-lan] " Flavio Suligoi
2019-03-01 8:15 ` Flavio Suligoi
2019-02-28 18:21 ` [Intel-wired-lan] [PATCH] " David Miller
2019-02-28 18:21 ` David Miller
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=20190228153245.GA17912@lunn.ch \
--to=andrew@lunn.ch \
--cc=intel-wired-lan@osuosl.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.