From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Mohammed Shafi Shajakhan <mohammed@qca.qualcomm.com>
Cc: Julien Massot <jmassot@aldebaran-robotics.com>,
<linux-wireless@vger.kernel.org>, <ath6kl-devel@qca.qualcomm.com>
Subject: Re: ath6kl: AR6004 failed to start on computer boot
Date: Fri, 8 Mar 2013 12:28:36 +0200 [thread overview]
Message-ID: <87sj46mbhn.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <51262CB2.6070208@qca.qualcomm.com> (Mohammed Shafi Shajakhan's message of "Thu, 21 Feb 2013 19:48:26 +0530")
Mohammed Shafi Shajakhan <mohammed@qca.qualcomm.com> writes:
> Hi Julien,
>
> On 02/21/2013 07:33 PM, 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.
>>
>> [ 7.012514] usb 1-7: firmware: requesting ath6k/AR6004/hw1.3/bdata.bin
>> [ 7.035276] cfg80211: World regulatory domain updated:
>> [ 7.035287] cfg80211: (start_freq - end_freq @ bandwidth),
>> (max_antenna_gain, max_eirp)
>> [ 7.035299] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz),
>> (300 mBi, 2000 mBm)
>> [ 7.037916] usb 1-7: firmware: requesting ath6k/AR6004/hw1.3/fw-3.bin
>> [ 9.378940] ath6kl: f59afe4c
>> [ 9.379054] ath6kl: f59afe6c
>> [ 9.379391] ath6kl_usb: probe of 1-7:1.0 failed with error -5
>> Here I reset the device.
>
> that was the suggestion gave by Wei. The failure it seems
> check hostapp area to check target status and reset the device
> if needed.
>
> Great that you figured it out yourself!
The power of Open Source in action :)
But thanks a lot Julien, it was really great that you could solve it
yourself.
> We will send a proper patch for this.
I now sent a patch (plus few cleanups) to fix this.
--
Kalle Valo
next prev parent reply other threads:[~2013-03-08 10:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-10 14:39 ath6kl: AR6004 failed to start on computer boot Julien Massot
2012-12-13 17:46 ` Kalle Valo
2013-02-15 10:09 ` Kalle Valo
2013-02-15 14:10 ` Julien Massot
2013-02-15 14:22 ` Mohammed Shafi Shajakhan
2013-02-21 14:03 ` Julien Massot
2013-02-21 14:18 ` Mohammed Shafi Shajakhan
2013-03-08 10:28 ` Kalle Valo [this message]
2013-03-12 16:15 ` Mohammed Shafi Shajakhan
2013-02-21 17:06 ` Larry Finger
2013-02-22 15:06 ` Kalle Valo
2013-02-25 17:19 ` Yvan
2013-02-25 19:39 ` Larry Finger
[not found] ` <1448005898.305768.1361866657564.open-xchange@ox-webdesk.1and1.fr>
2013-02-26 14:09 ` Larry Finger
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=87sj46mbhn.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath6kl-devel@qca.qualcomm.com \
--cc=jmassot@aldebaran-robotics.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mohammed@qca.qualcomm.com \
/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).