From: Embedded System <embed.sys@gmail.com>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] how can I understand hcidump output
Date: Wed, 2 Feb 2005 23:31:59 +0800 [thread overview]
Message-ID: <c93f2a2905020207313a44e8ff@mail.gmail.com> (raw)
In-Reply-To: <4200EC42.9020004@prim-time.fr>
hi, Xavier
Merici! :) have downloaded v1.1 and took a look, very useful and clear!!!
all the best,
andy
On Wed, 02 Feb 2005 16:05:38 +0100, Xavier Garreau
<x.garreau@prim-time.fr> wrote:
> > Some of the hcidump is easy to understand, such as aid, but what is
> > scid, dcid, flags and etc. Is there any document helpful?
> >
> > Thanks a lot for your time.
>
> Well ... These are the same terms used in the Bluetooth Specification
> ... Download and read it ...
>
> Regards,
> Xavier
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
> Tool for open source databases. Create drag-&-drop reports. Save time
> by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
> Download a FREE copy at http://www.intelliview.com/go/osdn_nl
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users
>
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2005-02-02 15:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-02 14:54 [Bluez-users] how can I understand hcidump output Embedded System
2005-02-02 15:05 ` Xavier Garreau
2005-02-02 15:31 ` Embedded System [this message]
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=c93f2a2905020207313a44e8ff@mail.gmail.com \
--to=embed.sys@gmail.com \
--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