I think "everything else" is what I was thinking you should have the NDA for.
MACsec is an easier answer: there's no Linux support because no one ever asked
for it.
Todd Fujinaka
Software Application Engineer
Networking Division (ND)
Intel Corporation
[email protected]
(503) 712-4565
From: x aus [mailto:[email protected]]
Sent: Wednesday, March 26, 2014 12:38 PM
To: Fujinaka, Todd
Cc: [email protected]
Subject: Re: [E1000-devel] 82576/igb custom driver
We had NDA in place, other than the MACSEC item(#6), which item do you think
should better go to Intel too?
The response from Intel has been a little slow so far.
Thanks for your help,
Joe
On Wed, Mar 26, 2014 at 1:31 PM, Fujinaka, Todd
<[email protected]<mailto:[email protected]>> wrote:
I think some of these questions would be best answered under NDA. Can you
contact your vendor and go through that channel?
Thanks.
Todd Fujinaka
Software Application Engineer
Networking Division (ND)
Intel Corporation
[email protected]<mailto:[email protected]>
(503) 712-4565<tel:%28503%29%20712-4565>
-----Original Message-----
From: x aus [mailto:[email protected]<mailto:[email protected]>]
Sent: Wednesday, March 26, 2014 11:20 AM
To: [email protected]<mailto:[email protected]>
Subject: [E1000-devel] 82576/igb custom driver
We're using 82576 on a main board(ARM with PCIe x1) using 3.0.x kernel. I can
probe the device at the moment.
I'm connecting the 82576 to a SFP which has an I2C for the external PHY(RJ45),
I also have EEPROM and SPI-Flash connected via SPI to 82576 based on Intel's
reference schematics.
I have a list of questions:
1. We're using SerDes to connect with the SFP, it's unclear to me per the
Datasheet that, should we use SGMII instead? what's the key difference here?
We're using RJ45/SFP but we may need use fiber/SFP later, which is the reason
we're not using the internal PHY. I saw there are some code for SFP inside the
igb driver.
2. On the EEPROM, do we have to use it? I think igb is getting deviceID from
the EEPROM, as 'lspci -v' showed 10c9:0000 now, the EEPROM is blank at the
moment, and I modified the code to bypass the MAC-address-reading from
EEPROM(providing some fake MACs for now) so I can run 'ifconfig eth0 up'
against it though I can never send out packets.
2.1 Is it possible at all the get this working without using EEPROM?
3. How to program the blank EEPROM, can I use ethtool do that? or do I have to
take it out and program it before solder it down?
4. When do I need SPI-Flash? do I need it at all? The datasheet says it can
hold some firmware but I'm not sure what it means.
5. From e1000_hw.h, 0x10C9 is for 82576 itself, the rest is for the specific
products, but what's the difference between Fiber, Serdes, copper?
In my case I use SFP/RJ45, is it more like Serdes or Copper or even RGMII(there
is aE1000_DEV_ID_I350_SGMII) , very confused.
#define E1000_DEV_ID_82576 0x10C9
#define E1000_DEV_ID_82576_FIBER 0x10E6
#define E1000_DEV_ID_82576_SERDES 0x10E7
#define E1000_DEV_ID_82576_QUAD_COPPER 0x10E8
#define E1000_DEV_ID_82576_QUAD_COPPER_ET2 0x1526
#define E1000_DEV_ID_82576_SERDES_QUAD 0x150D
6. I don't see MACSEC code in the driver, is it implemented at Intel but just
not open sourced? The Intel representative is unclear on that either.
Basically I need confirm SerDes or RGMII for SFP, then learn how to modify the
driver and program EEPROM to get 82576 working on the custom design.
Any tips/suggestions are great appreciated!
Thanks a lot.
Joe
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
_______________________________________________
E1000-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel® Ethernet, visit
http://communities.intel.com/community/wired
