From: Marcos Chaparro <marcos@mrkindustries.com.ar>
To: Gustavo Padovan <gustavo@padovan.org>
Cc: Marcel Holtmann <marcel@holtmann.org>,
Johan Hedberg <johan.hedberg@gmail.com>,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ath3k: Add support for VAIO VPCEH [0489:e027]
Date: Thu, 1 Nov 2012 20:19:38 -0300 [thread overview]
Message-ID: <201211012019.38950.marcos@mrkindustries.com.ar> (raw)
In-Reply-To: <20121101225331.GB1915@joana>
On Thursday, November 01, 2012 19:53:31 Gustavo Padovan wrote:
> > # cat /sys/kernel/debug/usb/devices
> > T: Bus=01 Lev=02 Prnt=02 Port=04 Cnt=02 Dev#= 11 Spd=12 MxCh= 0
> > D: Ver= 1.10 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
> > P: Vendor=0cf3 ProdID=3005 Rev= 0.01
>
> I actually need the output without the patch in, showing the 0x0489 vendor
> id. Sorry, but we like to document the devices we add support properly.
I rebooted with an old (3.2.0-3-amd64) kernel and I still have the correct ID
0cf3:3005, I can't see the old usb ID.
I tried reloading all the bluetooth related modules but it still gets
identified as an 0cf3:3005.
Do you know how can I delete the device firmware to revert it to the original
state?
Apparently its keeping the firmware from my patched kernel.
root@bluestreak:/home/marcos# lsusb
Bus 001 Device 004: ID 0cf3:3005 Atheros Communications, Inc. AR3011 Bluetooth
Best regards
--
Marcos
next prev parent reply other threads:[~2012-11-01 23:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-29 13:09 [PATCH] Add bluetooth support for VAIO VPCEH [0489:e027] Marcos Chaparro
2012-10-31 18:25 ` Gustavo Padovan
2012-11-01 22:40 ` [PATCH] ath3k: Add " Marcos Chaparro
2012-11-01 22:53 ` Gustavo Padovan
2012-11-01 23:19 ` Marcos Chaparro [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-11-02 0:38 Marcos Chaparro
2012-11-06 11:02 ` Gustavo Padovan
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=201211012019.38950.marcos@mrkindustries.com.ar \
--to=marcos@mrkindustries.com.ar \
--cc=gustavo@padovan.org \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.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).