Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.33 as permitted sender) client-ip=23.128.96.33;
Date:   Tue, 28 Nov 2023 15:16:11 +0800
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
Message-ID: <20231128071611.GA5154@linux-l9pv.suse>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.11.4 (2019-03-13)
MIME-Version: 1.0
X-MS-Exchange-AntiSpam-MessageData-ChunkCount: 1
X-MS-Exchange-AntiSpam-MessageData-0: =?us-ascii?Q?oFlcbdqMkBJ58HRKGR5s6J1olr1UfkpJDJ4rMDNCJiPmBYEqFtx+vWgW7jxZ?=
 =?us-ascii?Q?qrvIj5E+Cu83aDDVxnIZdMPLlUIbKU9KN35aq8aLtBBmn4lhgqt6y71RjMG1?=
 =?us-ascii?Q?8XyS7VhQzuzJTdI3+kBOnghnnYD28wziUIf8sK69GYtNz87nZApWFCsdWsrs?=
 =?us-ascii?Q?77aoXIEepRQZm/OGDsmrnZ5wmq84awuN6Nf61InqSf1WWvi/sZ0NZ5CC5MME?=
 =?us-ascii?Q?uA3tgYjO5XnYfoIBmUv0ObUuoSKV69qgycqJKE5WrshWJ5lY5EIfxKzCTMyn?=
 =?us-ascii?Q?d5j0z6vcXDr+CYaNWrtNz4tEIwGMYKJqiwSsAEVYljkc+Q2iiCfK2nnIjjzh?=
 =?us-ascii?Q?14auC1T5NSZtnAPtb9yR5E6FsKf8glrTztM5cw5FEewslKn2kthBPYSv3HHA?=
 =?us-ascii?Q?Ta7cAu0Q47HF9boBmyTAXmTAOhkBeUvo5Mdp7xq/3MSriA1CrNJQYDAfDr9g?=
 =?us-ascii?Q?19VrUIT4wAVamAkvPx5G0YfS+G9jhvyyZh8oEFxPdnNNySl3/a/DrIV5ytLc?=
 =?us-ascii?Q?1e1yQjwJM2fNk3h1HH9IIDC6jnOsrp27Z3MvUZ62XHT4YL9p8B2S6hVPJSda?=
 =?us-ascii?Q?OdzrMFQ96JtYB6PNTIIr4wIm63rK+Vh8EK6xtcV+Qh889i8slIurgHX54WTE?=
 =?us-ascii?Q?JXO3u2RCjjtY8BiptBqfXnDPXpbXhqWdQdqISTqBRJoFDioyrDXp3bA1+8kk?=
 =?us-ascii?Q?psopC0OJCn2RCTrCDaJQJrWEaHBKlGkr9v8pTWt2Hj1tBmRq4hANpzISnMCe?=
 =?us-ascii?Q?WN6/v8j7D3mSxwA0h2ZKr1KvuMKZgAmC+uslqGg1kPniHSADw5yyc32m9jp4?=
 =?us-ascii?Q?ARE+kCcjPidHQNSYzs3K+A8s9G4+w54sB98Aoh3VwkjYqpr3mgB6KOJottn6?=
 =?us-ascii?Q?mIp8lAwVIrWIlFeFF68SCzV4nhrRB4BKQzb+FhjCIfw6UXMBr06WUQBZSNPk?=
 =?us-ascii?Q?vLUBAOtKJ0AKA4zFyE7rqNkP7LC50HXfqIW3EbDJiae2VwSMWc/1P0xp21dX?=
 =?us-ascii?Q?QvVX0kJ/9m91dUTRqenWnNTFDDiw6CooPJ3buFKTrHmQ45ssbxvnMTO+kCVe?=
 =?us-ascii?Q?+eRFIBUFlhw6hjyhqzXoY1k+sC5IAeDYPdoRKVqQ8LWh3S8THlRpR/l/Rka0?=
 =?us-ascii?Q?JPR7JUEYSToDHeGhSpRwUCS+//VjxeS50Fbpgq/kUkshr3zGssz+CLFnIBfy?=
 =?us-ascii?Q?SO2+Q1IysMCP1VJtlI4+GPup1ikTnqGFvDg1BwLTyeUT2loB2WGsKGxMmHmk?=
 =?us-ascii?Q?bLqNqVSI+gtmpHrZqAdidMLvW091dgQxqhNyTx4gGqVdCHI4XFC1/l4hkvX6?=
 =?us-ascii?Q?C5UP7AfDMM+gUHcgTccoI0j770qIF4f9T/NlszFhUpKWaqJOZWhXcGAsH6hY?=
 =?us-ascii?Q?v82UE+ynStb3E3mkI6hu1LuoMkwwIoX+c74p7I7jS0y1o8Qkqj/7qCGWvyCv?=
 =?us-ascii?Q?K9v5IW+7q7dfW/4pi61mjGUEdsui9+BCL2oRpqntzEVWC4ruvNhrV7LvB5WN?=
 =?us-ascii?Q?rO54c9klW4LE0sAnNEb/RLJk+SavvPsriN9GE1tnnXlzK/98aYmzksgIanEP?=
 =?us-ascii?Q?2W/AIUtwuB/WJg+FN7M=3D?=
X-OriginatorOrg: suse.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 0b8ce22b-5aac-4482-e22b-08dbefe1eb22
X-MS-Exchange-CrossTenant-AuthSource: DB8PR04MB7164.eurprd04.prod.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 28 Nov 2023 07:16:19.6150
 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: f7a17af6-1c5c-4a36-aa8b-f5be247aa4ba
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: T0jmkmel0JwrovwP7dAFHP22QfmI5cWgSfy3bLnxKlbALJlRtc+TruSH6FuU2wtn
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM8PR04MB7284
X-Spam-Status: No, score=-0.9 required=5.0 tests=DKIM_SIGNED,DKIM_VALID,
	DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,
	SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=unavailable
	autolearn_force=no version=3.4.6
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lipwig.vger.email
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.4 (lipwig.vger.email [0.0.0.0]); Mon, 27 Nov 2023 23:17:48 -0800 (PST)

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