- 25 12月, 2005 1 次提交
-
-
由 Manfred Spraul 提交于
Two critical bugs were found in forcedeth 0.47: - TSO doesn't work. - pci_map_single() for the rx buffers is called with size==0. This bug is critical, it causes random memory corruptions on systems with an iommu. Below is a minimal fix for both bugs, for 2.6.15. TSO will be fixed properly in the next version. Tested on x86-64. Signed-Off-By: NManfred Spraul <manfred@colorfullife.com> Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
-
- 11 11月, 2005 3 次提交
-
-
由 Ayaz Abdulla 提交于
Added phy address 0 to the phy scan. Signed-off-by: NAyaz Abdulla <aabdulla@nvidia.com>
-
由 Ayaz Abdulla 提交于
This patch contains support for different modes of interrupt mitigation of forcedeth. It includes changes based on Jeff's comments. Currently, the modes are changed through module parameters since ethtool does not support something similar. Signed-off-by: NAyaz Abdulla <aabdulla@nvidia.com>
-
由 Ayaz Abdulla 提交于
Signed-off-by: NAyaz Abdulla <aabdulla@nvidia.com>
-
- 26 10月, 2005 1 次提交
-
-
由 Ayaz Abdulla 提交于
also: - eliminate use of pointless get_nvpriv() wrapper, and use netdev_priv() directly. - use NETDEV_TX_xxx return codes
-
- 22 9月, 2005 1 次提交
-
-
由 Manfred Spraul 提交于
Recent forcedeth nics support checksum offloading for tx. The attached patch, written by Ayaz Abdulla, adds the support to the driver. It also cleans up the handling of the three dma ring entry formats that are supported by the driver. Signed-off-By: NManfred Spraul <manfred@colorfullife.com> Signed-off-By: NJeff Garzik <jgarzik@pobox.com>
-
- 14 9月, 2005 1 次提交
-
-
由 John W. Linville 提交于
Add support for ETHTOOL_GPERMADDR to forcedeth. Signed-off-by: NJohn W. Linville <linville@tuxdriver.com> Signed-off-by: NJeff Garzik <jgarzik@pobox.com>
-
- 07 9月, 2005 1 次提交
-
-
由 viro@ftp.linux.org.uk 提交于
Signed-off-by: NAl Viro <viro@zeniv.linux.org.uk> Signed-off-by: NJeff Garzik <jgarzik@pobox.com>
-
- 19 8月, 2005 1 次提交
-
-
由 Manfred Spraul 提交于
Rüdiger found a bug in nv_open that explains some of the reports with duplex mismatches: nv_open calls nv_update_link_speed for initializing the hardware link speed registers. If current link setting matches the values in np->linkspeed and np->duplex, then the function does nothing. Usually, doing nothing is the right thing, but not in nv_open: During nv_open, the registers must be initialized because the nic was reset. The attached patch fixes that by setting np->linkspeed to an invalid value before calling nv_update_link_speed from nv_open. Signed-Off-By: NManfred Spraul <manfred@colorfullife.com> Signed-off-by: NJeff Garzik <jgarzik@pobox.com>
-
- 01 8月, 2005 6 次提交
-
-
由 Manfred Spraul 提交于
This is a multi-part message in MIME format. Signed-off-by: NJeff Garzik <jgarzik@pobox.com>
-
由 Manfred Spraul 提交于
This is a multi-part message in MIME format. Signed-off-by: NJeff Garzik <jgarzik@pobox.com>
-
由 Manfred Spraul 提交于
This is a multi-part message in MIME format. Signed-off-by: NJeff Garzik <jgarzik@pobox.com>
-
由 Manfred Spraul 提交于
This is a multi-part message in MIME format. Signed-off-by: NJeff Garzik <jgarzik@pobox.com>
-
由 Manfred Spraul 提交于
This is a multi-part message in MIME format. Signed-off-by: NJeff Garzik <jgarzik@pobox.com>
-
由 Manfred Spraul 提交于
This is a multi-part message in MIME format. Signed-off-by: NJeff Garzik <jgarzik@pobox.com>
-
- 27 6月, 2005 3 次提交
-
-
由 Manfred Spraul 提交于
This is a multi-part message in MIME format.
-
由 Manfred Spraul 提交于
This is a multi-part message in MIME format.
-
由 Manfred Spraul 提交于
This is a multi-part message in MIME format.
-
- 16 5月, 2005 1 次提交
-
-
由 Manfred Spraul 提交于
Ayaz wrote an update to the error handling for forcedeth (which I modified heavily, thus all bugs are mine): The ERROR4 bit is not a fatal error, it just indicates a mismatch between the actual packet len and the len according to the 802.3 header. The patch adds proper handling. The patch also removes the code that drops all packets with RX_ERROR & (!RX_FRAMINGERR): ERROR4 errors are also not fatal.
-
- 13 5月, 2005 1 次提交
-
-
由 Michal Schmidt 提交于
-
- 17 4月, 2005 1 次提交
-
-
由 Linus Torvalds 提交于
Initial git repository build. I'm not bothering with the full history, even though we have it. We can create a separate "historical" git archive of that later if we want to, and in the meantime it's about 3.2GB when imported into git - space that would just make the early git days unnecessarily complicated, when we don't have a lot of good infrastructure for it. Let it rip!
-