From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Querying device information.
Date: Wed, 06 Jul 2005 14:26:27 +0200 [thread overview]
Message-ID: <1120652788.8836.7.camel@pegasus> (raw)
In-Reply-To: <20050706120934.GW21449@beta.private.mielke.cc>
Hi Dave,
> If, from a user-space application, I have a socket which has been created via:
>
> socket(PF_BLUETOOTH, SOCK_STREAM, BTPROTO_RFCOMM)
>
> are there any special Bluetooth ioctls which can be used to, for example, query
> device information? If so, where can I find and/or read about them? Is there
> another interface I should be using? Thanks.
this depends on the information you want. In general you need to use the
BlueZ HCI API.
Regards
Marcel
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&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-07-06 12:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-06 11:37 [Bluez-devel] Moving over to GCC 4.0 Marcel Holtmann
2005-07-06 12:09 ` [Bluez-devel] Querying device information Dave Mielke
2005-07-06 12:26 ` Marcel Holtmann [this message]
2005-07-06 12:33 ` Dave Mielke
2005-07-06 12:43 ` Marcel Holtmann
2005-07-09 4:10 ` [Bluez-devel] hcid dies on socket connect attempt Dave Mielke
2005-07-09 7:43 ` Marcel Holtmann
2005-07-06 15:24 ` [Bluez-devel] Moving over to GCC 4.0 Brad Midgley
2005-07-06 16:57 ` Marcel Holtmann
2005-07-06 17:02 ` Peter Robinson
2005-07-06 17:09 ` Marcel Holtmann
2005-07-06 16:35 ` Luiz Fernando Capitulino
2005-07-06 17:48 ` 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=1120652788.8836.7.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