From: "Jörg Esser" <jackfritt@boh.de>
To: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: 057c:3800 BlueFRITZ! Bluetooth Stick broken since 2.6.something
Date: Mon, 22 Jul 2013 09:10:59 +0200 [thread overview]
Message-ID: <51ECDB03.8090109@boh.de> (raw)
In-Reply-To: <20130719162051.GA7373@x220.p-661hnu-f1>
Johan Hedberg schrieb:
> Hi Marcel,
>
> On Fri, Jul 19, 2013, Marcel Holtmann wrote:
>>>> HCI Event: Command Complete (0x0e) plen 12 [hci0] 0.043811
>>> Read Local Version Information (0x04|0x0001) ncmd 1
>>> Status: Success (0x00)
>>> HCI version: 2 - 0x2006
>>> LMP version: 2 - 0x1806
>>> Manufacturer: AVM Berlin (31)
>> it declares itself here as Bluetooth 1.2 device. Which means it is the
>> second generation of BlueFritz! USB device.
>>
>> <snip>
>>
>>> < HCI Command: Read Local Supported Comm.. (0x04|0x0002) plen 0 [hci0] 0.210014
>>>> HCI Event: Command Status (0x0f) plen 4 [hci0] 0.217361
>>> Read Local Supported Commands (0x04|0x0002) ncmd 1
>>> Status: Unknown HCI Command (0x01)
>> And here is your failing command. Newer kernels have been strict with
>> failing commands and will just abort the setup if anything goes wrong.
>>
>> Johan, we need to figure out on how to work around this one. Might
>> just match for the manufacturer before sending the command.
> Either that or a quirk based on the USB id. Wouldn't matching just the
> manufacturer be a bit problematic for any newer chips from this company,
> or they stopped doing Bluetooth dongles after this one?
They stopped doing Bluetooth dongles after this one. I found no more
Product with bluetooth on their website.
The support from AVM endet on 01.12.2009.
As I read here http://www.wehavemorefun.de/fritzbox/BlueFRITZ!_USB
Should I open my trashbin?
--
Gruss, Joerg
next prev parent reply other threads:[~2013-07-22 7:10 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-18 13:26 057c:3800 BlueFRITZ! Bluetooth Stick broken since 2.6.something Jörg Esser
2013-07-18 14:13 ` Marcel Holtmann
2013-07-19 6:26 ` Jörg Esser
2013-07-19 13:49 ` Marcel Holtmann
2013-07-19 16:20 ` Johan Hedberg
2013-07-22 7:10 ` Jörg Esser [this message]
2013-07-22 14:22 ` Marcel Holtmann
2013-07-23 23:39 ` Johan Hedberg
2013-07-25 9:10 ` Jörg Esser
2013-07-25 10:55 ` Gustavo Padovan
2013-07-25 14:51 ` Marcel Holtmann
2013-07-25 14:40 ` Marcel Holtmann
-- strict thread matches above, loose matches on Subject: below --
2011-11-18 15:28 Michael Schmitt
2011-11-18 15:36 ` Johan Hedberg
2011-11-18 15:49 ` Michael Schmitt
2011-11-18 16:21 ` Johan Hedberg
2011-11-18 16:34 ` Michael Schmitt
2011-11-18 20:30 ` Johan Hedberg
2011-11-20 15:27 ` Michael Schmitt
2011-11-27 10:04 ` Michael Schmitt
2011-11-28 8:42 ` Andrei Emeltchenko
2011-11-21 8:57 ` Andrei Emeltchenko
2011-11-21 9:12 ` Andrei Emeltchenko
2011-11-21 9:13 ` Marcel Holtmann
2011-11-21 10:22 ` Andrei Emeltchenko
2011-11-21 13:03 ` Marcel Holtmann
2011-11-21 10:35 ` Johan Hedberg
2011-11-21 13:04 ` Marcel Holtmann
2011-11-21 15:21 ` Johan Hedberg
2011-11-18 16:17 ` Michael Schmitt
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=51ECDB03.8090109@boh.de \
--to=jackfritt@boh.de \
--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).