From: Mohammed Shafi Shajakhan <mohammed@qca.qualcomm.com>
To: Julien Massot <jmassot@aldebaran-robotics.com>
Cc: Kalle Valo <kvalo@qca.qualcomm.com>,
<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 19:52:48 +0530 [thread overview]
Message-ID: <511E44B8.3000308@qca.qualcomm.com> (raw)
In-Reply-To: <CADGp=Qf=j+kWA4EM1Z-xyKkuutW64Fi0vfUNqm1tPM1+4WEKyQ@mail.gmail.com>
Hi,
On 02/15/2013 07:40 PM, Julien Massot wrote:
> Hi Kalle
>
>> IIRC you mentioned on IRC that you don't see this anymore, is that
>> correct?
>
> I still have the problem on a reboot, but the device initialize itself
> properly after a normal boot.
>
> It's still a problem for me, I obtain exactly the same log.
> ath6kl: Failed to start hardware: -5
> Dec 13 01:43:21 x201 kernel: [ 24.843781] ath6kl: Failed to init
> ath6kl core: -5
> Dec 13 01:43:21 x201 kernel: [ 24.843849] ath6kl_usb: probe of
> 2-1.2:1.0 failed with error -5
In x86 I remember this issue can be seen, I will try to take
a look at this by finding some time :)
>
> If you need to test anything don't hesitate to request me.
>
>
--
thanks,
shafi
next prev parent reply other threads:[~2013-02-15 14:22 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 [this message]
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=511E44B8.3000308@qca.qualcomm.com \
--to=mohammed@qca.qualcomm.com \
--cc=ath6kl-devel@qca.qualcomm.com \
--cc=jmassot@aldebaran-robotics.com \
--cc=kvalo@qca.qualcomm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.