From: John Holland <hidden> Date: 2016-01-29 22:11:55
The Intel i211 LOM pcie ethernet controllers' iNVM operates as an OTP
and has no externel EEPROM interface [1]. The following allows the
driver to pickup the MAC address from a device tree blob when CONFIG_OF
has been enabled.
[1]
http://www.intel.com/content/www/us/en/embedded/products/networking/i211-ethernet-controller-datasheet.html
Signed-off-by: John Holland <redacted>
---
drivers/net/ethernet/intel/igb/igb_main.c | 30
++++++++++++++++++++++++++++++
1 file changed, 30 insertions(+)
From: Jeff Kirsher <hidden> Date: 2016-02-09 11:02:31
On Fri, 2016-01-29 at 23:11 +0100, John Holland wrote:
quoted hunk
The Intel i211 LOM pcie ethernet controllers' iNVM operates as an
OTP
and has no externel EEPROM interface [1]. The following allows the
driver to pickup the MAC address from a device tree blob when
CONFIG_OF
has been enabled.
[1]
http://www.intel.com/content/www/us/en/embedded/products/networking/i
211-ethernet-controller-datasheet.html
Signed-off-by: John Holland <redacted>
---
drivers/net/ethernet/intel/igb/igb_main.c | 30
++++++++++++++++++++++++++++++
1 file changed, 30 insertions(+)
Hi John
Would this also work for the i210?
If so, you normally use the compatible string for the first device
this works with. So maybe this should be changed to intel,i210?
Thanks
Andrew
Humm, NULL, NULL. That means find the first node anywhere in the
device tree which matches. This is not going to work too well when you
have multiple i211s.
There is a way so specify a DT node is attached to a specific PCIe
bus/slot. I think you should search only there, so solving the
multiple device issue.
Andrew
From: Shannon Nelson <hidden> Date: 2016-02-09 17:42:46
It seem to me this should be using eth_platform_get_mac_address(), a
slightly more generic method to do this. See the i40e driver for an
example, commit d9a84324e6 I believe.
sln
On Tue, Feb 9, 2016 at 3:59 AM, Andrew Lunn [off-list ref] wrote:
Humm, NULL, NULL. That means find the first node anywhere in the
device tree which matches. This is not going to work too well when you
have multiple i211s.
There is a way so specify a DT node is attached to a specific PCIe
bus/slot. I think you should search only there, so solving the
multiple device issue.
Andrew
--
==============================================
Mr. Shannon Nelson Network Division, Intel Corp.
Shannon.Nelson@intel.com I don't speak for Intel
Parents can't afford to be squeamish
From: David Miller <davem@davemloft.net> Date: 2016-02-09 22:10:52
From: Shannon Nelson <redacted>
Date: Tue, 9 Feb 2016 09:42:45 -0800
It seem to me this should be using eth_platform_get_mac_address(), a
slightly more generic method to do this. See the i40e driver for an
example, commit d9a84324e6 I believe.
From: John Holland <hidden> Date: 2016-02-10 08:50:57
On Feb 9, 2016, at 18:42, Shannon Nelson [off-list ref] wrote:
It seem to me this should be using eth_platform_get_mac_address(), a
slightly more generic method to do this. See the i40e driver for an
example, commit d9a84324e6 I believe.
From: John Holland <hidden> Date: 2016-02-10 08:52:50
On Feb 9, 2016, at 12:02, Jeff Kirsher [off-list ref] wrote:
quoted
On Fri, 2016-01-29 at 23:11 +0100, John Holland wrote:
The Intel i211 LOM pcie ethernet controllers' iNVM operates as an
OTP
and has no externel EEPROM interface [1]. The following allows the
driver to pickup the MAC address from a device tree blob when
CONFIG_OF
has been enabled.
[1]
http://www.intel.com/content/www/us/en/embedded/products/networking/i
211-ethernet-controller-datasheet.html
Signed-off-by: John Holland <redacted>
---
drivers/net/ethernet/intel/igb/igb_main.c | 30
++++++++++++++++++++++++++++++
1 file changed, 30 insertions(+)
Humm, NULL, NULL. That means find the first node anywhere in the
device tree which matches. This is not going to work too well when you
have multiple i211s.
There is a way so specify a DT node is attached to a specific PCIe
bus/slot. I think you should search only there, so solving the
multiple device issue.