All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Holler <holler@ahsoftware.de>
To: Bala Shanmugam <sbalashanmugam@atheros.com>
Cc: Marcel Holtmann <marcel@holtmann.org>,
	Shanmugamkamatchi Balashanmugam
	<Shanmugamkamatchi.Balashanmugam@Atheros.com>,
	"linux-bluetooth@vger.kernel.org"
	<linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCH] Bluetooth: Add new PID for Atheros 3011
Date: Fri, 26 Nov 2010 16:40:01 +0100	[thread overview]
Message-ID: <4CEFD4D1.1040706@ahsoftware.de> (raw)
In-Reply-To: <4CEFA3A4.7030806@atheros.com>

Hello,

Am 26.11.2010 13:10, schrieb Bala Shanmugam:
> Marcel Holtmann wrote:
>> Hi Bala,
>>
>>> Atheros 3011 has small sflash firmware and needs to be
>>> blacklisted in transport driver to load actual firmware
>>> in DFU driver.
>>
>> please add an empty line here. The signed-off line should always be
>> separated from the commit message. The git am takes it literal as it is
>> and does not modify it.
>>
>>> Signed-off-by: Bala Shanmugam <sbalashanmugam@atheros.com>
>>> ---
>>> drivers/bluetooth/ath3k.c | 2 ++
>>> drivers/bluetooth/btusb.c | 3 +++
>>> 2 files changed, 5 insertions(+), 0 deletions(-)
>>>
>>> diff --git a/drivers/bluetooth/ath3k.c b/drivers/bluetooth/ath3k.c
>>> index 128cae4..c70fb0b 100644
>>> --- a/drivers/bluetooth/ath3k.c
>>> +++ b/drivers/bluetooth/ath3k.c
>>> @@ -35,6 +35,8 @@
>>> static struct usb_device_id ath3k_table[] = {
>>> /* Atheros AR3011 */
>>> { USB_DEVICE(0x0CF3, 0x3000) },
>>
>> For the sake of readability add another empty line here as well.
>>
>>> + /* Atheros AR3011 with sflash firmware*/
>>> + { USB_DEVICE(0x0CF3, 0x3002) },

I don't understand this patch and starting bluetooth will fail here, 
when that patch is applied (to 2.6.36.1):

-----------
[  118.395793] usb 1-1.3: new full speed USB device using orion-ehci and 
address 4
[  118.506262] usb 1-1.3: New USB device found, idVendor=0cf3, 
idProduct=3000
[  118.506280] usb 1-1.3: New USB device strings: Mfr=0, Product=0, 
SerialNumber=0
[  118.654973] Bluetooth: Atheros AR30xx firmware driver ver 1.0
[  119.072139] usbcore: registered new interface driver ath3k
[  119.184499] usb 1-1.3: USB disconnect, address 4
[  120.695642] usb 1-1.3: new full speed USB device using orion-ehci and 
address 5
[  120.806394] usb 1-1.3: New USB device found, idVendor=0cf3, 
idProduct=3002
[  120.806410] usb 1-1.3: New USB device strings: Mfr=0, Product=0, 
SerialNumber=0
[  125.815007] ath3k_load_firmware: Can't change to loading 
configuration err
[  125.815096] ath3k: probe of 1-1.3:1.0 failed with error -5
-----------

As I've understood it, the pid 0x3002 will only come up, when the 
firmwire was already uploaded. So adding 0x3002 to ath3k seems to be wrong.

Regards,

Alexander

  reply	other threads:[~2010-11-26 15:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-26 10:13 [PATCH] Bluetooth: Add new PID for Atheros 3011 Bala Shanmugam
2010-11-26 11:22 ` Marcel Holtmann
2010-11-26 12:10   ` Bala Shanmugam
2010-11-26 15:40     ` Alexander Holler [this message]
2010-11-26 15:55       ` Alexander Holler
2010-11-29  6:09         ` Bala Shanmugam
2010-11-29 11:28           ` Alexander Holler
2010-11-30  5:59             ` Bala Shanmugam

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=4CEFD4D1.1040706@ahsoftware.de \
    --to=holler@ahsoftware.de \
    --cc=Shanmugamkamatchi.Balashanmugam@Atheros.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=sbalashanmugam@atheros.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.