All of lore.kernel.org
 help / color / mirror / Atom feed
From: joeyli <jlee@suse.com>
To: linux-bluetooth@vger.kernel.org
Cc: linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: What is the successor of /dev/rfcomm0 after the rfcomm tool be deprecated
Date: Tue, 28 Nov 2023 15:16:11 +0800	[thread overview]
Message-ID: <20231128071611.GA5154@linux-l9pv.suse> (raw)

Hi bluetooth experts, 

I am learning user space programming for bluetooth. I have tried
a simple python script as a socket client for access /dev/rfcomm0 success.
I created the /dev/rfcomm0 device by "rfcomm bind" command. It works fine.

But after the rfcomm tool be deprecated in bluez. I didn't see any
successor of /dev/rfcomm0 or rfcomm tool. I read this article:

http://www.bluez.org/the-management-interface/  

Does that mean all scripts/applications base on rfcomm tool and /dev/rfcomm0
need to be rewritten by using bluetoothd-dbus API? Do we have any solution
to keep those old socket scripts work as is? For example: Forwarding socket
request of /dev/rfcomm0 to bluetoothd?

Thanks a lot!
Joey Lee

                 reply	other threads:[~2023-11-28  7:17 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20231128071611.GA5154@linux-l9pv.suse \
    --to=jlee@suse.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@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.