From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Broadcom chipset and reverse engineering
Date: Fri, 14 Oct 2005 00:53:21 +0200 [thread overview]
Message-ID: <1129244001.5057.17.camel@localhost.localdomain> (raw)
In-Reply-To: <434E9DCE.6090402@gmx.de>
Hi Benjamin,
> I am using a Broadcom chipset based USB Bluetooth dongle (Belkin F8T008)
> and I have a Logitech Mobile Pro Headset. Of course I am not able to use
> that headset with BlueZ because the Broadcom chipset is not supported.
> But it works without problems under Windows XP. I have read that the
> BlueZ developers are not able to make it work with the Broadcom chipset
> because they did not get any information about that chipset.
> So here are my questions:
> - Is it of any help if I try to log some of the USB traffic (I have
> found this program for example:
> http://sourceforge.net/projects/usbsnoop/) under my Windows XP system
> when connecting the headset and sending audio to it?
> - Is it allowed to sniff the traffic between the OS and the USB adapter
> (Is reverse engineering allowed)?
since they use H:2 as transport, you should start decoding the USBsnoop
dumps by yourself. And yes it is legal in Germany for interop purpose.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2005-10-13 22:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-13 17:47 [Bluez-users] Broadcom chipset and reverse engineering Benjamin Eikel
2005-10-13 22:53 ` Marcel Holtmann [this message]
2005-10-14 11:27 ` [Bluez-users] " Benjamin Eikel
2005-10-14 11:56 ` Marcel Holtmann
2005-10-14 16:18 ` Benjamin Eikel
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=1129244001.5057.17.camel@localhost.localdomain \
--to=marcel@holtmann.org \
--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