From: Stefan Wiehler <sephalon@farce.de>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Replacement for rfcomm.conf
Date: Mon, 12 Jan 2015 14:08:08 +0900 [thread overview]
Message-ID: <54B356B8.1030208@farce.de> (raw)
In-Reply-To: <61857A98-EF57-4478-83B8-74DD691164ED@holtmann.org>
Hi Marcel,
> just create an init script of systemd service file and run the rfcomm
> bind command manually. As long as you know the remote BD_ADDR of the
> device you want to connect to and the RFCOMM channel of the SSP
> service on that device, you can create a binding. No local controller
> has to be present to create a RFCOMM binding.
How embarrassing that I didn't realize that by myself. Indeed this was
the simplest solution for the problem. Thank you for your help!
Kind regards,
Stefan Wiehler
prev parent reply other threads:[~2015-01-12 5:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-11 12:55 Replacement for rfcomm.conf Stefan Wiehler
2015-01-11 22:41 ` Marcel Holtmann
2015-01-12 5:08 ` Stefan Wiehler [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=54B356B8.1030208@farce.de \
--to=sephalon@farce.de \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.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).