diff options
| author | Linas Vepstas <linas@austin.ibm.com> | 2007-06-11 14:23:42 -0400 |
|---|---|---|
| committer | Jeff Garzik <jeff@garzik.org> | 2007-06-20 19:09:33 -0400 |
| commit | 2bf27a0d4913a5f0ef38e3be510b1b3add2869ad (patch) | |
| tree | 6644564484a6501d5f2adf2d296ce817b4a1fc6e /drivers/cpufreq | |
| parent | 4c4bd5a97a87670d2c368ed4ed8a8f2c93080605 (diff) | |
spidernet: Don't terminate the RX ring
The terminated RX ring will cause trouble during the RX ram full
conditions, leading to a hung driver, as the hardware can't find
the next descr. There is no real reason to terminate the RX ring;
it doesn't make the operation any smooother, and it does
require an extra sync. So don't do it.
Signed-off-by: Linas Vepstas <linas@austin.ibm.com>
Signed-off-by: Jeff Garzik <jeff@garzik.org>
Diffstat (limited to 'drivers/cpufreq')
0 files changed, 0 insertions, 0 deletions