linux-kernel - Re: [PATCH] ath3k: Add support for VAIO VPCEH [0489:e027]

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Thu, 1 Nov 2012 20:19:38 -0300
From:	Marcos Chaparro <marcos@...industries.com.ar>
To:	Gustavo Padovan <gustavo@...ovan.org>
Cc:	Marcel Holtmann <marcel@...tmann.org>,
	Johan Hedberg <johan.hedberg@...il.com>,
	linux-bluetooth@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ath3k: Add support for VAIO VPCEH [0489:e027]

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@...estreak:/home/marcos# lsusb
Bus 001 Device 004: ID 0cf3:3005 Atheros Communications, Inc. AR3011 Bluetooth

Best regards

--
Marcos
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/