From: nirav rabara <niravrabara@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: Right way of pairing?
Date: Sat, 28 Nov 2009 11:22:46 +0530 [thread overview]
Message-ID: <912bb79a0911272152y6fb12a05p299090e97ac91a54@mail.gmail.com> (raw)
Hi,
I am newbie to bluetooth world, For pairing I am connecting RFCOM
socket, I can show this connection on /org/bluez/789(pid of
process)/hci0 as dev_00_05_AD_EF_F8_A5 and linkkey information in
linkkeys file. but when I close this RFCOM socket (or when application
kills) all the information regarding the device pairing getting lost.
Is this the right way of pairing ??
I know that API has also available for device pairing, but I want to
use Dbus as less as possible due to the time take by dbus fucntions
calls and also I am not so comfortable with dbus API.
Can anybody suggest me the right way to pair devices?? Is it
compulsory to use DBUS API for pairing OR any other way without using
Dbus API
Your suggestion would be a great help for me.....
--
With Regards,
Nirav Rabara
next reply other threads:[~2009-11-28 5:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-28 5:52 nirav rabara [this message]
2009-11-28 16:40 ` Right way of pairing? Pierre Ficheux
2009-11-30 4:30 ` nirav rabara
2009-11-30 6:17 ` nirav rabara
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=912bb79a0911272152y6fb12a05p299090e97ac91a54@mail.gmail.com \
--to=niravrabara@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
/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