Home
last modified time | relevance | path

Searched hist:e4a668c59080f862af3ecc28b359533027cbe434 (Results 1 – 3 of 3) sorted by relevance

/openbmc/linux/drivers/net/wireless/ath/carl9170/
H A Dcarl9170.hdiff e4a668c59080f862af3ecc28b359533027cbe434 Fri Oct 29 16:26:13 CDT 2010 Christian Lamparter <chunkeey@googlemail.com> carl9170: fix spurious restart due to high latency

RX Stress tests of unidirectional bulk traffic with
bitrates of up to 220Mbit/s have revealed that the
fatal-event recovery logic [which was solely triggered
by an out-of-rx-buffer situation] is too aggressive.

The new method now "pings" the device and then
decides - based on the response - whenever
a restart is needed or not.

Signed-off-by: Christian Lamparter <chunkeey@googlemail.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
H A Dusb.cdiff e4a668c59080f862af3ecc28b359533027cbe434 Fri Oct 29 16:26:13 CDT 2010 Christian Lamparter <chunkeey@googlemail.com> carl9170: fix spurious restart due to high latency

RX Stress tests of unidirectional bulk traffic with
bitrates of up to 220Mbit/s have revealed that the
fatal-event recovery logic [which was solely triggered
by an out-of-rx-buffer situation] is too aggressive.

The new method now "pings" the device and then
decides - based on the response - whenever
a restart is needed or not.

Signed-off-by: Christian Lamparter <chunkeey@googlemail.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
H A Dmain.cdiff e4a668c59080f862af3ecc28b359533027cbe434 Fri Oct 29 16:26:13 CDT 2010 Christian Lamparter <chunkeey@googlemail.com> carl9170: fix spurious restart due to high latency

RX Stress tests of unidirectional bulk traffic with
bitrates of up to 220Mbit/s have revealed that the
fatal-event recovery logic [which was solely triggered
by an out-of-rx-buffer situation] is too aggressive.

The new method now "pings" the device and then
decides - based on the response - whenever
a restart is needed or not.

Signed-off-by: Christian Lamparter <chunkeey@googlemail.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>