[Bluez-devel] Plugz with Dell inbuilt-BT

Jon Barnett

author

2007-02-05 18:27 UTC #0 lore raw

I've tested the latest plugz from CVS with kernel 2.6.19.2 patched with 2.6.19-mh2 and the bluez-3.9 release. Things seem to be working fine now in terms of being able to send sound to my Sony Ericcson headset.

Bus 2 Device 4: ID 413c:8126 Dell Computer Corp.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 224 Wireless
bDeviceSubClass 1 Radio Frequency
bDeviceProtocol 1 Bluetooth
bMaxPacketSize0 64
idVendor 0x413c Dell Computer Corp.
idProduct 0x8126
bcdDevice 1.00

  iManufacturer           1 Broadcom Corp
  iProduct                2 BCM2045
  iSerial                 0 
  bNumConfigurations      1

Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 216
bNumInterfaces 4
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0010 1x 16 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0000 1x 0 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0000 1x 0 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 1
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0009 1x 9 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0009 1x 9 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 2
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0011 1x 17 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0011 1x 17 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 3
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0020 1x 32 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0020 1x 32 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 4
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 5
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 2
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84 EP 4 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0020 1x 32 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x04 EP 4 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0020 1x 32 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 3
bAlternateSetting 0
bNumEndpoints 0
bInterfaceClass 254 Application Specific Interface
bInterfaceSubClass 1 Device Firmware Update
bInterfaceProtocol 0
iInterface 0
Device Status: 0x0000
(Bus Powered)

hci0: Type: USB

        BD Address: 00:16:CF:CE:C2:75 ACL MTU: 1017:8 SCO MTU: 64:8
        UP RUNNING 
        RX bytes:356 acl:0 sco:0 events:11 errors:0
        TX bytes:39 acl:0 sco:0 commands:11 errors:0
        Features: 0xff 0xff 0x8d 0xfe 0x9b 0xfd 0x00 0x80
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
        Link policy: 
        Link mode: SLAVE ACCEPT 
        Name: 'BCM2045'
        Class: 0x000000
        Service Classes: Unspecified
        Device Class: Miscellaneous, 
        HCI Ver: 2.0 (0x3) HCI Rev: 0x20da LMP Ver: 2.0 (0x3) LMP

Subver: 0x4182
Manufacturer: Broadcom Corporation (15)

The only problem is that skype can't use the plugz device as it doesn't recognize it - since it doesn't do detection of available pcm devices. btsco in CVS doesn't build into a loadable module in so far as the module causes a segmentation fault on my SMP 2.6.19.2 kernel. I'm using the alsa-1.0.14rc2 releases. I think someone has already asked about a solution to get skype working with the new plugz service.

As 2.6.20 has been released, I may next try upgrading to this kernel and patching in the bluez and plugz software.

Cheers,

JonB.

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

Mark Hellman

2007-02-06 13:06 UTC #1 lore raw

Quoted 4 lines · Jon Barnett

The only problem is that skype can't use the plugz device as it doesn't recognize it - since it doesn't do detection of available pcm devices.
Quoted 1 line
From a user's perspective that is, in my opinion, the main problem with

using plugz instead of btsco. Skype and Ekiga are the reasons why 90% of users want to install plugz.

Is this an ALSA limitation, or isn't Skype using the right functions from the ALSA's API to enumerate all available devices? Who must be fixes: Skype of ALSA?
Could some developer enlighten us on this issue?

Thanks,
Mark

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

Fabien Chevalier

2007-02-08 14:42 UTC #2 lore raw

Hi,

Quoted 5 lines · Mark Hellman

Quoted 2 lines · Jon Barnett
The only problem is that skype can't use the plugz device as it doesn't recognize it - since it doesn't do detection of available pcm devices.

Quoted 7 lines

Quoted 1 line
Quoted 1 line
From a user's perspective that is, in my opinion, the main problem with
using plugz instead of btsco. Skype and Ekiga are the reasons why 90% of users want to install plugz.
Is this an ALSA limitation, or isn't Skype using the right functions from the ALSA's API to enumerate all available devices? Who must be fixes: Skype of ALSA?

Thing is : sadly, there is no ALSA function to enumerate available PCMs on the system. There are only features to enumerate hardware cards. That's a known ALSA weakness, but this is how things are as of to today in Linux world :-(

Quoted 1 line

Could some developer enlighten us on this issue?

Just use Skype in OSS mode, and use skype_bt_hijacker available in contrib directory to redirect sound to ALSA headset. I haven't tested it myself recently, but theorically this should work.

Cheers,

Fabien

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

Jon Barnett

author

2007-02-08 16:54 UTC #3 lore raw

The problem with the bt-hijacker approach is that it is based on the snd-bt-sco module which creates the necessary /dev/dspX entry for re-routing sound. The plugz approach doesn't result in the creation of a /dev/dspX. So the hijacker can't reroute the sound as far as I can see. Or am I missing something?

Cheers,

JonB

Quoted 23 lines · Fabien Chevalier

Hi,
Quoted 5 lines · Mark Hellman
Quoted 2 lines · Jon Barnett
The only problem is that skype can't use the plugz device as it doesn't recognize it - since it doesn't do detection of available pcm devices.
Quoted 7 lines
Quoted 1 line
From a user's perspective that is, in my opinion, the main problem with
using plugz instead of btsco. Skype and Ekiga are the reasons why 90% of users want to install plugz.
Is this an ALSA limitation, or isn't Skype using the right functions from the ALSA's API to enumerate all available devices? Who must be fixes: Skype of ALSA?
Thing is : sadly, there is no ALSA function to enumerate available PCMs on the system. There are only features to enumerate hardware cards. That's a known ALSA weakness, but this is how things are as of to today in Linux world :-(
Quoted 1 line
Could some developer enlighten us on this issue?

Quoted 10 lines

Just use Skype in OSS mode, and use skype_bt_hijacker available in contrib directory to redirect sound to ALSA headset. I haven't tested it myself recently, but theorically this should work.
Cheers,
Fabien

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

Mark Hellman

2007-02-06 13:11 UTC #4 lore raw

In reply to Jon Barnett

Quoted 4 lines · Jon Barnett

The only problem is that skype can't use the plugz device as it doesn't recognize it =A0- since it doesn't do detection of available pcm devices.
Quoted 1 line
From a user's perspective that is, in my opinion, the main problem with =

using plugz instead of btsco. Skype and Ekiga are the reasons why 90% of users want to install plugz.

Is this an ALSA limitation, or isn't Skype making use the right functions from the ALSA's API to enumerate all available devices? =

Which must be fixed: Skype of ALSA? =

Could some developer enlighten us on this issue?

Thanks,
Mark

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