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
| File | Mode | Size |
|---|---|---|
| Kconfig | -rw-r--r-- | 2.6 KB |
| Makefile | -rw-r--r-- | 494 bytes |
| associola.c | -rw-r--r-- | 39.0 KB |
| bind_addr.c | -rw-r--r-- | 11.7 KB |
| chunk.c | -rw-r--r-- | 8.0 KB |
| command.c | -rw-r--r-- | 2.4 KB |
| crc32c.c | -rw-r--r-- | 8.2 KB |
| debug.c | -rw-r--r-- | 4.7 KB |
| endpointola.c | -rw-r--r-- | 9.7 KB |
| input.c | -rw-r--r-- | 25.5 KB |
| inqueue.c | -rw-r--r-- | 6.5 KB |
| ipv6.c | -rw-r--r-- | 28.3 KB |
| objcnt.c | -rw-r--r-- | 4.0 KB |
| output.c | -rw-r--r-- | 19.3 KB |
| outqueue.c | -rw-r--r-- | 50.5 KB |
| primitive.c | -rw-r--r-- | 7.6 KB |
| proc.c | -rw-r--r-- | 11.0 KB |
| protocol.c | -rw-r--r-- | 34.6 KB |
| sm_make_chunk.c | -rw-r--r-- | 84.8 KB |
| sm_sideeffect.c | -rw-r--r-- | 43.4 KB |
| sm_statefuns.c | -rw-r--r-- | 176.1 KB |
| sm_statetable.c | -rw-r--r-- | 32.5 KB |
| socket.c | -rw-r--r-- | 173.9 KB |
| ssnmap.c | -rw-r--r-- | 3.5 KB |
| sysctl.c | -rw-r--r-- | 6.8 KB |
| transport.c | -rw-r--r-- | 18.1 KB |
| tsnmap.c | -rw-r--r-- | 10.4 KB |
| ulpevent.c | -rw-r--r-- | 28.2 KB |
| ulpqueue.c | -rw-r--r-- | 26.8 KB |
Computing file changes ...
