From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] documentation of current bluez stack interaction?
Date: Sat, 03 Mar 2007 12:35:26 +0100 [thread overview]
Message-ID: <1172921726.24446.18.camel@aeonflux.holtmann.net> (raw)
In-Reply-To: <200702271318.52535.penguinacity@yahoo.com>
Hi Walt,
> I have a 2.6.18 kernel with blues enabled and am trying to understand
> function.
> Specifically I'm looking for how rfcomm interacts?
> All of the info at ...
> http://www.holtmann.org/linux/bluetooth/
> seems inappropriate and much says don't use this anymore.
>
> Does anyone have a pointer?
> Maybe some of this stuff should be made inaccessible? It could be VERY
> confusing to folks.
> Is there no owner for this?
you have to look at the source code. RFCOMM provides socket and TTY
interfaces. All other configuration and interaction can be done over
D-Bus.
Regards
Marcel
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2007-03-03 11:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-27 18:18 [Bluez-users] documentation of current bluez stack interaction? Walt Shekrota
2007-03-03 11:35 ` 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=1172921726.24446.18.camel@aeonflux.holtmann.net \
--to=marcel@holtmann.org \
--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