linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Schmitt <tcwardrobe@gmail.com>
To: linux-bluetooth@vger.kernel.org
Cc: marcel@holtmann.org, padovan@profusion.mobi
Subject: Re: 057c:3800 BlueFRITZ! Bluetooth Stick broken since 2.6.something
Date: Sun, 20 Nov 2011 16:27:59 +0100	[thread overview]
Message-ID: <4EC91C7F.9070500@gmail.com> (raw)
In-Reply-To: <20111118203019.GA24250@x220.ger.corp.intel.com>

Am 18.11.2011 21:30, schrieb Johan Hedberg:
> HI Michael,
>
> On Fri, Nov 18, 2011, Michael Schmitt wrote:
>> Thanks for the input. But do you know why the device works with
>> older kernel / userland?>
> Probably because the list of supported commands wasn't previously
> requested as part of the adapter init sequence, or because the kernel
> code didn't actually wait for all commands to complete before notifying
> success to user space (I know the latter is at least true since I
> submitted a patch for it).

So that means, if the bt-stack in the kernel would ignore the successful 
completion of those "what protocol version do you understand"-commands 
all bt-related stuff with the stick would work nevertheless?

>> So, and what do we do from here on?
> Well, the attached patch will at least make sure that the failure of
> this command is correctly detected so you get an immediate error instead
> of a timeout. The next step is to decide whether to do a quirk for your
> specific adapter or to make it a general rule that errors for this
> particular HCI command are ignored (for that we'd need feedback from the
> real kernel experts like Marcel and Gustavo).

But apparently none of them had the urge to actually respond in this 
ml-thread yet. :) Let's see, I try to poke them "mildly" in cc'ing them...

General speaking, the bt-stick in question is old (at least 5 years or 
so) and I have another (working) stick here, so there is no immediate 
adversity for me. But I guess as this stick is from major bt-accessoirs 
supplier from germany (AVM GmbH Berlin) this hardware may be around for 
many users for a fairly long time. But then again... it seems to be a 
hardware-bug...

Anyway, I guess it would ne nice to have it "fixed" someday. :)

Greetings
Michael

  reply	other threads:[~2011-11-20 15:27 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-18 15:28 057c:3800 BlueFRITZ! Bluetooth Stick broken since 2.6.something 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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2013-07-18 13:26 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
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

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=4EC91C7F.9070500@gmail.com \
    --to=tcwardrobe@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=padovan@profusion.mobi \
    /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).