Jonathan Nieder wrote:
> I just noticed the following change upstream:
[...]
> Bluetooth: ath3k: output firmware filename when request_firmware
> failed
[...]
> which gives me hope that upstream is looking at this kind of thing
> (that patch was merged in v3.3-rc1). This suggests two p
Andres Cimmarusti wrote:
> I tested two kernels on Squeeze:
>
> - 3.1.8 from squeeze-backports, which was compiled using gcc 4.4.5 (as
> my own compiled 3.0.x and 3.1.x kernels)
>
> - 3.1.8 from wheezy, compiled using gcc 4.6.2
>
> Both kernels loaded the firmware correctly without any problems. T
Andres Cimmarusti wrote:
> One of the differences between Wheezy and Squeeze in terms of, say the
> 3.1.x, kernel is that in Squeeze I compile it with gcc 4.4.5, but in
> wheezy this is done with gcc 4.6.x. Could there be a problem here?
Ah, you have been compiling the kernel from source?
Yes, t
There's only silence in the linux-kernel and linux-bluetooth mailing lists...
At this point there is only one thing I haven't tried because I can't
at the moment.
One of the differences between Wheezy and Squeeze in terms of, say the
3.1.x, kernel is that in Squeeze I compile it with gcc 4.4.5, b
Hi there
> Yes, no ideas here, either. Please contact
> linux-blueto...@vger.kernel.org, cc-ing linux-ker...@vger.kernel.org
> and either me or this bug log so we can track it.
I've spotted something odd that may give us some light as to why it's
not working and I wanted to discuss it here befor
Andres Cimmarusti wrote:
> No luck there either. I downgraded to usb-modeswitch from squeeze and
> I got the exact same error when loading the atheros firmware. At the
> same time I was able to test the newest udev version 175.
Thanks.
> I don't know what else to try!
Yes, no ideas here, either
Andres Cimmarusti wrote:
> I was able to try wheezy with a downgraded udev to version 164 from
> squeeze, but using Sid's kernel 3.1.4. Sadly, I get the same problem!
> (this is rather upsetting, since I'm using the same combination on
> squeeze and I get no problems).
Maybe playing with usb-mode
Hi Jonathan,
> I'd like to narrow down the difference even more. So, here are some
> ideas:
>
> 1. Can you reproduce this with a squeeze kernel? (I'm guessing it
> lacks support since it doesn't include commit
> v2.6.33-rc7~20^2~3^2~1, "Bluetooth: Add DFU driver for Atheros
> Bluetooth
Hi Andres,
Andres Cimmarusti wrote:
> Here they go. Let me know if I need to send other logs, but this one
> clearly shows the error loading the firmware while using testing and
> no error at all using stable and basically the same kernel version and
> firmware.
Yep, weird.
I'd like to narrow d
9 matches
Mail list logo