* What is the successor of /dev/rfcomm0 after the rfcomm tool be deprecated
@ 2023-11-28 7:16 joeyli
0 siblings, 0 replies; only message in thread
From: joeyli @ 2023-11-28 7:16 UTC (permalink / raw)
To: linux-bluetooth; +Cc: linux-serial, linux-kernel
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2023-11-28 7:17 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2023-11-28 7:16 What is the successor of /dev/rfcomm0 after the rfcomm tool be deprecated joeyli
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.