An error occurred fetching the project authors.
- 19 Oct, 2004 3 commits
-
-
Ganesh Venkatesan authored
Signed-off-by:
Ganesh Venkatesan <ganesh.venkatesan@intel.com>
-
Ganesh Venkatesan authored
Signed-off-by:
Ganesh Venkatesan <ganesh.venkatesan@intel.com>
-
Ganesh Venkatesan authored
is brought down. Signed-off-by:
Ganesh Venkatesan <ganesh.venkatesan@intel.com>
-
- 16 Oct, 2004 1 commit
-
-
Alexander Viro authored
Signed-off-by:
Al Viro <viro@parcelfarce.linux.theplanet.co.uk>
-
- 30 Sep, 2004 2 commits
-
-
Jesse Brandeburg authored
This is a short patch to add a couple of new DPRINTKS and fix some whitespace issues. Signed-off-by:
Jesse Brandeburg <jesse.brandeburg@intel.com>
-
Jesse Brandeburg authored
While polling in NAPI mode, we were occassionally getting interrupts re-enabled by the watchdog trying to generate a software interrupt. Fix is to add a spinlock around that shared hardware register to allow a read-modify-write operation. This was nasty nasty. I don't like the spinlock in the hot path but i see no other way. Comments are welcome. Updates the driver version as well. Signed-off-by:
Jesse Brandeburg <jesse.brandeburg@intel.com>
-
- 17 Sep, 2004 3 commits
-
-
Ganesh Venkatesan authored
-
Ganesh Venkatesan authored
-
Ganesh Venkatesan authored
-
- 29 Jul, 2004 6 commits
-
-
Ganesh Venkatesan authored
-
Ganesh Venkatesan authored
-
Ganesh Venkatesan authored
-
Ganesh Venkatesan authored
-
Ganesh Venkatesan authored
-
Ganesh Venkatesan authored
the completion of the diagnostic tests
-
- 10 Jun, 2004 4 commits
-
-
Scott Feldman authored
I see no reason to keep the non-NAPI option for e100. This patch removes the CONFIG_E100_NAPI option and puts the driver in NAPI mode all the time. Matches the way tg3 works. Unless someone has a really good reason to keep the non-NAPI mode, this should go in for 2.6.7. -scott
-
Scott Feldman authored
* When e100 experiences a transmit timeout, it calls e100_up() to reset the device. e100_up calls netif_start_queue to release any flow block, but doesn't reschedule. This patch unblocks the flow and schedules Tx. Jay Vosburgh [fubar@us.ibm.com]. Signed-off-by: scott.feldman@intel.com
-
Scott Feldman authored
* If e100 experiences a transmit timeout, and the tx ring is completely full at the time, it will leak all of the skbs on the tx ring (because extra logic is needed to distinguish ring full from ring empty). Jay Vosburgh [fubar@us.ibm.com]. Signed-off-by: scott.feldman@intel.com
-
Scott Feldman authored
* Spotted by Jay Vosburgh [fubar@us.ibm.com]. err return code was getting stepped on in the case where we need to report low or no cb resources, which in turn messed up the netif_stop_queue logic in xmit_frame. Signed-off-by: scott.feldman@intel.com
-
- 04 Jun, 2004 1 commit
-
-
Alexander Viro authored
From: Jeff Garzik Jeff's patch adds a helper for obtaining mii_ioctl_data from ifreq and switches drivers to it. It's almost a "move common expression into inline helper", except that instead of (struct mii_ioctl_data *)&rq->ifr_ifru.ifru_data it does (struct mii_ioctl_data *)&rq->ifr_ifru - pointer to union instead of pointer to a field of union that has nothing to do with mii_ioctl_data *and* adds confusion by being a pointer itself.
-
- 18 May, 2004 3 commits
-
-
Scott Feldman authored
* Convert all netdev->priv references to the fancy new netdev_priv().
-
Scott Feldman authored
* Reads/writes from/to eeprom using ethtool weren't working right on big-endian. Now they are.
-
Scott Feldman authored
* Changed mapping on Rx skb to bi-directional. skb->data holds both the RFD structure and the packet data, and the RFD is read/written by HW. Issue found on Xscale HW that doesn't handle cache syncs auto- matically. Other changes in patch are whitespace/spelling.
-
- 24 Apr, 2004 1 commit
-
-
Scott Feldman authored
* Need to carry forward this workaround from old e100 driver to avoid a Tx hang on ICH systems linked at 10/Half. Workaround adds a stall before each Tx command queued by issuing a NOP command followed by 1us delay. Yuck! Otherwise HW locks hard. (Probably needed for eepro100 also ;-).
-
- 14 Mar, 2004 1 commit
-
-
Andrew Morton authored
From: "David S. Miller" <davem@redhat.com> Currently, for an existing DMA mapping, there is a way to transfer buffer ownership back to the cpu, yet there is no way to give it back to the device again explicitly. The latter really is needed on platforms where the PCI subsystem does not snoop the cpu caches, MIPS is one example. Many drivers were expecting the existing DMA sync interface to handle both directions, which was wrong. Now, with this change, we have explicit interfaces for DMA syncing to/from the device and the cpu.
-
- 12 Mar, 2004 1 commit
-
-
Scott Feldman authored
* Not setting cb->skb = NULL after releasing skb to OS or during initialization of cbs. Reported by Deepak Saxena [dsaxena@plexity.net].
-
- 07 Mar, 2004 1 commit
-
-
Scott Feldman authored
* Add National DP83840 PHY rev b/c setup. Only rev a was being setup.
-
- 24 Feb, 2004 1 commit
-
-
Scott Feldman authored
* define dump stats complete constant * add mwb() to keep order straight with HW when appending new resources to Rx and Tx queues * increment stats for rx_dropped and rx_over_errors
-
- 13 Jan, 2004 2 commits
-
-
Scott Feldman authored
* Misc: 2004 copyright, remove trailing white space, remove some unused symbols.
-
Scott Feldman authored
* Addresses two problems, both resulting in slab corruption: 1) driver indicating skb while HW is still DMA'ing (ouch!), 2) driver not stopping receiver activity before downing i/f. Fix is 1) wait for RNR (receiver-no-resources) interrupt before restarting receiver, 2) reseting HW to stop receiver before stopping i/f. This issue was also reproducible with eepro100. You need to turn off the copybreak, and reduce the number of descriptors to 4. Then bang on it with pktgen with 60-byte packets, with slab debugging enabled. For e100-3.0.x, the issue was a lot easier to reproduce with NAPI, because NAPI polls independently of where the HW is at, so it's easier for us to catch HW in the middle of finishing off the last Rx (as it runs out of resources) and asking HW if it's idle. Checking the RU status is not-reliable! That's the problem, and the mistake both eepro100 and e100-3.0.x were making. The solution is rely on RNR interrupts as the only indicator that HW is truly done, and then we're ready to restart the RU. We should only get RNR interrupts when we overrun the Rx ring. With NAPI, if the ring is overrun, we'll post RNR, but not restart the RU until we're out of polling. Without NAPI, we'll restart the RU as soon as we get RNR. I ran some 24-hour tests with and without NAPI (with 4 descriptors) and didn't get any corruption. Prior to this patch, I would get many errors about slab corruption. Also, the patch is larger than you might expect, but I initially thought I was doing something wrong with managing the <list.h> ring, so I that code using old fashion double-link list. The ring management wasn't the problem, after all, but I prefer the old-fashion d-link implementation as it's easier to read.
-
- 10 Jan, 2004 4 commits
-
-
Scott Feldman authored
* Preserve forced speed/duplex settings during close/open sequence. * Reset PHY when going from autoneg to forced speed/duplex settings using ethtool. * Add netpoll support.
-
Jeff Garzik authored
Fixes build.
-
Scott Feldman authored
* Add ICH6 device IDs. Devices funcionally equivalent to supported ICH5 devices, but new IDs. * Fixed unaligned access to casted skb->data (Matt Willcox [willy@debian.org]). * MODULE_PARM -> module_param * Bug printk after register_netdev to identify nic details. * misc cleanups.
-
Scott Feldman authored
-