diff options
| author | Mauro Carvalho Chehab <mchehab@infradead.org> | 2006-10-04 10:56:29 -0300 |
|---|---|---|
| committer | Mauro Carvalho Chehab <mchehab@infradead.org> | 2006-10-04 10:56:29 -0300 |
| commit | 17e74b573dc630942da350ce5cbe8d760bdf94c1 (patch) | |
| tree | afa932537b4671595e3012dae0ee90ad9e7ca802 /linux/drivers/media/video/w9968cf.c | |
| parent | c7b6c448bbe3230edff5d16e6c3fe78742c65c69 (diff) | |
| download | mediapointer-dvb-s2-17e74b573dc630942da350ce5cbe8d760bdf94c1.tar.gz mediapointer-dvb-s2-17e74b573dc630942da350ce5cbe8d760bdf94c1.tar.bz2 | |
USB: Dealias -110 code (more complete)
From: Mauro Carvalho Chehab <mchehab@infradead.org>
Apply the relevant parts of a patch from Pete Zaitcev <zaitcev@redhat.com>
kernel-sync:
Original description:
The purpose of this patch is to split off the case when a device does
not reply on the lower level (which is reported by HC hardware), and
a case when the device accepted the request, but does not reply at
upper level. This redefinition allows to diagnose issues easier,
without asking the user if the -110 happened "immediately".
The usbmon splits such cases already thanks to its timestamp, but
it's not always available.
I adjusted all drivers which I found affected (by searching for "urb").
Out of tree drivers may suffer a little bit, but I do not expect much
breakage. At worst they may print a few messages.
Signed-off-by: Mauro Carvalho Chehab <mchehab@infradead.org>
Diffstat (limited to 'linux/drivers/media/video/w9968cf.c')
| -rw-r--r-- | linux/drivers/media/video/w9968cf.c | 7 |
1 files changed, 3 insertions, 4 deletions
diff --git a/linux/drivers/media/video/w9968cf.c b/linux/drivers/media/video/w9968cf.c index 20f211b55..2912326a5 100644 --- a/linux/drivers/media/video/w9968cf.c +++ b/linux/drivers/media/video/w9968cf.c @@ -586,15 +586,14 @@ static struct w9968cf_symbolic_list urb_errlist[] = { { -EFBIG, "Too much ISO frames requested" }, { -ENOSR, "Buffer error (overrun)" }, { -EPIPE, "Specified endpoint is stalled (device not responding)"}, - { -EOVERFLOW, "Babble (bad cable?)" }, + { -EOVERFLOW, "Babble (too much data)" }, { -EPROTO, "Bit-stuff error (bad cable?)" }, { -EILSEQ, "CRC/Timeout" }, - { -ETIMEDOUT, "NAK (device does not respond)" }, + { -ETIME, "Device does not respond to token" }, + { -ETIMEDOUT, "Device does not respond to command" }, { -1, NULL } }; - - /**************************************************************************** * Memory management functions * ****************************************************************************/ |