From: John Holland <jotihojr@gmail.com>
To: intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org
Subject: Re: [Intel-wired-lan] [next] igb: allow setting MAC address on i211 using a device tree blob V5
Date: Thu, 18 Feb 2016 14:43:59 +0100 [thread overview]
Message-ID: <56C5CA9F.3000102@gmail.com> (raw)
In-Reply-To: <56C5A6BC.6030708@gmail.com>
On 02/18/2016 12:10 PM, John Holland wrote:
> Hello,
>
> The Intel i211 LOM PCIe Ethernet controllers' iNVM operates as an OTP
> and has no external EEPROM interface [1]. The following allows the
> driver to pickup the MAC address from a device tree blob when CONFIG_OF
> has been enabled.
>
> + if (eth_platform_get_mac_address(&pdev->dev, hw->mac.addr)) {
For later reference, putting all necessary information in one place.
This requires the dtb for the mac address routing to be properly
positioned. On an imx6q using U-Boot, that required setting the U-Boot
environment variable eth1addr and reworking the PCIe tree and allocating
an alias as such:
1) Set intel,i211 MAC address.
# env set eth1addr <valid-mac-address>
2) Add an alias to pick up the MAC address from U-Boot and route it to
the intel,i211 PCIe endpoint for an imx6qdl derivative.
/ {
aliases {
ethernet1 = ð1;
};
};
&pcie {
/* soc pcie bridge 00:00.0 */
pcie@0,0 {
reg = <0x000000 0 0 0 0>;
#address-cells = <3>;
#size-cells = <2>;
/* pcie endpoint 01:00.0 */
eth1: intel,i211@pcie0,0 {
reg = <0x010000 0 0 0 0>;
};
};
};
John
next prev parent reply other threads:[~2016-02-18 13:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-18 11:10 [Intel-wired-lan] [next] igb: allow setting MAC address on i211 using a device tree blob V5 John Holland
2016-02-18 13:43 ` John Holland [this message]
2016-03-01 2:52 ` Brown, Aaron F
2016-03-01 6:56 ` John Holland
2016-03-01 23:23 ` Brown, Aaron F
2016-03-01 23:55 ` Jeff Kirsher
2016-03-02 3:48 ` John Holland
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=56C5CA9F.3000102@gmail.com \
--to=jotihojr@gmail.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=netdev@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).