From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Julien Massot <jmassot@aldebaran-robotics.com>
Cc: <linux-wireless@vger.kernel.org>, <ath6kl-devel@qca.qualcomm.com>
Subject: Re: ath6kl: AR6004 failed to start on computer boot
Date: Fri, 15 Feb 2013 12:09:33 +0200 [thread overview]
Message-ID: <87ehghanxe.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CADGp=QfF1bBgqP_X9=+PXfH0xCgPFn=h2VG19uV8_cJ8xzg8gg@mail.gmail.com> (Julien Massot's message of "Mon, 10 Dec 2012 15:39:09 +0100")
Hi Julien,
sorry for taking so long to get back to you.
Julien Massot <jmassot@aldebaran-robotics.com> writes:
> I have some problem with the AR6004 (hw 1.3) initialisation.
> I'm using the compat wireless 3.6.6-1 package, with the ath6kl driver from
> https://github.com/kvalo/ath6kl.git. (master branch)
>
> The device seems not to respond after the firmware upload.
> "ath6kl: htc_wait_recv_ctrl_message: Timeout!"
> Increasing the timeout doesn't help.
> Here is the log at startup.
> http://pastebin.com/DsivqdDP
>
> If I unplug and re-plug the adapter, every thing is going well.
> http://pastebin.com/BTz0w5QL.
>
> Any Idea on how to fix or workaround this issue ?
>
> (I've also tried the recovery options recovery_enable=1 heart_beat_poll=200)
IIRC you mentioned on IRC that you don't see this anymore, is that
correct?
--
Kalle Valo
next prev parent reply other threads:[~2013-02-15 10:09 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 [this message]
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
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=87ehghanxe.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 \
/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).