From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] a2dp timing
Date: Fri, 25 Mar 2005 18:28:13 +0100 [thread overview]
Message-ID: <1111771693.9195.130.camel@pegasus> (raw)
In-Reply-To: <20050325172338.GB7214@externe.net>
Hi Guylhem,
> > > However I don't have the bluesoleil stack....
> >
> > do you have the Frontline FTS4BT or the CATC Merlin II sniffer?
>
> Looks like it's dedicated hardware - nope. I though some software
> sniffing was possible (ala tcpdump with hcidump)
not for air sniffing and that is what you actually need in this case.
Regards
Marcel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-03-25 17:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-25 5:00 [Bluez-devel] a2dp timing Brad Midgley
2005-03-25 13:14 ` Marcel Holtmann
2005-03-25 14:22 ` Guylhem Aznar
2005-03-25 14:26 ` Marcel Holtmann
2005-03-25 17:23 ` Guylhem Aznar
2005-03-25 17:28 ` Marcel Holtmann [this message]
2005-03-25 18:14 ` btlog anyone? " Brad Midgley
2005-03-25 16:44 ` Brad Midgley
2005-03-25 17:31 ` Marcel Holtmann
2005-04-04 17:14 ` Brad Midgley
2005-04-05 15:12 ` Marcel Holtmann
-- strict thread matches above, loose matches on Subject: below --
2005-04-14 8:04 Mayank Batra
2005-04-14 8:17 ` Brad Midgley
2005-04-15 9:41 Mayank Batra
2005-04-16 20:32 ` Henryk Plötz
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=1111771693.9195.130.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@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 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.