Linux bluetooth development
 help / color / mirror / Atom feed
From: "Al Chane" <al_chane@issc.com.tw>
To: <bluez-users@lists.sourceforge.net>
Subject: [Bluez-users] ISSC USB dongle patch
Date: Mon, 27 Jun 2005 18:53:40 +0800	[thread overview]
Message-ID: <009401c57b06$7afe3ef0$0132a8c0@AL> (raw)

Hi,

     I have an ISSC USB dongle and search the last year's archive to find 
the patch to
make it work with BlueZ.

     I just wonder how it works. What's black_ids[] for and the purpose of
adding .driver_info = HCI_RESET?

struct usb_device_id bluetooth_ids[]
struct usb_device_id ignore_ids[] or black_ids[]

thanks a lot,

Al



=================================================================
it looks like that this device needs the HCI_Reset before it can run an
inquiry. Funny is that every other HCI command work without it. Try the
attached patch.

Regards

Marcel


===== drivers/bluetooth/hci_usb.c 1.53 vs edited =====
--- 1.53/drivers/bluetooth/hci_usb.c	2004-07-16 12:55:02 +02:00
+++ edited/drivers/bluetooth/hci_usb.c	2004-07-31 12:13:10 +02:00
 <at>  <at>  -98,6 +98,9  <at>  <at>
 	/* Broadcom BCM2035 */
 	{ USB_DEVICE(0x0a5c, 0x200a), .driver_info = HCI_RESET },

+	/* ISSC Bluetooth Adapter v3.1 */
+	{ USB_DEVICE(0x1131, 0x1001), .driver_info = HCI_RESET },




-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

             reply	other threads:[~2005-06-27 10:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-27 10:53 Al Chane [this message]
2005-06-27 11:14 ` [Bluez-users] ISSC USB dongle patch 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='009401c57b06$7afe3ef0$0132a8c0@AL' \
    --to=al_chane@issc.com.tw \
    --cc=bluez-users@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