From: Andrey Batyiev <batyiev@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: Yet another counterfeit CSR device?
Date: Mon, 29 Jul 2019 06:20:18 +0300 [thread overview]
Message-ID: <CAEQQxWySUJZBa9CF7-W_4zXcuitgaNuu2f_pYswLKDUtVwWd1g@mail.gmail.com> (raw)
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
next reply other threads:[~2019-07-29 3:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-29 3:20 Andrey Batyiev [this message]
2019-07-30 9:39 ` Yet another counterfeit CSR device? Marcel Holtmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAEQQxWySUJZBa9CF7-W_4zXcuitgaNuu2f_pYswLKDUtVwWd1g@mail.gmail.com \
--to=batyiev@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).