From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] BlueZ API documentation
Date: Tue, 11 Sep 2007 01:42:11 +0200 [thread overview]
Message-ID: <1189467731.7893.10.camel@violet> (raw)
In-Reply-To: <690118.53390.qm@web32905.mail.mud.yahoo.com>
Hi Brown,
> Not problem. I think I should get used to the src code.
>
> One quick question though (just to get around what I'm currently stuck
> with)
>
> I want to programatically control the disovery status of my local BT
> device.
> Meaning - my program should be able to set the BT device status so
> that other device cannot "see" it.
>
> I noticed these in hci.h
>
> #define OCF_WRITE_SCAN_ENABLE 0x001A
> #define SCAN_DISABLED 0x00
> #define SCAN_INQUIRY 0x01
> #define SCAN_PAGE 0x02
>
>
> But I am not sure what API's should be used and how.
if you wanna mess around with the HCI directly then you are on your own.
Why don't you use the nice D-Bus API we have. I gives you everything you
need and takes care of all the minor details you don't even wanna know
about.
Regards
Marcel
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2007-09-10 23:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-10 23:37 [Bluez-users] BlueZ API documentation Brown Dwarf
2007-09-10 23:42 ` Marcel Holtmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-09-10 23:17 Brown Dwarf
2007-09-10 23:22 ` 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=1189467731.7893.10.camel@violet \
--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