Larry Finger <Larry.Finger@xxxxxxxxxxxx> writes:
> On 02/21/2013 08:03 AM, Julien Massot wrote:
>> Hi,
>> I just find a quick and dirty patch to workaround this issue.
>> I just reset the device on initialization failure.
>>
>> I hope this helps to understand the real issue.
>>
[...]
> I am certain that the real problem here is that ath6kl is requesting
> firmware with a synchronous call using request_firmware() rather than
> with the asynchronous request_firmware_nowait(). That used to work,
> but updates to udev caused the firmware read operation to time out. It
> works after a reset because the file reading routines are now running;
> however, the correct fix is to rewrite the firmware reading section.
I haven't looked at all the details yet, but AFAIK this is about cold vs
warm booting the chip. When rebooting the host while maintaining the
power to ar6004 ("warm boot") ath6kl probe fails as the chip is in odd
state and needs to be reset. It's not about dowloading the firmware
image from user space, it's about starting the firmware inside the chip.
And besides, didn't udev finally fix that (after some "feedback" from
Linus) so that we don't need to change all the drivers?
--
Kalle Valo
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
