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;
Subject: Re: deprecated tools: rfcomm, can we un-deprecate it?
To:     BlueZ devel list <linux-bluetooth@vger.kernel.org>
Cc:     Johan Hedberg <johan.hedberg@gmail.com>,
        Marcel Holtmann <marcel@holtmann.org>
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>
 <7192C77E-BFF5-4507-A004-3684EDE489AC@gmail.com>
From:   Stefan Seyfried <stefan.seyfried@googlemail.com>
Message-ID: <0524896a-fedc-463d-14ac-370de38467de@message-id.googlemail.com>
Date:   Tue, 7 Jan 2020 14:49:17 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101
 Thunderbird/68.2.1
MIME-Version: 1.0
In-Reply-To: <7192C77E-BFF5-4507-A004-3684EDE489AC@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Sender: linux-bluetooth-owner@vger.kernel.org
Precedence: bulk

Hi Johan,

Am 04.01.20 um 14:18 schrieb Johan Hedberg:
> 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?

You are right, now that I know what I am looking for, this is exactly the example code that I need ;-)

> 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).

I'll try to cook up an example application (if I get some spare time...) for the
(apparently) #1 wanted application of old rfcomm:
connecting to a "serial console" via bluetooth and then starting a terminal program on /dev/rfcomm0

This should be possible by either providing a local socket that can be connected to or a pty.

We can then decide if we include this in the bluez examples or if I provide it as a
separate project.

Best regards ans thanks for the info,

	Stefan
-- 
Stefan Seyfried

"For a successful technology, reality must take precedence over
 public relations, for nature cannot be fooled." -- Richard Feynman