From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] code is ok, but still unknown field type
Date: Fri, 10 Jun 2005 02:59:28 +0200 [thread overview]
Message-ID: <1118365168.5609.2.camel@notepaq> (raw)
In-Reply-To: <20050609131722.GF6606@pangeia.com.br>
Hi Nelson,
> lk2a is a ascii dump for link_key database (default in /etc/bluetooth)
>
> Field1 = key
> Field2 = bdaddr remote
> Field3 = bdaddr local
> Field4 = type (???)
> Field5 = time
>
> # ./lk2a
> 88fc30d45810b6f32cfd626c969bfc49 00:10:60:AA:9B:5B 00:60:57:DF:1D:29 0 Fri May 27 10:58:47 2005
why don't you read the Bluetooth specification to understand what type
is. Look for HCI_Link_Key_Notification.
Starting with bluez-utils-2.16 it is no longer a binary file.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput
a projector? How fast can you ride your desk chair down the office luge track?
If you want to score the big prize, get to know the little guy.
Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-06-10 0:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-07 10:06 [Bluez-devel] Build BlueZ Libs and BluzZ Utils for ARM Martin Rolsted Jensen
2005-04-07 12:19 ` Anderson Rodrigues
2005-06-09 13:17 ` [Bluez-devel] code is ok, but still unknown field type Nelson Murilo
2005-06-10 0:59 ` Marcel Holtmann [this message]
2005-06-10 1:50 ` Nelson Murilo
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=1118365168.5609.2.camel@notepaq \
--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.