From: Johan Hedberg <johan.hedberg@gmail.com>
To: Stefan Seyfried <stefan.seyfried@googlemail.com>
Cc: BlueZ devel list <linux-bluetooth@vger.kernel.org>,
Marcel Holtmann <marcel@holtmann.org>
Subject: Re: deprecated tools: rfcomm, can we un-deprecate it?
Date: Sat, 4 Jan 2020 14:18:03 +0100 [thread overview]
Message-ID: <7192C77E-BFF5-4507-A004-3684EDE489AC@gmail.com> (raw)
In-Reply-To: <cb73add2-cb8c-353a-5d10-134a13553cf4@message-id.googlemail.com>
Hi Stefan,
On 4. Jan 2020, at 13.45, Stefan Seyfried <stefan.seyfried@googlemail.com> wrote:
>> This would be for creating a "rfcomm service" for other devices to
>> connect to, right? (The equivalent of "rfcomm listen...")
>>
>> But how would I connect e.g. to my serial module (I got this for trying
>> it by myself instead of relying on bugreporters results...), so what's
>> the dbus equivalent of "rfcomm connect hci0 <bdaddr> <channel>"?
>
> OK, now I found https://github.com/tonyespy/bluez5-spp-example which
> explains how to do this.
>
> I'd still think an example in the bluez documentation would be useful,
> because…
Doesn’t test/test-profile give a pretty good overview of both server- and client-role usage of the Profile D-Bus API? The main difference to the RFCOMM ioctls is that instead of a TTY you get a file descriptor (which I guess you could convert to a TTY using a pty). For client, another difference is that it’s a two-step process, i.e. first you register the client role profile and then you call e.g. ConnectProfile (which test-profile doesn’t cover).
Johan
next prev parent reply other threads:[~2020-01-04 13:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-22 10:04 deprecated tools: rfcomm, can we un-deprecate it? Stefan Seyfried
2019-12-26 20:40 ` Marcel Holtmann
2019-12-31 17:35 ` Stefan Seyfried
2020-01-04 12:45 ` Stefan Seyfried
2020-01-04 13:18 ` Johan Hedberg [this message]
2020-01-07 13:49 ` Stefan Seyfried
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=7192C77E-BFF5-4507-A004-3684EDE489AC@gmail.com \
--to=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=stefan.seyfried@googlemail.com \
/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).