public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Tim Gardner <tim.gardner@canonical.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
	Mario Limonciello <mario_limonciello@dell.com>
Subject: Re: Dell Wireless 365 requires reset quirk
Date: Sun, 30 Nov 2008 11:33:39 +0100	[thread overview]
Message-ID: <1228041219.9176.10.camel@violet.holtmann.net> (raw)
In-Reply-To: <491CCD86.7050904@canonical.com>

Hi Tim,

> >> >From 931ccb629d739aa563347a4e866bc26107e6b545 Mon Sep 17 00:00:00 2001
> >> From: Tim Gardner <tim.gardner@canonical.com>
> >> Date: Tue, 4 Nov 2008 09:18:06 -0700
> >> Subject: [PATCH] Dell Wireless 365 needs BTUSB_RESET quirk.
> >>  OriginalAuthor: Mario Limonciello <mario_limonciello@dell.com>
> >>
> >> Signed-off-by: Tim Gardner <tim.gardner@canonical.com>
> >> Cc: stable@kernel.org
> >> ---
> >>  drivers/bluetooth/btusb.c |    3 +++
> >>  1 files changed, 3 insertions(+), 0 deletions(-)
> >>
> >> diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
> >> index af472e0..051b758 100644
> >> --- a/drivers/bluetooth/btusb.c
> >> +++ b/drivers/bluetooth/btusb.c
> >> @@ -125,6 +125,9 @@ static struct usb_device_id blacklist_table[] = {
> >>  	/* Dell laptop with Broadcom chip */
> >>  	{ USB_DEVICE(0x413c, 0x8126), .driver_info = BTUSB_RESET | BTUSB_WRONG_SCO_MTU },
> >>  
> >> +	/* Dell Wireless 365 */
> >> +	{ USB_DEVICE(0x413c, 0x8160), .driver_info = BTUSB_RESET },
> >> +
> >>  	/* Dell Wireless 370 */
> >>  	{ USB_DEVICE(0x413c, 0x8156), .driver_info = BTUSB_RESET | BTUSB_WRONG_SCO_MTU },
> >>  
> > 
> > I shall assume that this patch was authored by Mario.  This should have
> > been communicated by adding his From: line right at the top of the
> > changelog.  Mario's signed-off-by: is absent, but that is tolerable
> > because we have yours.
> > 
> > The (absent) changelog fails to explain what effect this patch has. 
> > _why_ does this driver need this quirk?
> > 
> > As it stands, there is insufficient information here for making
> > 2.6.28-vs-2.6.29 decisions, let alone 2.6.27.x, 2.6.26.x, etc.
> > 
> 
> Is this better (aside from being an attachment) ?

the patch will no longer be needed. I am making HCI Reset the default
and only letting the old drivers quirk a NO_RESET.

Regards

Marcel



      reply	other threads:[~2008-11-30 10:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-04 16:24 Dell Wireless 365 requires reset quirk Tim Gardner
2008-11-11 22:57 ` Andrew Morton
2008-11-11 23:41   ` Mario Limonciello
2008-11-14  0:59   ` Tim Gardner
2008-11-30 10:33     ` Marcel Holtmann [this message]

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=1228041219.9176.10.camel@violet.holtmann.net \
    --to=marcel@holtmann.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mario_limonciello@dell.com \
    --cc=tim.gardner@canonical.com \
    /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