From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] newb request
Date: Thu, 09 Dec 2004 17:57:16 +0100 [thread overview]
Message-ID: <1102611436.9988.237.camel@pegasus> (raw)
In-Reply-To: <5f30e2610412090850b7f5f85@mail.gmail.com>
Hi Jeff,
> I have about 5 years experience with sockets programming, but I am new
> to BlueZ. I am interested in developing applications using HCI. I
> have skimmed through the Bluetooth specifications (through 2.0) and I
> have created a "Hello World" app using hcitool.c (bluez-utils-2.7) as
> a guide.
>
> What other documents are available? Is there a FAQ, man page, or a
> central location for API documentation somewhere? Looking at the
> source of hcitool is helpful, but it only gets me so far. Where can I
> get more details?
>
> I am looking for anything to help me translate the Bluetooth spec into
> the practical workings of the BlueZ implementation.
I think what you really wanna do is using L2CAP or RFCOMM as transport
layers and so better look a l2test.c and rctest.c files.
Regards
Marcel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-12-09 16:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-09 16:50 [Bluez-devel] newb request Jeff Wilson
2004-12-09 16:57 ` Marcel Holtmann [this message]
2004-12-09 17:15 ` Jeff Wilson
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=1102611436.9988.237.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