From: Florian Lohoff <flo@rfc822.org>
To: Max Krasnyansky <maxk@qualcomm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.4.21] bluez/usb-ohci bulk_msg timeout
Date: Fri, 25 Jul 2003 14:40:10 +0200 [thread overview]
Message-ID: <20030725124010.GA910@paradigm.rfc822.org> (raw)
In-Reply-To: <5.1.0.14.2.20030723140628.096fcbe0@unixmail.qualcomm.com>
[-- Attachment #1: Type: text/plain, Size: 1953 bytes --]
On Wed, Jul 23, 2003 at 02:08:25PM -0700, Max Krasnyansky wrote:
> Probably. Could try the prev revision of the HCI USB driver though. ie The one without SCO
> support. Just copy hci_usb.[ch] over from older kernel and see if it works with newer OHCI.
I tried the ones from 2.4.20 and the same error messages appear - So i
think its the OHCI stuff - It got a some major changes it seems from the
2.4.21 patch ...
Linux version 2.4.21-vaio3 (root@paradigm) (gcc version 2.95.4 20011002 (Debian prerelease)) #1 Fri Jul 25 13:12:06 CEST 2003
[...]
hub.c: new USB device 00:0f.0-2, assigned address 3
usb.c: USB device 3 (vend/prod 0x44e/0x3001) is not claimed by any active driver.
usb_control/bulk_msg: timeout
usbdevfs: USBDEVFS_CONTROL failed dev 3 rqt 128 rq 6 len 9 ret -110
BlueZ Core ver 2.3 Copyright (C) 2000,2001 Qualcomm Inc
Written 2000,2001 by Maxim Krasnyansky <maxk@qualcomm.com>
BlueZ HCI USB driver ver 2.1 Copyright (C) 2000,2001 Qualcomm Inc
Written 2000,2001 by Maxim Krasnyansky <maxk@qualcomm.com>
usb.c: registered new driver hci_usb
usb_control/bulk_msg: timeout
usbdevfs: USBDEVFS_CONTROL failed dev 3 rqt 128 rq 6 len 193 ret -110
usb_control/bulk_msg: timeout
usbdevfs: USBDEVFS_CONTROL failed dev 3 rqt 128 rq 6 len 193 ret -110
usb_control/bulk_msg: timeout
usbdevfs: USBDEVFS_CONTROL failed dev 3 rqt 128 rq 6 len 9 ret -110
BlueZ RFCOMM ver 1.0
Copyright (C) 2002 Maxim Krasnyansky <maxk@qualcomm.com>
Copyright (C) 2002 Marcel Holtmann <marcel@holtmann.org>
usbdevfs: USBDEVFS_CONTROL failed dev 3 rqt 128 rq 6 len 9 ret -75
BlueZ L2CAP ver 2.3 Copyright (C) 2000,2001 Qualcomm Inc
Written 2000,2001 by Maxim Krasnyansky <maxk@qualcomm.com>
CSLIP: code copyright 1989 Regents of the University of California
PPP generic driver version 2.4.2
Flo
--
Florian Lohoff flo@rfc822.org +49-171-2280134
Heisenberg may have been here.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2003-07-25 12:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-18 17:32 [2.4.21] bluez/usb-ohci bulk_msg timeout Florian Lohoff
2003-07-21 17:06 ` Max Krasnyansky
2003-07-23 14:20 ` Florian Lohoff
2003-07-23 21:08 ` Max Krasnyansky
2003-07-25 12:40 ` Florian Lohoff [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030725124010.GA910@paradigm.rfc822.org \
--to=flo@rfc822.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxk@qualcomm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).