Revision 3b12e0141f7a97c3b84731b5f935ed738bb6f960 authored by Stephen Hemminger on 27 September 2007, 00:58:47 UTC, committed by Jeff Garzik on 28 September 2007, 03:32:28 UTC
The Yukon FE+ chip appears to have a hardware glitch that causes bogus
receive status values to be posted. The data in the packet is good, but
the status value is random garbage.  As a temporary workaround until the
problem is better understood, implement the workaround the vendor driver
used of ignoring the status value on this chip.

Since this means trusting dodgy hardware values; add additional checking
of the receive packet length.

Signed-off-by: Stephen Hemminger <shemminger@linux-foundation.org>
Signed-off-by: Jeff Garzik <jeff@garzik.org>
1 parent ff0ce68
History
File Mode Size
Kconfig -rw-r--r-- 22.4 KB
Makefile -rw-r--r-- 1.0 KB
calibrate.c -rw-r--r-- 4.7 KB
do_mounts.c -rw-r--r-- 10.1 KB
do_mounts.h -rw-r--r-- 1.4 KB
do_mounts_initrd.c -rw-r--r-- 3.0 KB
do_mounts_md.c -rw-r--r-- 7.3 KB
do_mounts_rd.c -rw-r--r-- 10.0 KB
initramfs.c -rw-r--r-- 11.9 KB
main.c -rw-r--r-- 20.6 KB
noinitramfs.c -rw-r--r-- 1.4 KB
version.c -rw-r--r-- 1009 bytes

back to top