Hi,
i have an el-cheapo USB BT dongle in front of me that throws an endless
stream of
kernel: hci_scodata_packet: hci1 SCO packet for unknown connection handle 0
after inserting it into the USB port, unless i do
echo 1 > /sys/module/hci_usb/parameters/isoc
I don't know about the usual practice in such cases: do those devices get
blacklisted in the drivers? If yes, what information should i provide to
get it into the blacklist?
-- =
Stefan Seyfried \ "I didn't want to write for pay. I
QA / R&D Team Mobile Devices \ wanted to be paid for what I write."
SUSE LINUX Products GmbH, N=FCrnberg \ -- Leonard Cohen
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easi=
er
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat=3D1=
21642
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel
Hi Stefan,
> > > > actually with isco=1 the SCO transfers are still on, but limited to
> > > > 8-bit instead of 16-bit with isoc=2. So if you have isoc=2 it fills up
> > > > your syslog. Can you extract some of these SCO packets with hcidump for
> > > > me.
>
> > > root@strolchi:~# hcidump -i hci1
> > > HCI sniffer - Bluetooth packet analyzer ver 1.29
> > > device: hci1 snap_len: 1028 filter: 0xffffffff
> > > > SCO data: handle 0 dlen 0
> > > > SCO data: handle 0 dlen 0
>
> > > This happens immediately after plugging the thing in, there is no pairing
> > > or any application involved that might trigger this AFAICT.
> >
> > Another RTX based dongle with RTX chip (0400:0807) has already been
> > blacklisted by me. I have no idea, why they can't get this right.
>
> > It would be interesting if this will work with isoc=1 and a 16-bit PCM
> > stream. You should really try some stuff from the btsco package.
>
> I did this and could not get it to work at all, means it did not play any sound
> with btsco and aplay to a Belkin F8T060xHDST headset. I got some "pops" on the
> earpiece when opening the device, but it did not play back anything.
>
> The headset worked with a Belkin F8T013 after applying the SCO MTU patch and
> with a Gigabyte GN-BTD02 out of the box. The SCO MTU patch did not help for
> the Abe dongle.
>
> I guess this piece of silicon is just plain crap :-)
it is the same as the Vivanco one, which I also have a bug report for:
lsusb: Bus 003 Device 004: ID 0400:080a National Semiconductor Corp.
And yes, they are a piece of crap when it comes to ISOC transfers. We
can only mark the SCO support as broken.
Regards
Marcel
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel
Hi,
On Fri, Jul 14, 2006 at 03:54:38PM +0200, Marcel Holtmann wrote:
> Hi Stefan,
> =
> > > actually with isco=3D1 the SCO transfers are still on, but limited to
> > > 8-bit instead of 16-bit with isoc=3D2. So if you have isoc=3D2 it fil=
ls up
> > > your syslog. Can you extract some of these SCO packets with hcidump f=
or
> > > me.
=
> > root@strolchi:~# hcidump -i hci1
> > HCI sniffer - Bluetooth packet analyzer ver 1.29
> > device: hci1 snap_len: 1028 filter: 0xffffffff
> > > SCO data: handle 0 dlen 0
> > > SCO data: handle 0 dlen 0
> > This happens immediately after plugging the thing in, there is no pairi=
ng
> > or any application involved that might trigger this AFAICT.
> =
> Another RTX based dongle with RTX chip (0400:0807) has already been
> blacklisted by me. I have no idea, why they can't get this right.
=
> It would be interesting if this will work with isoc=3D1 and a 16-bit PCM
> stream. You should really try some stuff from the btsco package.
I did this and could not get it to work at all, means it did not play any s=
ound
with btsco and aplay to a Belkin F8T060xHDST headset. I got some "pops" on =
the
earpiece when opening the device, but it did not play back anything.
The headset worked with a Belkin F8T013 after applying the SCO MTU patch and
with a Gigabyte GN-BTD02 out of the box. The SCO MTU patch did not help for
the Abe dongle.
I guess this piece of silicon is just plain crap :-)
Details for your blacklisting pleasure:
cf51:~ # lsusb -s 1:19
Bus 001 Device 019: ID 0400:080a National Semiconductor Corp.
cf51:~ # hciconfig -a
hci0: Type: USB
BD Address: 00:0C:78:31:11:0A ACL MTU: 339:4 SCO MTU: 64:9
UP RUNNING PSCAN ISCAN
RX bytes:1108 acl:0 sco:0 events:63 errors:0
TX bytes:348 acl:0 sco:0 commands:24 errors:0
Features: 0xff 0xff 0x81 0x00 0x18 0x18 0x00 0x00
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: 'BlueZ cf51 (0)'
Class: 0x100100
Service Classes: Object Transfer
Device Class: Computer, Uncategorized
HCI Ver: 1.2 (0x2) HCI Rev: 0x222 LMP Ver: 1.2 (0x2) LMP Subver: 0x=
222
Manufacturer: RTX Telecom A/S (21)
-- =
Stefan Seyfried \ "I didn't want to write for pay. I
QA / R&D Team Mobile Devices \ wanted to be paid for what I write."
SUSE LINUX Products GmbH, N=FCrnberg \ -- Leonard Cohen
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3DDE=
VDEV
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel
Hi,
On Fri, Jul 14, 2006 at 03:54:38PM +0200, Marcel Holtmann wrote:
=
> the preferred way would be "hcidump -i hci1 -X -V" to have full decoding
> support, but for SCO this doesn't really matter.
Ok, i'll note this on my cheat sheet :-)
> It would be interesting if this will work with isoc=3D1 and a 16-bit PCM
> stream. You should really try some stuff from the btsco package.
Audio and sco is on my todo list for next week, i'll report back after
trying it.
-- =
Stefan Seyfried \ "I didn't want to write for pay. I
QA / R&D Team Mobile Devices \ wanted to be paid for what I write."
SUSE LINUX Products GmbH, N=FCrnberg \ -- Leonard Cohen
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easi=
er
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat=3D1=
21642
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel
Hi Stefan,
> > actually with isco=1 the SCO transfers are still on, but limited to
> > 8-bit instead of 16-bit with isoc=2. So if you have isoc=2 it fills up
> > your syslog. Can you extract some of these SCO packets with hcidump for
> > me.
>
> ok, it looks like this (hoping that i invoked hcidump correctly, i am still
> learning this bluetooth thingy :-):
the preferred way would be "hcidump -i hci1 -X -V" to have full decoding
support, but for SCO this doesn't really matter.
> root@strolchi:~# hcidump -i hci1
> HCI sniffer - Bluetooth packet analyzer ver 1.29
> device: hci1 snap_len: 1028 filter: 0xffffffff
> > SCO data: handle 0 dlen 0
> > SCO data: handle 0 dlen 0
> > SCO data: handle 0 dlen 0
> > SCO data: handle 0 dlen 0
> > SCO data: handle 0 dlen 0
> > SCO data: handle 0 dlen 0
> > SCO data: handle 0 dlen 0
> > SCO data: handle 0 dlen 0
> > SCO data: handle 0 dlen 0
> > SCO data: handle 0 dlen 0
>
> This happens immediately after plugging the thing in, there is no pairing
> or any application involved that might trigger this AFAICT.
Another RTX based dongle with RTX chip (0400:0807) has already been
blacklisted by me. I have no idea, why they can't get this right.
> > Any chance of a name or identification of this dongle?
>
> It is an Abe UB20S, http://www.abe-hk.com/english/products/ub12-22/ub12-22.htm
> The FCC ID is NV6-CS8024.
> It is sold e.g. by conrad.com in germany and pretty cheap (around 10 Euro),
> and it is pretty small (this is why i bought it, i can leave it plugged in
> when putting the notebook into the bag :-)
It would be interesting if this will work with isoc=1 and a 16-bit PCM
stream. You should really try some stuff from the btsco package.
Regards
Marcel
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel
Hi,
On Tue, Jul 11, 2006 at 03:46:31PM +0200, Marcel Holtmann wrote:
> Hi Stefan,
=
> actually with isco=3D1 the SCO transfers are still on, but limited to
> 8-bit instead of 16-bit with isoc=3D2. So if you have isoc=3D2 it fills up
> your syslog. Can you extract some of these SCO packets with hcidump for
> me.
ok, it looks like this (hoping that i invoked hcidump correctly, i am still
learning this bluetooth thingy :-):
root@strolchi:~# hcidump -i hci1
HCI sniffer - Bluetooth packet analyzer ver 1.29
device: hci1 snap_len: 1028 filter: 0xffffffff
> SCO data: handle 0 dlen 0
> SCO data: handle 0 dlen 0
> SCO data: handle 0 dlen 0
> SCO data: handle 0 dlen 0
> SCO data: handle 0 dlen 0
> SCO data: handle 0 dlen 0
> SCO data: handle 0 dlen 0
> SCO data: handle 0 dlen 0
> SCO data: handle 0 dlen 0
> SCO data: handle 0 dlen 0
This happens immediately after plugging the thing in, there is no pairing
or any application involved that might trigger this AFAICT.
> My problem is now that I can only fully blacklist the SCO support for
> this dongle. I can't force the Bluetooth core into using 8-bit only.
Maybe i should try if SCO works at all with this thing :-)
=
> Any chance of a name or identification of this dongle?
It is an Abe UB20S, http://www.abe-hk.com/english/products/ub12-22/ub12-22.=
htm
The FCC ID is NV6-CS8024.
It is sold e.g. by conrad.com in germany and pretty cheap (around 10 Euro),
and it is pretty small (this is why i bought it, i can leave it plugged in
when putting the notebook into the bag :-)
-- =
Stefan Seyfried \ "I didn't want to write for pay. I
QA / R&D Team Mobile Devices \ wanted to be paid for what I write."
SUSE LINUX Products GmbH, N=FCrnberg \ -- Leonard Cohen
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easi=
er
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat=3D1=
21642
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel
Hi Stefan,
> > > i have an el-cheapo USB BT dongle in front of me that throws an endless
> > > stream of
> > > kernel: hci_scodata_packet: hci1 SCO packet for unknown connection handle 0
> > > after inserting it into the USB port, unless i do
> > > echo 1 > /sys/module/hci_usb/parameters/isoc
> > >
> > > I don't know about the usual practice in such cases: do those devices get
> > > blacklisted in the drivers? If yes, what information should i provide to
> > > get it into the blacklist?
> >
> > what does "hciconfig -a" tells you about this dongle? The content
>
> root@strolchi:~# hciconfig -a hci1
> hci1: Type: USB
> BD Address: 00:0C:78:31:11:0A ACL MTU: 339:4 SCO MTU: 60:9
> UP RUNNING
> RX bytes:419 acl:0 sco:0 events:19 errors:0
> TX bytes:319 acl:0 sco:0 commands:17 errors:0
> Features: 0xff 0xff 0x81 0x00 0x18 0x18 0x00 0x00
> Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
> Link policy: RSWITCH HOLD SNIFF PARK
> Link mode: SLAVE ACCEPT
> Name: 'BlueZ strolchi (1)'
> Class: 0x100100
> Service Classes:
> Device Class: Computer, Uncategorized
> HCI Ver: 1.2 (0x2) HCI Rev: 0x222 LMP Ver: 1.2 (0x2) LMP Subver: 0x222
> Manufacturer: RTX Telecom A/S (21)
>
> > from /proc/bus/usb/devices for this device might also be helpful.
>
> T: Bus=02 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 3 Spd=12 MxCh= 0
> D: Ver= 1.10 Cls=e0(unk. ) Sub=01 Prot=01 MxPS= 8 #Cfgs= 1
> P: Vendor=0400 ProdID=080a Rev= 1.00
> C:* #Ifs= 2 Cfg#= 1 Atr=80 MxPwr= 0mA
> I: If#= 0 Alt= 0 #EPs= 3 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
> E: Ad=81(I) Atr=03(Int.) MxPS= 64 Ivl=1ms
> E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
> E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
> I: If#= 1 Alt= 0 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
> E: Ad=83(I) Atr=01(Isoc) MxPS= 0 Ivl=1ms
> E: Ad=03(O) Atr=01(Isoc) MxPS= 0 Ivl=1ms
> I: If#= 1 Alt= 1 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
> E: Ad=83(I) Atr=01(Isoc) MxPS= 9 Ivl=1ms
> E: Ad=03(O) Atr=01(Isoc) MxPS= 9 Ivl=1ms
> I: If#= 1 Alt= 2 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
> E: Ad=83(I) Atr=01(Isoc) MxPS= 17 Ivl=1ms
> E: Ad=03(O) Atr=01(Isoc) MxPS= 17 Ivl=1ms
> I: If#= 1 Alt= 3 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
> E: Ad=83(I) Atr=01(Isoc) MxPS= 25 Ivl=1ms
> E: Ad=03(O) Atr=01(Isoc) MxPS= 25 Ivl=1ms
> I: If#= 1 Alt= 4 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
> E: Ad=83(I) Atr=01(Isoc) MxPS= 33 Ivl=1ms
> E: Ad=03(O) Atr=01(Isoc) MxPS= 33 Ivl=1ms
> I: If#= 1 Alt= 5 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
> E: Ad=83(I) Atr=01(Isoc) MxPS= 49 Ivl=1ms
> E: Ad=03(O) Atr=01(Isoc) MxPS= 49 Ivl=1ms
>
> This is all with isoc=1, as otherwise my syslog fills quicker than i am
> able to free space on my drive :-)
actually with isco=1 the SCO transfers are still on, but limited to
8-bit instead of 16-bit with isoc=2. So if you have isoc=2 it fills up
your syslog. Can you extract some of these SCO packets with hcidump for
me.
My problem is now that I can only fully blacklist the SCO support for
this dongle. I can't force the Bluetooth core into using 8-bit only.
Any chance of a name or identification of this dongle?
Regards
Marcel
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel
Hi,
On Tue, Jul 11, 2006 at 01:24:58PM +0200, Marcel Holtmann wrote:
> Hi Stefan,
> =
> > i have an el-cheapo USB BT dongle in front of me that throws an endless
> > stream of
> > kernel: hci_scodata_packet: hci1 SCO packet for unknown connection hand=
le 0
> > after inserting it into the USB port, unless i do
> > echo 1 > /sys/module/hci_usb/parameters/isoc
> > =
> > I don't know about the usual practice in such cases: do those devices g=
et
> > blacklisted in the drivers? If yes, what information should i provide to
> > get it into the blacklist?
> =
> what does "hciconfig -a" tells you about this dongle? The content
root@strolchi:~# hciconfig -a hci1
hci1: Type: USB
BD Address: 00:0C:78:31:11:0A ACL MTU: 339:4 SCO MTU: 60:9
UP RUNNING
RX bytes:419 acl:0 sco:0 events:19 errors:0
TX bytes:319 acl:0 sco:0 commands:17 errors:0
Features: 0xff 0xff 0x81 0x00 0x18 0x18 0x00 0x00
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: 'BlueZ strolchi (1)'
Class: 0x100100
Service Classes:
Device Class: Computer, Uncategorized
HCI Ver: 1.2 (0x2) HCI Rev: 0x222 LMP Ver: 1.2 (0x2) LMP Subver: 0x=
222
Manufacturer: RTX Telecom A/S (21)
> from /proc/bus/usb/devices for this device might also be helpful.
T: Bus=3D02 Lev=3D01 Prnt=3D01 Port=3D00 Cnt=3D01 Dev#=3D 3 Spd=3D12 MxC=
h=3D 0
D: Ver=3D 1.10 Cls=3De0(unk. ) Sub=3D01 Prot=3D01 MxPS=3D 8 #Cfgs=3D 1
P: Vendor=3D0400 ProdID=3D080a Rev=3D 1.00
C:* #Ifs=3D 2 Cfg#=3D 1 Atr=3D80 MxPwr=3D 0mA
I: If#=3D 0 Alt=3D 0 #EPs=3D 3 Cls=3De0(unk. ) Sub=3D01 Prot=3D01 Driver=
=3Dhci_usb
E: Ad=3D81(I) Atr=3D03(Int.) MxPS=3D 64 Ivl=3D1ms
E: Ad=3D82(I) Atr=3D02(Bulk) MxPS=3D 64 Ivl=3D0ms
E: Ad=3D02(O) Atr=3D02(Bulk) MxPS=3D 64 Ivl=3D0ms
I: If#=3D 1 Alt=3D 0 #EPs=3D 2 Cls=3De0(unk. ) Sub=3D01 Prot=3D01 Driver=
=3Dhci_usb
E: Ad=3D83(I) Atr=3D01(Isoc) MxPS=3D 0 Ivl=3D1ms
E: Ad=3D03(O) Atr=3D01(Isoc) MxPS=3D 0 Ivl=3D1ms
I: If#=3D 1 Alt=3D 1 #EPs=3D 2 Cls=3De0(unk. ) Sub=3D01 Prot=3D01 Driver=
=3Dhci_usb
E: Ad=3D83(I) Atr=3D01(Isoc) MxPS=3D 9 Ivl=3D1ms
E: Ad=3D03(O) Atr=3D01(Isoc) MxPS=3D 9 Ivl=3D1ms
I: If#=3D 1 Alt=3D 2 #EPs=3D 2 Cls=3De0(unk. ) Sub=3D01 Prot=3D01 Driver=
=3Dhci_usb
E: Ad=3D83(I) Atr=3D01(Isoc) MxPS=3D 17 Ivl=3D1ms
E: Ad=3D03(O) Atr=3D01(Isoc) MxPS=3D 17 Ivl=3D1ms
I: If#=3D 1 Alt=3D 3 #EPs=3D 2 Cls=3De0(unk. ) Sub=3D01 Prot=3D01 Driver=
=3Dhci_usb
E: Ad=3D83(I) Atr=3D01(Isoc) MxPS=3D 25 Ivl=3D1ms
E: Ad=3D03(O) Atr=3D01(Isoc) MxPS=3D 25 Ivl=3D1ms
I: If#=3D 1 Alt=3D 4 #EPs=3D 2 Cls=3De0(unk. ) Sub=3D01 Prot=3D01 Driver=
=3Dhci_usb
E: Ad=3D83(I) Atr=3D01(Isoc) MxPS=3D 33 Ivl=3D1ms
E: Ad=3D03(O) Atr=3D01(Isoc) MxPS=3D 33 Ivl=3D1ms
I: If#=3D 1 Alt=3D 5 #EPs=3D 2 Cls=3De0(unk. ) Sub=3D01 Prot=3D01 Driver=
=3Dhci_usb
E: Ad=3D83(I) Atr=3D01(Isoc) MxPS=3D 49 Ivl=3D1ms
E: Ad=3D03(O) Atr=3D01(Isoc) MxPS=3D 49 Ivl=3D1ms
This is all with isoc=3D1, as otherwise my syslog fills quicker than i am
able to free space on my drive :-)
Thanks,
Stefan
-- =
Stefan Seyfried \ "I didn't want to write for pay. I
QA / R&D Team Mobile Devices \ wanted to be paid for what I write."
SUSE LINUX Products GmbH, N=FCrnberg \ -- Leonard Cohen
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easi=
er
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat=3D1=
21642
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel
Hi Stefan,
> i have an el-cheapo USB BT dongle in front of me that throws an endless
> stream of
> kernel: hci_scodata_packet: hci1 SCO packet for unknown connection handle 0
> after inserting it into the USB port, unless i do
> echo 1 > /sys/module/hci_usb/parameters/isoc
>
> I don't know about the usual practice in such cases: do those devices get
> blacklisted in the drivers? If yes, what information should i provide to
> get it into the blacklist?
what does "hciconfig -a" tells you about this dongle? The content
from /proc/bus/usb/devices for this device might also be helpful.
Regards
Marcel
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel