From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Definition of hci_conn_info_req
Date: Fri, 02 Dec 2005 12:01:51 +0100 [thread overview]
Message-ID: <1133521311.11226.41.camel@blade> (raw)
In-Reply-To: <94e407f00512020254pb83407ds7fec44efaaca1385@mail.gmail.com>
Hi Arpit,
> > no, it is not.
>
> What does hci_conn_info_req do then?Any documentation anywhere?I'm
> kinda lost with all the Bluez code.
you can get information about the current established connections.
> > Depends on how you convert the address. Use ba2str().
>
> Yes I'm using ba2str to convert.My question is, should &cr->bdaddr
> contain the address of the remote bluetooth device?
>
> char add[18];
> struct hci_conn_info_req *cr;
> cr = malloc(sizeof(*cr) + sizeof(struct hci_conn_info));
> bacpy( &cr->bdaddr, &bdaddr );
> ba2str( &bdaddr, add);
> printf("Bluetooth address-remote device: %s \n", add);
> cr->type = ACL_LINK;
>
> Everytime I run the executable C, I get a different value for
> &cr->bdaddr.
Where does bdaddr come from?
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2005-12-02 11:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-02 10:22 [Bluez-users] Definition of hci_conn_info_req Arpit Rai
2005-12-02 10:33 ` Marcel Holtmann
2005-12-02 10:54 ` Arpit Rai
2005-12-02 11:01 ` Marcel Holtmann [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=1133521311.11226.41.camel@blade \
--to=marcel@holtmann.org \
--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;
as well as URLs for NNTP newsgroup(s).