From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Re: Broadcom chipset and reverse engineering
Date: Fri, 14 Oct 2005 13:56:56 +0200 [thread overview]
Message-ID: <1129291016.5057.47.camel@localhost.localdomain> (raw)
In-Reply-To: <loom.20051014T130900-929@post.gmane.org>
Hi Benjamin,
> > 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.
> >
>
> Sorry, but I am new to Bluetooth development. I just searched some information
> about that 'H:2' transport and found out that this 'H:2' is the USB transport
> layer which is used for the physical transport of the HCI packets.
>
> Is there any program which could decode the HCI data automatically from the USB
> data or do I have to decode every package by hand (I think there are about 6000
> packets [and yes, only my headset was connected; no other Bluetooth devices])?
>
> Or perhaps there is an easier way: Is there any free tool that runs under
> Windows XP (I have to use Windows because the headset only works there), which
> can dump/log/sniff the HCI packets between the USB host controller and the USB
> Bluetooth adapter?
I always did it by hand.
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-14 11:56 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
2005-10-14 11:27 ` [Bluez-users] " Benjamin Eikel
2005-10-14 11:56 ` Marcel Holtmann [this message]
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=1129291016.5057.47.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