netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: "David S. Miller" <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: Bluetooth update for 2.6
Date: Tue, 18 Jul 2006 19:08:44 +0200	[thread overview]
Message-ID: <1153242524.21024.14.camel@localhost> (raw)
In-Reply-To: <1152887911.25660.32.camel@localhost>

Hi Dave,

> here are two more bug fixes for the Bluetooth subsystem. Both are
> workarounds for either broken implementations or broken hardware.

we've seen a bunch of buggy USB Bluetooth devices lately and I have
three more patches to workaround various issues. I also re-based the
tree to 2.6.18-rc2 and pushed the additional changes. Please pull and
forward to Linus as soon as possible.

Regards

Marcel


Please pull from

        git://git.kernel.org/pub/scm/linux/kernel/git/holtmann/bluetooth-2.6.git

This will update the following files:

 drivers/bluetooth/hci_usb.c |    8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

through these ChangeSets:

Marcel Holtmann <marcel@holtmann.org> Tue, 18 Jul 2006 18:32:33 +0200 

    [Bluetooth] Enable SCO support for Broadcom HID proxy dongle
    
    The Broadcom dongles with HID proxy support actually support SCO over
    HCI if the SCO buffer size values are corrected. So instead of disabling
    the SCO support, mark this dongle with the quirk for the Bluetooth core
    to correct the wrong buffer size values.
    
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>

Marcel Holtmann <marcel@holtmann.org> Tue, 18 Jul 2006 18:04:59 +0200 

    [Bluetooth] Add quirk for another broken RTX Telecom based dongle
    
    This patch disables the ISOC transfers for another broken RTX Telecom
    based USB dongle. Starting the USB ISOC transfers only ends in a burst
    of error messages for invalid SCO packets on connection handle 0.
    
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>

Marcel Holtmann <marcel@holtmann.org> Tue, 18 Jul 2006 17:47:40 +0200 

    [Bluetooth] Correct SCO buffer size for Belkin devices
    
    The Belkin F8T012 and F8T013 devices are both based on a Bluetooth chip
    from Broadcom and their SCO buffer size values are wrong. The Bluetooth
    core should correct these values.
    
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>




  reply	other threads:[~2006-07-18 17:08 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-14 14:38 Bluetooth update for 2.6 Marcel Holtmann
2006-07-18 17:08 ` Marcel Holtmann [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-11-19  0:34 Marcel Holtmann
2006-11-21  0:14 ` David Miller
2006-10-20  7:49 Marcel Holtmann
2006-10-20  8:16 ` David Miller
2006-10-15 16:10 Marcel Holtmann
2006-10-16  6:13 ` David Miller
2006-09-21 19:47 Marcel Holtmann
2006-09-26 10:46 ` Marcel Holtmann
2006-09-28  5:58   ` David Miller
2006-09-28 21:14     ` Marcel Holtmann
2006-09-28 22:30       ` David Miller
2006-07-12 21:49 Marcel Holtmann
2006-07-12 22:34 ` David Miller
2006-07-06 20:09 Marcel Holtmann
2006-07-07  7:17 ` David Miller
2006-07-07 22:54   ` Marcel Holtmann
2006-07-07 23:14     ` David Miller

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=1153242524.21024.14.camel@localhost \
    --to=marcel@holtmann.org \
    --cc=davem@davemloft.net \
    --cc=netdev@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).