Thanks, I will try it. The strange thing is the eSCO audio worked ok with Blackberry curve 8310, which seems to use the same CSR BlueCore4 chipset and firmware version 0xc5c. I assume the library of Blackberry is not Bluez. But when I use a PC with CSR BlueCore4 dongle with USB interface and Bluez library as the remote for testing, from the captured eSCO stream, I can not see any real data I sent, I got all zero. However If I changed the USB dongle to Broadcom chipset, I can see a few real data from captured eSCO stream (not all of data I sent, some seemed lost or being replaced by zero). -----Original Message----- From: Nick Pelly [mailto:npelly@xxxxxxxxxx] Sent: Monday, March 15, 2010 5:35 PM To: Cooper Xu Cc: linux-bluetooth@xxxxxxxxxxxxxxx Subject: Re: A strange compatible problem for eSCO audio with CSR USB Bluetooth dongle I wonder if this is some eSCO packet type incompatibility between chipsets. Try setting /sys/module/sco/parameters/disable_esco to 1 to see if this resolves the issue. Nick -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
