Linux-Bluetooth Archive on lore.kernel.org
 help / color / Atom feed
* Yet another counterfeit CSR device?
@ 2019-07-29  3:20 Andrey Batyiev
  2019-07-30  9:39 ` Marcel Holtmann
  0 siblings, 1 reply; 2+ messages in thread
From: Andrey Batyiev @ 2019-07-29  3:20 UTC (permalink / raw)
  To: linux-bluetooth

Hello everyone,

I have nontdescript usb bluetooth dongle with "V5.0" marking on it.
It claims to be CSR (0a12:0001) bluetooth dongle, but it has
nonfunctional "delete stored link key" command, so I think it is
counterfeit.

Futhermore, Linux kernel doesn't detect it as counterfeit
(in`btusb_setup_csr`), because the dongle reports following:

- From USB enumeration:
bcdDevice = 0x8891

- From Read Local Version HCI command:
Manufacturer = 0x000a (CSR)
HCI ver. = 4.0
HCI rev. = 2064
LMP ver. = 4.0
LMP subver. = 4114

So, Linux kernel fails to power up this dongle. Ok, so I've hacked
`btusb_setup_csr` routine to include this device too (it powers up
now), however GATT communication doesn't work (btmon should nothing =
no ATT exchanges except MTU setup).

Any ideas on what should I check to make this device work?

Thanks,
    Andrey

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Yet another counterfeit CSR device?
  2019-07-29  3:20 Yet another counterfeit CSR device? Andrey Batyiev
@ 2019-07-30  9:39 ` Marcel Holtmann
  0 siblings, 0 replies; 2+ messages in thread
From: Marcel Holtmann @ 2019-07-30  9:39 UTC (permalink / raw)
  To: Andrey Batyiev; +Cc: linux-bluetooth

Hi Andrey,

> I have nontdescript usb bluetooth dongle with "V5.0" marking on it.
> It claims to be CSR (0a12:0001) bluetooth dongle, but it has
> nonfunctional "delete stored link key" command, so I think it is
> counterfeit.
> 
> Futhermore, Linux kernel doesn't detect it as counterfeit
> (in`btusb_setup_csr`), because the dongle reports following:
> 
> - From USB enumeration:
> bcdDevice = 0x8891
> 
> - From Read Local Version HCI command:
> Manufacturer = 0x000a (CSR)
> HCI ver. = 4.0
> HCI rev. = 2064
> LMP ver. = 4.0
> LMP subver. = 4114
> 
> So, Linux kernel fails to power up this dongle. Ok, so I've hacked
> `btusb_setup_csr` routine to include this device too (it powers up
> now), however GATT communication doesn't work (btmon should nothing =
> no ATT exchanges except MTU setup).
> 
> Any ideas on what should I check to make this device work?

please post a btmon -w trace.log from the init procedure. You might need to blacklist btusb.ko module and then manually load it to capture the whole sequence with btmon.

Regards

Marcel


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, back to index

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-07-29  3:20 Yet another counterfeit CSR device? Andrey Batyiev
2019-07-30  9:39 ` Marcel Holtmann

Linux-Bluetooth Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-bluetooth/0 linux-bluetooth/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-bluetooth linux-bluetooth/ https://lore.kernel.org/linux-bluetooth \
		linux-bluetooth@vger.kernel.org linux-bluetooth@archiver.kernel.org
	public-inbox-index linux-bluetooth


Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-bluetooth


AGPL code for this site: git clone https://public-inbox.org/ public-inbox