From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Re: urb timeout with bluetooth USB HCI on ARM (2.6.11-rc3)
Date: Thu, 24 Feb 2005 11:40:09 +0100 [thread overview]
Message-ID: <1109241609.5645.4.camel@notepaq> (raw)
In-Reply-To: <loom.20050222T131039-923@post.gmane.org>
Hi Thibaut,
> Looking at the code, "isoc" is only available when CONFIG_BT_HCIUSB_SCO is
> enabled, which wasn't my case. AFAICT it's used for disabling SCO protocol at
> runtime in the code, but just to make absolutely sure I rebuilt the module with
> SCO support enabled, tried various values for isoc=, none changed anything.
>
> tried with "reset=1", didn't change anything either
>
> FWIW, it's almost impossible to debug with CONFIG_BT_HCIUSB_DEBUG force set on,
> for the machine is so slowed down that the timeouts would actually be
> meaningful. Maybe this is why this config option isn't available from the config
> menu ;)
if both not helps, then I think that it a ARM and USB related problem.
Since I don't have any of these platform, I can't help you here.
Regards
Marcel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-02-24 10:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-21 17:04 [Bluez-devel] urb timeout with bluetooth USB HCI on ARM (2.6.11-rc3) Thibaut VARENE
2005-02-21 22:45 ` Marcel Holtmann
2005-02-22 12:31 ` [Bluez-devel] " Thibaut VARENE
2005-02-24 10:40 ` Marcel Holtmann [this message]
2005-02-22 12:41 ` Thibaut VARENE
2005-02-24 10:38 ` Marcel Holtmann
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=1109241609.5645.4.camel@notepaq \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
/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