linux.git/drivers/net/e1000e/netdev.c, branch v2.6.28

driver/net/*: remove redundant argument comments

2008-11-23T23:46:55+00:00

remove redundant argument comments in files of drivers/net/*

Signed-off-by: Qinghuang Feng 
Signed-off-by: David S. Miller

e1000e: fix IPMI traffic

2008-11-17T03:05:16+00:00

Some users reported that they have machines with BMCs enabled that cannot
receive IPMI traffic after e1000e is loaded.
http://marc.info/?l=e1000-devel&m=121909039127414&w=2
http://marc.info/?l=e1000-devel&m=121365543823387&w=2

This fixes the issue if they load with the new parameter = 0 by disabling
crc stripping, but leaves the performance feature on for most users.
Based on work done by Hong Zhang.

Signed-off-by: Jeff Kirsher 
Signed-off-by: Jesse Brandeburg 
Signed-off-by: David S. Miller

e1000e: fix warn_on reload after phy_id error

2008-11-17T03:05:02+00:00

If the driver fails to initialize the first time due to the failure in the
phy_id check the kernel triggers a warn_on on the second try to load the
driver because the driver did not free the msi/x resources in the first
load because of the previous failure in phy_id check.

Signed-off-by: Jeff Kirsher 
Signed-off-by: David S. Miller

e1000e: Use device_set_wakeup_enable

2008-11-16T09:35:45+00:00

Since dev->power.should_wakeup bit is used by the PCI core to
decide whether the device should wake up the system from sleep
states, set/unset this bit whenever WOL is enabled/disabled using
e1000_set_wol().  Accordingly, use device_can_wakeup() for checking
if wake-up is supported by the device.

Signed-off-by: "Rafael J. Wysocki" 
Signed-off-by: Jeff Kirsher 
Signed-off-by: David S. Miller

e1000e: don't generate bad checksums for tcp packets with 0 csum

2008-10-09T21:28:58+00:00

When offloading transmit checksums only, the driver was not
correctly configuring the hardware to handle the case of a zero
checksum.  For UDP the correct behavior is to leave it alone, but
for tcp the checksum must be changed from 0x0000 to 0xFFFF.  The
hardware takes care of this case but only if it is told the
packet is tcp.

Signed-off-by: Dave Graham 
Signed-off-by: Jesse Brandeburg 
Signed-off-by: Jeff Kirsher 
Signed-off-by: David S. Miller

Merge branch 'master' of master.kernel.org:/pub/scm/linux/kernel/git/davem/net-2.6

2008-10-08T21:56:41+00:00

Conflicts:

	drivers/net/e1000e/ich8lan.c
	drivers/net/e1000e/netdev.c

e1000e: update version from k4 to k6

2008-10-03T01:28:13+00:00

Signed-off-by: Jesse Brandeburg 
Signed-off-by: Linus Torvalds

e1000e: drop stats lock

2008-10-03T01:28:12+00:00

the stats lock is left over from e1000, e1000e no longer
has the adjust tbi stats function that required the addition
of the stats lock to begin with.

adding a mutex to acquire_swflag helped catch this one too.

Signed-off-by: Jesse Brandeburg 
Acked-by: Thomas Gleixner 
Signed-off-by: Linus Torvalds

e1000e: remove phy read from inside spinlock

2008-10-03T01:28:12+00:00

thanks to tglx, we're finding some interesting reentrancy issues.
this patch removes the phy read from inside a spinlock, paving
the way for removing the spinlock completely.  The phy read was
only feeding a statistic that wasn't used.

Signed-off-by: Jesse Brandeburg 
Acked-by: Thomas Gleixner 
Signed-off-by: Linus Torvalds

e1000e: do not ever sleep in interrupt context

2008-10-03T01:28:12+00:00

e1000e was apparently calling two functions that attempted to reserve
the SWFLAG bit for exclusive (to hardware and firmware) access to
the PHY and NVM (aka eeprom).  These accesses could possibly call
msleep to wait for the resource which is not allowed from interrupt
context.

Signed-off-by: Jesse Brandeburg 
Acked-by: Thomas Gleixner 
Tested-by: Thomas Gleixner 
Signed-off-by: Linus Torvalds