From: Stefan Wiehler <sephalon@farce.de>
To: linux-bluetooth@vger.kernel.org
Subject: Replacement for rfcomm.conf
Date: Sun, 11 Jan 2015 21:55:04 +0900 [thread overview]
Message-ID: <54B272A8.4000105@farce.de> (raw)
Hello everybody,
I recently added a Bluetooth dongle to a RS232 device to get readouts
from a remote location. This is working fine as long as I execute
"rfcomm bind" after each restart.
However, when I wanted to automate this process by using a rfcomm.conf
file as suggested by several guides on the web [1], I realized that the
corresponding code has been removed from the rfcomm tool several years
ago [2].
I tried to use udev as a replacement by writing a rule which executes
rfcomm after pairing, but it seems like sysfs does not expose
information about coupled devices (udevadm info -a -p
/sys/class/bluetooth/hci0).
Is it possible to solve that problem using udev? Or are there any other
best practices? Thank you for your consideration.
Kind regards,
Stefan Wiehler
[1] http://askubuntu.com/a/252235
[2]
http://git.kernel.org/cgit/bluetooth/bluez.git/commit/?id=5bec57420bd57f86d61b2919450d182f3407facf
next reply other threads:[~2015-01-11 12:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-11 12:55 Stefan Wiehler [this message]
2015-01-11 22:41 ` Replacement for rfcomm.conf Marcel Holtmann
2015-01-12 5:08 ` Stefan Wiehler
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=54B272A8.4000105@farce.de \
--to=sephalon@farce.de \
--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 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.