On Fri, 18 Nov 2005, Jeff Garzik wrote:
> Our position is users who need the new hardware support or new features
> now can download our driver tarball from sf.net/projects/e1000.
This position causes extra work, a split test base, and constant
mini-forks whenever e1000 patches come in from the
Jesse Brandeburg wrote:
We choose 1) Please merge these changes into upstream for 2.6.16, we
realize we missed the merge window for 2.6.15, but should have said so.
ok
Our position is users who need the new hardware support or new features
now can download our driver tarball from sf.net/pro
On Fri, 18 Nov 2005, Jeff Garzik wrote:
> e1000 driver update
>
> Signed-off-by: Jeff Kirsher <[EMAIL PROTECTED]>
> Signed-off-by: John Ronciak <[EMAIL PROTECTED]>
> Signed-off-by: Jesse Brandeburg <[EMAIL PROTECTED]>
Grumble! How many times has Intel been told to order fixes before new
feature
Jeff Kirsher wrote:
e1000 driver update
Signed-off-by: Jeff Kirsher <[EMAIL PROTECTED]>
Signed-off-by: John Ronciak <[EMAIL PROTECTED]>
Signed-off-by: Jesse Brandeburg <[EMAIL PROTECTED]>
Grumble! How many times has Intel been told to order fixes before new
features?
I have multiple Intel
e1000 driver update
Signed-off-by: Jeff Kirsher <[EMAIL PROTECTED]>
Signed-off-by: John Ronciak <[EMAIL PROTECTED]>
Signed-off-by: Jesse Brandeburg <[EMAIL PROTECTED]>
1. Fixes for 8257x
- TSO workaround
- Fixes eeprom version reporting
- Fix loopback test
- Fix for WOL
2. Performanc
