From: Max Krasnyansky <maxk@qualcomm.com>
To: Florian Lohoff <flo@rfc822.org>, linux-kernel@vger.kernel.org
Subject: Re: [2.4.21] bluez/usb-ohci bulk_msg timeout
Date: Mon, 21 Jul 2003 10:06:19 -0700 [thread overview]
Message-ID: <5.1.0.14.2.20030721100313.0759df08@unixmail.qualcomm.com> (raw)
In-Reply-To: <20030718173214.GD15430@paradigm.rfc822.org>
At 10:32 AM 7/18/2003, Florian Lohoff wrote:
>Hi,
>since 2.4.21 + mh2 bluez patch i am seeing these errors. 2.4.20 + mh7
>bluez patch did not show these errors. Results are very instable
>Bluetooth connections.
Those errors don't seem to be related to the driver update. But you could
try this. In drivers/bluetooth/hci_usb.h set HCI_MAX_BULK_TX define to 1 (instead of 4)
and rebuild the module. Does it make any difference ?
Max
next prev parent reply other threads:[~2003-07-21 16:51 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 [this message]
2003-07-23 14:20 ` Florian Lohoff
2003-07-23 21:08 ` Max Krasnyansky
2003-07-25 12:40 ` Florian Lohoff
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=5.1.0.14.2.20030721100313.0759df08@unixmail.qualcomm.com \
--to=maxk@qualcomm.com \
--cc=flo@rfc822.org \
--cc=linux-kernel@vger.kernel.org \
/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).