From: Marcel Holtmann <marcel@holtmann.org>
To: Matto clamaci <matto@clamaci.net>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Re: Bluez-devel digest, Vol 1 #1053 - 3 msgs
Date: Sun, 09 May 2004 13:03:19 +0200 [thread overview]
Message-ID: <1084100599.9269.17.camel@pegasus> (raw)
In-Reply-To: <00cc01c435af$2ec5a430$3288fc17@super>
Hi Matto,
> Where can I found a completely description of bluetooth module for linux?
>
> a.. bluez-libs-2.6.tar.gz
> a.. bluez-utils-2.6.tar.gz
> a.. bluez-pan-1.1.tar.gz
> a.. bluez-hcidump-1.8.tar.gz
> a.. bluez-hciemu-1.0.tar.gz
> a.. bluez-bluefw-1.0.tar.gz
> a.. bluez-pin-0.23.tar.gz
>
> How does it work?
every packages contains a README file and actually this is a good point
to start. For your second step you should read the manpages included in
these packages and check out the documentation on www.bluez.org. If you
then have specific questions you can ask them here, but you can't expect
an answer to such a generic question like "How does it work?" ;)
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver
higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2004-05-09 11:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1BMebm-0003Y5-Fc@sc8-sf-list2.sourceforge.net>
2004-05-09 10:19 ` [Bluez-devel] Re: Bluez-devel digest, Vol 1 #1053 - 3 msgs Matto clamaci
2004-05-09 11:03 ` Marcel Holtmann [this message]
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=1084100599.9269.17.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=matto@clamaci.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