From: Marcel Holtmann <marcel@rvs.uni-bielefeld.de>
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: 15 Aug 2003 14:39:20 +0200 [thread overview]
Message-ID: <1060951166.952.57.camel@pegasus> (raw)
In-Reply-To: <Pine.GSO.4.40.0308150819560.15387-100000@prosit.control.auc.dk>
Hi Jan,
> During my master thesis, I wrote a custom Linux USB Bluetooth driver to
> comply with my specific needs. I did this because I couldn't get bluez
> working. The hardware that was available to me, was some development
> boards from Digianswer a subsidiary of Motorola. They couldn't provide
> much help, since their official driver is for Microsoft products, and they
> have outsourced the development of their driver to another company in
> Denmark.
>
> So I just wrote my own driver according to the Bluetooth USB specification
> and the spec for USB 1.1, and basically found that my driver didn't
> work:-(
>
> A sniff program on a Windows computer then revealed that Digianswer for
> some strange reason uses a different value for their control requests,
> than what is expected. I changed my #define to the correct value, and my
> driver worked perfectly.
>
> Later I tried to change the value, just to see if I could get bluez
> working, and I succeeded:-)
>
> in hci_usb.h
> change
> #define HCI_CTRL_REQ 0x20
> to
> #define HCI_CTRL_REQ 0x40
>
> And everything works just fine. Though it was a development board that I
> used, this change can possibly make bluez work with other Digianswer USB
> hardware stated as "not working" with Bluez
>
> Maybe there could be a note on the webpage to potential users of
> Digianswer hardware, that this small hack could work?
thanks for this information. I always tried to get my hands on the
Digianswer Bluetooth devices, but I never got one. Do you have a spare
one for me?
Changing the bRequestType is such an ugly hack, but on the other side it
is a very simple change to get these devices supported by hci_usb. I
will write a patch for supporting Digianswer devices and H:2 Bluetooth
devices at the same time, but I need some more information about the
your device. Please send me the output of "cat /proc/bus/usb/devices"
and "hciconfig -a".
Regards
Marcel
-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2003-08-15 12:39 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 [this message]
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
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=1060951166.952.57.camel@pegasus \
--to=marcel@rvs.uni-bielefeld.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.