public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Brown Dwarf <brown_drf@yahoo.com>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] BlueZ API documentation
Date: Mon, 10 Sep 2007 16:37:09 -0700 (PDT)	[thread overview]
Message-ID: <690118.53390.qm@web32905.mail.mud.yahoo.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1924 bytes --]

Thanks for the quick Marcel.

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.
I'll be happy to update the wiki with these kind of info - if thats useful

~bd

----- Original Message ----
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Sent: Monday, September 10, 2007 4:22:00 PM
Subject: Re: [Bluez-users] BlueZ API documentation


Hi Brown,

>     Where can I find the documentation for BlueZ API's ? I'm looking
> for documentations for hci_xxx functions.
> 
> I looked under bluez wiki and HOWTO pages but did not find anything
> specific to API documentation. 

the Bluetooth library is not really documented. Use the source, Luke ;)

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


       
____________________________________________________________________________________
Boardwalk for $500? In 2007? Ha! Play Monopoly Here and Now (it's updated for today's economy) at Yahoo! Games.
http://get.games.yahoo.com/proddesc?gamekey=monopolyherenow  

[-- Attachment #1.2: Type: text/html, Size: 4507 bytes --]

[-- Attachment #2: Type: text/plain, Size: 228 bytes --]

-------------------------------------------------------------------------
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/

[-- Attachment #3: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

             reply	other threads:[~2007-09-10 23:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-10 23:37 Brown Dwarf [this message]
2007-09-10 23:42 ` [Bluez-users] BlueZ API documentation Marcel Holtmann
  -- 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=690118.53390.qm@web32905.mail.mud.yahoo.com \
    --to=brown_drf@yahoo.com \
    --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