From: Jeff Wilson <jazzbotley@gmail.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] newb request
Date: Thu, 9 Dec 2004 11:15:21 -0600 [thread overview]
Message-ID: <5f30e2610412090915395a1747@mail.gmail.com> (raw)
In-Reply-To: <1102611436.9988.237.camel@pegasus>
On Thu, 09 Dec 2004 17:57:16 +0100, Marcel Holtmann <marcel@holtmann.org> wrote:
> Hi Jeff,
>
> 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
>
Thank you for your prompt reply!
Sorry, I was not very clear about that part. I use RFCOMM for the
transport. (It's been a couple of months since I wrote "Hello
World".) You are correct; I used rctest.c as my guide for that.
My frustration is trying to understand more about HCI. I'm sure there
is no way around a steep learning curve -- my objective is to get as
fine-tuned control as possible over the INQUIRY and INQUIRY_SCAN
modes. I want two nodes (with zero prior knowledge of each other) to
be able to discover each other and exchange messages within a couple
of seconds.
Thanks again for your time,
Jeff
-------------------------------------------------------
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
prev parent reply other threads:[~2004-12-09 17:15 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
2004-12-09 17:15 ` Jeff Wilson [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=5f30e2610412090915395a1747@mail.gmail.com \
--to=jazzbotley@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.