From: tjoconno@ncsu.edu
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] BlueZ version
Date: Wed, 8 Aug 2007 13:04:12 -0400 (EDT) [thread overview]
Message-ID: <38134.204.84.244.1.1186592652.squirrel@webmail.ncsu.edu> (raw)
In-Reply-To: <81389.49773.qm@web58001.mail.re3.yahoo.com>
Can anyone point me in the direction of the file formats for btsnoop &
hcidump? Thank you so much in advance.
TJ
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-08-08 17:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.151917.1186390010.21973.bluez-devel@lists.sourceforge.net>
2007-08-06 16:40 ` [Bluez-devel] BlueZ version hong zhang
2007-08-08 17:04 ` tjoconno [this message]
2007-08-08 17:09 ` Marcel Holtmann
2007-08-06 20:33 ` [Bluez-devel] cross compile problem on bluez hong zhang
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=38134.204.84.244.1.1186592652.squirrel@webmail.ncsu.edu \
--to=tjoconno@ncsu.edu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox