From: Anders Karlsson <anders@trudheim.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Bluetooth oddity
Date: Fri, 30 Jan 2004 14:00:47 +0000 [thread overview]
Message-ID: <1075471246.11889.5.camel@tor.trudheim.com> (raw)
In-Reply-To: <1075469610.26729.108.camel@pegasus>
[-- Attachment #1: Type: text/plain, Size: 1151 bytes --]
On Fri, 2004-01-30 at 13:33, Marcel Holtmann wrote:
> Hi Anders,
Hello Marcel,
> I assume that you have enabled the SCO support of the HCI USB driver.
> The unlink of ISOC URB's fails on UHCI host controllers and actually I
> don't know why. So disable the SCO support of the HCI USB driver and you
> can switch on and off your Bluetooth device as often as you like.
I just checked, and I did have the SCO support switched on. Shows that
the name can not be trusted... ;-)
> What is your USB host controller chipset? Do you see an oops?
No oops, rebuilding the kernel with serial support built in so I can
attach serial console. After that I should be able to capture any
information required.
> This was a bug in the RFCOMM layer that has been already fixed. Why
> don't you say what 2.6 kernel do you use? Try the latest 2.6.2-rc2 or
> 2.6.1-mh3 and this will go away.
I am currently using 2.6.1 proper, but saw it in 2.6.0 and a couple of
half-way houses between 2.6.0 and 2.6.1.
I will give 2.6.2-rc2 a try over the weekend.
Regards,
--
Anders Karlsson <anders@trudheim.com>
Trudheim Technology Limited
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-01-30 14:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-30 11:32 Bluetooth oddity Anders Karlsson
2004-01-30 13:33 ` Marcel Holtmann
2004-01-30 14:00 ` Anders Karlsson [this message]
2004-01-30 14:25 ` 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=1075471246.11889.5.camel@tor.trudheim.com \
--to=anders@trudheim.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.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