Scott,

> On Jul 27, 2015, at 11:33 PM, Fujinaka, Todd <todd.fujin...@intel.com> wrote:
> 
> That's a known issue and we have a fix for it.

However, that fix will not be released until version 4.2.x of the driver is 
released.

> I think whoever wrote the readme was being optimistic about building on 4.1.2 
> because certainly, it doesn't.

Yes, it certainly doesn't and that was my mistake. I can confirm that it does 
not build with kernel versions 4.1.x. I have also verified that it does build 
on 4.0.9 and have updated the readme.txt accordingly.

<snip>

> I'll try to get the readme fixed (and renamed to README so we don't have to 
> download it to read it).

I tried calling it readme.txt, README.txt and README.TXT and the site never 
displays it, contrary to its documentation which indicates that any of them 
should have been picked up. Also the file is not marked executable, which is 
what we had thought was preventing it from being displayed. I think SourceForge 
is just broken.

> If you can tell us what the options you need are, we can tell you how they 
> map to ethtool. Not all do, but we can see


Todd's advice to try to use the ethtool interfaces on recent kernels is good 
advice. At some point in the future, the SourceForge driver will no longer be 
updated for new kernels as is the case now for some old drivers. At that point 
there will be no other option than to use the ethtool interface. Right now you 
can at least control when to switch interfaces while both options are possible. 
By the way, the SourceForge driver should support both ways, so it is possible 
to switch interfaces without simultaneously switching drivers.

--
Mark Rustad, Networking Division, Intel Corporation

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

------------------------------------------------------------------------------
_______________________________________________
E1000-devel mailing list
E1000-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel&#174; Ethernet, visit 
http://communities.intel.com/community/wired

Reply via email to