linux.git/drivers/net/e100.c, branch v2.6.23

[NET]: ethtool_perm_addr only has one implementation

2007-07-31T21:00:29+00:00

All drivers implement ethtool get_perm_addr the same way -- by calling
the generic function.  So we can inline the generic function into the
caller and avoid going through the drivers.

Signed-off-by: Matthew Wilcox 
Signed-off-by: David S. Miller

PCI: Change all drivers to use pci_device->revision

2007-07-11T23:02:10+00:00

Instead of all drivers reading pci config space to get the revision
ID, they can now use the pci_device->revision member.

This exposes some issues where drivers where reading a word or a dword
for the revision number, and adding useless error-handling around the
read. Some drivers even just read it for no purpose of all.

In devices where the revision ID is being copied over and used in what
appears to be the equivalent of hotpath, I have left the copy code
and the cached copy as not to influence the driver's performance.

Compile tested with make all{yes,mod}config on x86_64 and i386.

Signed-off-by: Auke Kok 
Acked-by: Dave Jones 
Signed-off-by: Greg Kroah-Hartman

e100: Fix Tyan motherboard e100 not receiving IPMI commands

2007-07-10T16:24:43+00:00

The 82550 & 51 parts have an extended configuration block that
includes a bit "GMRC", required to enable the expected TCO behavior,
in config byte offset 22d.  The config block sent by the failing driver
does include the extension area, but this bit is not initialised,
and the downlaod only specifies 0x16 bytes to be sent to the NIC
(thaht's bytes 00..21d). By initializing the GMRC bit, and extending
the download size for D102+ MACs, the problem is resolved.

Signed-off-by: David Graham 
Signed-off-by: Auke Kok 
Signed-off-by: Jeff Garzik

Revert "[netdrvr e100] experiment with doing RX in a similar manner to eepro100"

2007-06-12T22:52:31+00:00

This reverts commit d52df4a35af569071fda3f4eb08e47cc7023f094.

This patch attempted to fix e100 for non-cache coherent memory
architectures by using the cb style code that eepro100 had and using
the EL and s bits from the RFD list. Unfortunately the hardware
doesn't work exactly like this and therefore this patch actually
breaks e100. Reverting the change brings it back to the previously
known good state for 2.6.22. The pending rewrite in progress to this
code can then be safely merged later.

Signed-off-by: Auke Kok 
Signed-off-by: Jeff Garzik

e100: Optionally use I/O mode only to access register space

2007-04-28T15:01:07+00:00

It appears that some systems still like e100 better if it uses
I/O access mode.  Setting the new parameter use_io=1 will cause
all driver instances to use io mapping to access the register
space on the e100 device.

Signed-off-by: Jesse Brandeburg 
Signed-off-by: Auke Kok 
Signed-off-by: Jeff Garzik

e100: allow bad MAC address when running with invalid eeprom csum

2007-04-28T15:01:07+00:00

Seved Torstendahl  suggested to
let the module parameter for invalid eeprom checksum control the valid
mac address test.

If this bypass happens we should print a different message,
or at least one that is correct, maybe something like below

Signed-off-by: Jesse Brandeburg 
Signed-off-by: Auke Kok 
Signed-off-by: Jeff Garzik

[netdrvr e100] experiment with doing RX in a similar manner to eepro100

2007-04-28T15:01:05+00:00

I was going to say that eepro100's speedo_rx_link() does the same DMA
abuse as e100, but then I noticed one little detail: eepro100 sets  both
EL (end of list) and S (suspend) bits in the RFD as it chains it  to the
RFD list.  e100 was only setting the EL bit.  Hmmm, that's  interesting.
That means that if HW reads a RFD with the S-bit set,  it'll process
that RFD and then suspend the receive unit.  The  receive unit will
resume when SW clears the S-bit.  There is no need  for SW to restart
the receive unit.  Which means a lot of the receive  unit state tracking
code in the driver goes away.

So here's a patch against 2.6.14.  (Sorry for inlining it; the mailer
I'm using now will mess with the word wrap).  I can't test this on
XScale (unless someone has an e100 module for Gumstix :) .  It should
be doing exactly what eepro100 does with RFDs.  I don't believe this
change will introduce a performance hit because the S-bit and EL-bit  go
hand-in-hand meaning if we're going to suspend because of the S- bit,
we're on the last resource anyway, so we'll have to wait for SW  to
replenish.
(cherry picked from 29e79da9495261119e3b2e4e7c72507348e75976 commit)

[SK_BUFF]: Introduce skb_copy_to_linear_data{_offset}

2007-04-26T05:28:29+00:00

To clearly state the intent of copying to linear sk_buffs, _offset being a
overly long variant but interesting for the sake of saving some bytes.

Signed-off-by: Arnaldo Carvalho de Melo

e100: fix napi ifdefs removing needed code

2007-02-02T13:34:10+00:00

e100: fix napi ifdefs removing needed code

From: Auke Kok 

The e100 driver is NAPI mode only. We need to netif_poll_disable
during suspend and shutdown. The non-NAPI driver code was removed
and is only avaiable in the out-of-tree e100 kernel driver.

Signed-off-by: Auke Kok 
Signed-off-by: Jeff Garzik

e100: fix irq leak on suspend/resume

2007-01-30T14:36:02+00:00

e100: fix irq leak on suspend/resume

From: Frederik Deweerdt 

The e100_resume() function should be calling netif_device_detach and
free_irq. This fixes multiple irq's being allocated after resume.

Signed-off-by: Frederik Deweerdt 
Signed-off-by: Auke Kok 
Signed-off-by: Jeff Garzik