From: Marcel Holtmann <marcel@holtmann.org>
To: Stephen Quattlebaum <stephen@covidimus.net>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Connection Timeout
Date: Sat, 30 Oct 2004 01:15:21 +0200 [thread overview]
Message-ID: <1099091721.6912.35.camel@pegasus> (raw)
In-Reply-To: <1099090255.12760.26.camel@athene.covidimus.net>
[-- Attachment #1: Type: text/plain, Size: 1914 bytes --]
Hi Stephen,
> I'm a BT newbie having trouble with device timeouts using bluez. I've
> seen this issue posted a few other places but no answers yet. Some
> background:
>
> I just bought a Microsoft BT mouse for a Win XP laptop and decided this
> afternoon to take it for a spin on my Linux box.
>
> I've got kernel 2.6.8 (what gentoo calls 2.6.8.1-ck9; don't know where
> the .1 comes from but the ck9 refers to a set of desktop performance
> tuning patches they apply).
>
> I applied patch-2.6.9-mh2 from http://www.bluez.org/patches.html and
> rebuilt my kernel and modules.
be carful with this, because these patches are only tested with the
kernel they are made for.
> The mouse came with a little USB dongle that has the following info on
> the backside:
>
> "Wireless Transceiver for Bluetooth 2.0"
> Model: 1003
> IC: 3048A-1003
>
> usbview shows the dongle with the name "Wireless Radio for Bluetooth",
> and its name is in red, which I've been led to believe means that no
> drivers have attached themselves to the device. I don't know if that's
> important here or not. I'd paste in the usbview output but usbview
> appears to not support whatever flavor of cut-and-paste gnome uses.
> I'll pull out any info someone asks me for (it's a big listing). Here's
> the first several lines:
>
> Manufacturer: Microsoft
> Serial Number: 0050F2E8E590
> Speed: 12Mb/s (full)
> USB Version: 1.10
> Device Class: e0(unk.)
> Device Subclass: 01
> Device Protocol: 01
> Maximum Default Endpoint Size: 64
> Number of Configurations: 1
> Vendor Id: 045e
> Product Id: 009c
> Revision Number: 1.00
This is the new dongle from Microsoft and it is now Broadcom based and
so you maybe need an additional patch to make it working. When it works,
send back the output from "hciconfig -a".
Btw I need this new desktop package from Microsoft for testing. Is there
anyone willing to donate one?
Regards
Marcel
[-- Attachment #2: patch --]
[-- Type: text/plain, Size: 545 bytes --]
===== drivers/bluetooth/hci_usb.c 1.58 vs edited =====
--- 1.58/drivers/bluetooth/hci_usb.c 2004-10-27 23:42:21 +02:00
+++ edited/drivers/bluetooth/hci_usb.c 2004-10-30 01:09:54 +02:00
@@ -103,6 +103,9 @@
/* Broadcom BCM2035 */
{ USB_DEVICE(0x0a5c, 0x200a), .driver_info = HCI_RESET | HCI_BROKEN_ISOC },
+ /* Microsoft Wireless Transceiver for Bluetooth 2.0 */
+ { USB_DEVICE(0x045e, 0x009c), .driver_info = HCI_RESET | HCI_BROKEN_ISOC },
+
/* ISSC Bluetooth Adapter v3.1 */
{ USB_DEVICE(0x1131, 0x1001), .driver_info = HCI_RESET },
next prev parent reply other threads:[~2004-10-29 23:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-29 22:50 [Bluez-users] Connection Timeout Stephen Quattlebaum
2004-10-29 23:15 ` Marcel Holtmann [this message]
2004-10-30 2:20 ` Stephen Quattlebaum
2004-10-30 13:37 ` Marcel Holtmann
2004-10-29 23:19 ` Henryk Plötz
2004-10-30 10:22 ` Jouni.Lohikoski@iki.fi
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=1099091721.6912.35.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
--cc=stephen@covidimus.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