From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Using ASCII based files for link key storage
Date: Sun, 17 Apr 2005 01:16:16 +0200 [thread overview]
Message-ID: <1113693376.18450.23.camel@pegasus> (raw)
In-Reply-To: <1113668583.16433.76.camel@pegasus>
Hi again,
> All the framework around these stuff is already committed to the BlueZ
> utils CVS and we need only to fill in the functions for writing and
> reading the link keys from the files. Both can be found as some kind of
> prototypes in hcid/storage.c and I would be very happy if someone fills
> these function with actual code, because I am quite busy with some other
> stuff.
I just wrote some code do deal with the link key storage and to support
the device name cache. I don't fully like it and I think it contains
some bugs, but it is better than nothing. So feel free to send me
patches to improve it. And btw using the hcitool with name cache support
is very great in my environment.
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-04-16 23:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-16 16:23 [Bluez-devel] Using ASCII based files for link key storage Marcel Holtmann
2005-04-16 17:32 ` Fred Schaettgen
2005-04-16 18:01 ` Fred Schaettgen
2005-04-16 18:33 ` Marcel Holtmann
2005-04-18 11:35 ` Marcel Holtmann
2005-04-16 19:04 ` Marcel Holtmann
2005-04-16 21:21 ` Fred Schaettgen
2005-04-16 21:38 ` Marcel Holtmann
2005-04-16 23:16 ` Marcel Holtmann [this message]
2005-04-17 18:41 ` Guylhem Aznar
2005-04-17 18:54 ` Marcel Holtmann
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=1113693376.18450.23.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox