Dang [mailto:dhd...@apm.com]
>> Sent: Thursday, April 9, 2015 11:58 AM
>> To: Fujinaka, Todd
>> Cc: e1000-devel@lists.sourceforge.net
>> Subject: Re: [E1000-devel] [linux-nics] Arm64 kernel crashes with e1000e
>> driver
>>
>> Hi Fujinaka,
>>
>> As e1
1000-devel] [linux-nics] Arm64 kernel crashes with e1000e
> driver
>
> Hi Fujinaka,
>
> As e1000e product family is nearly end of life. Does Intel have alternative
> options for 1Gb NIC?
>
> Regards,
> Duc Dang.
>
> On Mon, Apr 6, 2015 at 3:35 PM, Fujinaka, Todd
&
I'm not a sales guy, so I'm not sure what to tell you. There are NICs based on
the i350 and i210 and those use the igb driver.
Todd Fujinaka
Software Application Engineer
Networking Division (ND)
Intel Corporation
todd.fujin...@intel.com
(503) 712-4565
-Original Message-
From: Duc Dang [
Hi Fujinaka,
As e1000e product family is nearly end of life. Does Intel have
alternative options for 1Gb NIC?
Regards,
Duc Dang.
On Mon, Apr 6, 2015 at 3:35 PM, Fujinaka, Todd wrote:
> The only documentation I have is what's in the commit bdc125f7 in the kernel.
> I'm assuming you've already l
The only documentation I have is what's in the commit bdc125f7 in the kernel.
I'm assuming you've already looked at the git logs.
It all is predicated by that flag and it appears from the comments and the code
that the flag is only set for the 82579. I'll ask around, but if I'm wrong I'm
sure I
Thanks, Fujinaka.
The comment in E1000E driver (below) says that "on some parts there is
a bug that acknowledges Host accesses later than it should". Do you
know if 82752EI and 82754L have this problem or not?
/**
* __ew32_prepare - prepare to write to MAC CSR register on certain parts
* @hw: p
Unfortunately I think the only suggestion I have is to stick to stable kernels.
We don't have any ARM hardware available so we can't test this locally.
I'm also deleting the laundry-list of cc's because I think I'm the only one on
82574L support on Linux at this time.
Todd Fujinaka
Software App
