On Sun, May 27, 2012 at 1:35 AM, Jonathan Nieder
<jrnieder@gmail.com> wrote:
Arief M Utama wrote:
> This is the output from lsusb:
>
> Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
> Bus 004 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
> Bus 001 Device 003: ID 0a5c:21e1 Broadcom Corp.
> Bus 004 Device 003: ID 0424:b832 Standard Microsystems Corp.
> Bus 004 Device 004: ID 064e:e258 Suyin Corp.
>
> More details from lsusb output on the bluetooth device attached.
Thanks.
> I can confirm that patch number 4
> [0004-Bluetooth-btusb-typo-in-Broadcom-SoftSailing-id.patch] is working on
> my laptop. Haven't tested other patches, although I can report that only
> patches 1, 4, 6 and 8 that applied successfully.
Ok. What kernel are you applying these to? Could you attach "dmesg"
output from the patched kernel?
The source package was called this: linux-2.6-3.2.18, the image is this: linux-image-3.2.0-2-amd64.
dmesg output attached here.
I was hoping to get a quick sanity check that the other patches at
least didn't cause the kernel to explode :), but answers to more
important questions about them would indeed require info from people
with the matching hardware. Will look around and then submit these
for inclusion in 3.2.y from kernel.org if they seem to be well tested.
I can test the other patches if needed, just to make sure about it :-)
Hope that helps,
Jonathan