Received-SPF: pass (google.com: best guess record for domain of linux-bluetooth-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Content-Type: text/plain;
        charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.40.2.2.4\))
Subject: Re: deprecated tools: rfcomm, can we un-deprecate it?
From:   Johan Hedberg <johan.hedberg@gmail.com>
In-Reply-To: <cb73add2-cb8c-353a-5d10-134a13553cf4@message-id.googlemail.com>
Date:   Sat, 4 Jan 2020 14:18:03 +0100
Cc:     BlueZ devel list <linux-bluetooth@vger.kernel.org>,
        Marcel Holtmann <marcel@holtmann.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <7192C77E-BFF5-4507-A004-3684EDE489AC@gmail.com>
References: <0aad7250-65f9-3e4c-e5ca-434139a9ae64@message-id.googlemail.com>
 <2203E98B-B581-4C14-94DF-164D7E036234@holtmann.org>
 <fa70a57e-d5f0-a47d-f987-27b46d8275c4@message-id.googlemail.com>
 <cb73add2-cb8c-353a-5d10-134a13553cf4@message-id.googlemail.com>
To:     Stefan Seyfried <stefan.seyfried@googlemail.com>
Sender: linux-bluetooth-owner@vger.kernel.org
Precedence: bulk

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...")
>>=20
>> 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>"?
>=20
> OK, now I found https://github.com/tonyespy/bluez5-spp-example which
> explains how to do this.
>=20
> I'd still think an example in the bluez documentation would be useful,
> because=E2=80=A6

Doesn=E2=80=99t 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=E2=80=99s a two-step process, i.e. =
first you register the client role profile and then you call e.g. =
ConnectProfile (which test-profile doesn=E2=80=99t cover).

Johan