From: Marcel Holtmann <marcel@holtmann.org>
To: Stefan Mischke <survivor@uni-paderborn.de>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] L2CAP and SDP interface specification?
Date: Mon, 05 Apr 2004 17:40:07 +0200 [thread overview]
Message-ID: <1081179607.2843.9.camel@pegasus> (raw)
In-Reply-To: <407174BC.8020503@uni-paderborn.de>
Hi Stefan,
> where can I find the specification of the BlueZ L2CAP and SDP API? I
> hope there ist any.
the L2CAP API is a socket interface and you will find the API in the
bluetooth/l2cap.h header file. For an usage example look at l2test.
The SDP API can be found in bluetooth/sdp.h and bluetooth/sdp_lib.h and
for example code look at the dund and pand applications.
> And how can I register my application for getting HCI events, so that I
> don't have to poll? hcid? API/specs?
The HCI API is also a socket interface. If you want to have some kind of
event based approach you have to use and IO event main loop like it is
used in the Glib.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&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:[~2004-04-05 15:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-05 15:01 [Bluez-devel] L2CAP and SDP interface specification? Stefan Mischke
2004-04-05 15:40 ` Marcel Holtmann [this message]
2004-04-05 16:25 ` Stefan Mischke
2004-04-07 14:39 ` 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=1081179607.2843.9.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=survivor@uni-paderborn.de \
/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