From: Marcel Holtmann <marcel@holtmann.org>
To: Oliver Neukum <oneukum@suse.de>
Cc: bluez-devel@lists.sf.net, linux-usb-devel@lists.sourceforge.net,
maxk@qualcomm.com
Subject: Re: [Bluez-devel] [patch]quirky dongle for hci_usb
Date: Wed, 16 May 2007 14:08:59 +0200 [thread overview]
Message-ID: <1179317339.10069.73.camel@violet> (raw)
In-Reply-To: <200705161355.22934.oneukum@suse.de>
Hi Oliver,
> > > here's an additional device with the reset quirk.
> > >
> > > Regards
> > > Oliver
> > > Signed-off-by: Oliver Neukum <oneukum@suse.de>
> >
> > that patch doesn't apply since we already have this:
> >
> > /* Dell laptop with Broadcom chip */
> > { USB_DEVICE(0x413c, 0x8126), .driver_info = HCI_WRONG_SCO_MTU },
> >
> > Why do you think HCI_RESET is needed? Did Dell switched to using a HID
> > proxy dongle or what?
>
> A user reported that his dongle needs a reset to work. A manual reset, the
> module option and that patch solved the issue.
an manual reset is not possible. The HCI_RESET quirk only end up sending
HCI Reset as the first command. This actually only resets the Bluetooth
chip and nothing on the USB bus. Only in cases of Broadcom HID proxy it
triggers the HID to HCI switch.
I am simply not convinced that this is a HID proxy adapter and thus this
patch is not needed at all.
Regards
Marcel
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-05-16 12:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200705161345.58587.oneukum@suse.de>
2007-05-16 11:50 ` [Bluez-devel] [patch]quirky dongle for hci_usb Marcel Holtmann
[not found] ` <200705161355.22934.oneukum@suse.de>
2007-05-16 12:08 ` Marcel Holtmann [this message]
[not found] ` <200705161413.08514.oneukum@suse.de>
2007-05-16 12:22 ` 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=1179317339.10069.73.camel@violet \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sf.net \
--cc=bluez-devel@lists.sourceforge.net \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=maxk@qualcomm.com \
--cc=oneukum@suse.de \
/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).