From: Marcel Holtmann <marcel@holtmann.org>
To: "Jan J. Jessen" <jjjessen@control.auc.dk>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Digianswer USB driver
Date: 22 Sep 2003 19:59:19 +0200 [thread overview]
Message-ID: <1064253565.5641.126.camel@pegasus> (raw)
In-Reply-To: <Pine.GSO.4.40.0309171153080.23244-100000@prosit.control.auc.dk>
[-- Attachment #1: Type: text/plain, Size: 237 bytes --]
Hi Jan,
> I've compiled a kernel with MODVERSION and now hci_usb loads without
> trouble. I've tried to do hciconfig hci0 up but this gives:
> Can't init device hci0. Connection timed out(110)
what about this patch?
Regards
Marcel
[-- Attachment #2: patch-hci-usb-digianswer2 --]
[-- Type: text/x-patch, Size: 1888 bytes --]
diff -urN linux-2.4.22/drivers/bluetooth/hci_usb.c linux-2.4.22-digianswer/drivers/bluetooth/hci_usb.c
--- linux-2.4.22/drivers/bluetooth/hci_usb.c Mon Aug 25 13:44:41 2003
+++ linux-2.4.22-digianswer/drivers/bluetooth/hci_usb.c Mon Sep 22 19:57:15 2003
@@ -70,6 +70,9 @@
static struct usb_driver hci_usb_driver;
static struct usb_device_id bluetooth_ids[] = {
+ /* Digianswer device */
+ { USB_DEVICE(0x08fd, 0x0001), driver_info: HCI_DIGIANSWER },
+
/* Generic Bluetooth USB device */
{ USB_DEVICE_INFO(HCI_DEV_CLASS, HCI_DEV_SUBCLASS, HCI_DEV_PROTOCOL) },
@@ -427,7 +430,7 @@
} else
dr = (void *) _urb->urb.setup_packet;
- dr->bRequestType = HCI_CTRL_REQ;
+ dr->bRequestType = husb->ctrl_req;
dr->bRequest = 0;
dr->wIndex = 0;
dr->wValue = 0;
@@ -872,6 +875,11 @@
husb->bulk_out_ep = bulk_out_ep[0];
husb->bulk_in_ep = bulk_in_ep[0];
husb->intr_in_ep = intr_in_ep[0];
+
+ if (id->driver_info & HCI_DIGIANSWER)
+ husb->ctrl_req = HCI_DIGI_REQ;
+ else
+ husb->ctrl_req = HCI_CTRL_REQ;
#ifdef CONFIG_BLUEZ_USB_SCO
if (isoc_iface) {
diff -urN linux-2.4.22/drivers/bluetooth/hci_usb.h linux-2.4.22-digianswer/drivers/bluetooth/hci_usb.h
--- linux-2.4.22/drivers/bluetooth/hci_usb.h Fri Jun 13 16:51:32 2003
+++ linux-2.4.22-digianswer/drivers/bluetooth/hci_usb.h Mon Sep 22 19:56:44 2003
@@ -35,6 +35,9 @@
#define HCI_DEV_PROTOCOL 0x01 /* Bluetooth programming protocol */
#define HCI_CTRL_REQ 0x20
+#define HCI_DIGI_REQ 0x40
+
+#define HCI_DIGIANSWER 0x01
#define HCI_MAX_IFACE_NUM 3
@@ -118,6 +121,8 @@
struct usb_interface *isoc_iface;
struct usb_endpoint_descriptor *isoc_out_ep;
struct usb_endpoint_descriptor *isoc_in_ep;
+
+ __u8 ctrl_req;
struct sk_buff_head transmit_q[4];
struct sk_buff *reassembly[4]; // Reassembly buffers
next prev parent reply other threads:[~2003-09-22 17:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-15 6:25 [Bluez-devel] Digianswer USB driver Jan J. Jessen
2003-08-15 12:39 ` Marcel Holtmann
2003-08-26 11:24 ` Jan J. Jessen
2003-08-30 0:11 ` Marcel Holtmann
2003-09-16 14:02 ` Jan J. Jessen
2003-09-16 23:57 ` Marcel Holtmann
2003-09-17 9:59 ` Jan J. Jessen
2003-09-22 17:59 ` Marcel Holtmann [this message]
2003-09-23 8:21 ` Jan J. Jessen
2003-09-23 8:56 ` Marcel Holtmann
2003-09-29 10:58 ` Jan J. Jessen
2003-09-16 14:16 ` Jan J. Jessen
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=1064253565.5641.126.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=jjjessen@control.auc.dk \
/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