From: "Grégoire Gentil" <gregoire@gentil.com>
To: linux-bluetooth@vger.kernel.org
Subject: rfcomm without bluetoothd?
Date: Thu, 29 Dec 2016 15:34:57 -0800 [thread overview]
Message-ID: <f4fea7cd-a68c-abc4-3e5e-c4ff80df118c@gentil.com> (raw)
Hello,
I'm posting here because there doesn't seem to be any more the
bluez-users mailing list.
I have a very optimized and constrained embedded device and I would like
to use rfcomm WITHOUT dbus and bluetoothd daemon.
The following works:
dbus-daemon --system --fork
bluetoothd
sdptool add --channel=22 SP
rfcomm listen /dev/rfcomm0 22
but I would like to use rfcomm without dbus and bluetoothd running. How
could I do that?
For reference, hidd works without bluetoothd so it's possible to
associate and have some bluetooth communication in the kernel directly
from a user-space application without bluetoothd running.
Many thanks in advance for any idea,
Grégoire
next reply other threads:[~2016-12-29 23:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-29 23:34 Grégoire Gentil [this message]
2016-12-30 7:21 ` rfcomm without bluetoothd? Johan Hedberg
2018-05-18 17:40 ` Where is the documentation of l2cap_options? Grégoire Gentil
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=f4fea7cd-a68c-abc4-3e5e-c4ff80df118c@gentil.com \
--to=gregoire@gentil.com \
--cc=linux-bluetooth@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).