From: Sven Schnelle <svens@stackframe.org>
To: ath10k@lists.infradead.org
Subject: Re: compat-wireless-2014-05-22 breaks ath10k in an Archer C7 v2
Date: Thu, 05 Jun 2014 13:15:00 +0200 [thread overview]
Message-ID: <53905134.8010303@stackframe.org> (raw)
In-Reply-To: <CA+BoTQmUyvTr+ga81EacbMkE4UVtMBP2PfBs_vH-PF4OvHuZQg@mail.gmail.com>
On 05/29/2014 09:48 AM, Michal Kazior wrote:
> +ath10k@lists.infradead.org
>
> On 28 May 2014 20:35, Andy Lutomirski <luto@amacapital.net> wrote:
>> It dies with 'otp calibration failed: 2'.
>>
>> Some older version of the driver seemed to work fine.
> ath10k did not verify otp result before so it could load successfully
> despite errors.
>
> Someone raised this problem yesterday on IRC. I'm not really sure how
> we should deal with this properly.
>
>
> http://lists.infradead.org/mailman/listinfo/ath10k
I see the following output on the firmware console:
otp main...
Table initialized..
streamCnt 0
Golden Bin/fake Board Template used ...
otp done...
assertion failed? pc=0x948f19, line=5555, dump area=0x40ad04
Target ID: 0x4100016c (1090519404)
Debug Info:
0x4100016c 0x000015b3 0x00948f19 0x00955b31
0x00948f19 0x00060530 0x00000004 0x00000000
0x00000000 0x004045f0 0x00404610 0x00955a00
0x0000
However, the AP where OTP now fails is an engineering sample,
and probably doesn't contain any valid calibration. It did work
in the past, but with the latest ath10k the driver doesn't load
because of OTP failing. So maybe that output is helpful here.
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2014-06-05 11:12 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-28 18:35 compat-wireless-2014-05-22 breaks ath10k in an Archer C7 v2 Andy Lutomirski
2014-05-29 7:48 ` Michal Kazior
2014-05-29 7:48 ` Michal Kazior
2014-05-29 17:52 ` Andy Lutomirski
2014-05-29 17:52 ` Andy Lutomirski
2014-06-05 10:26 ` Kalle Valo
2014-06-05 10:26 ` Kalle Valo
2014-06-05 16:04 ` Andy Lutomirski
2014-06-05 16:04 ` Andy Lutomirski
2014-06-05 16:08 ` Ben Greear
2014-06-05 16:08 ` Ben Greear
2014-06-05 16:23 ` Andy Lutomirski
2014-06-05 16:23 ` Andy Lutomirski
2014-06-06 6:39 ` Kalle Valo
2014-06-06 6:39 ` Kalle Valo
2014-06-06 16:05 ` Ben Greear
2014-06-06 16:05 ` Ben Greear
2014-06-06 8:59 ` Matti Laakso
2014-06-06 9:09 ` Kalle Valo
2014-06-06 23:31 ` Kamal Koshy
2014-06-07 5:36 ` Kalle Valo
2014-06-07 6:11 ` Sven Schnelle
2014-06-08 11:52 ` Matti Laakso
2014-06-09 8:28 ` Kalle Valo
2014-06-09 14:39 ` Kamal Koshy
2014-06-09 5:07 ` Michal Kazior
2014-06-09 20:01 ` Sven Schnelle
2014-06-05 11:15 ` Sven Schnelle [this message]
2014-06-05 11:36 ` Kalle Valo
2014-06-05 11:49 ` Sven Schnelle
2014-06-05 12:20 ` Michal Kazior
2014-06-07 20:37 ` Sven Schnelle
2014-06-07 20:41 ` Sven Schnelle
2014-06-08 5:59 ` Kamal Koshy
2014-06-09 5:40 ` Michal Kazior
2014-06-12 12:57 ` Michal Kazior
2014-06-12 19:37 ` Sven Schnelle
2014-06-13 11:12 ` Michal Kazior
2014-06-14 16:51 ` Kalle Valo
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=53905134.8010303@stackframe.org \
--to=svens@stackframe.org \
--cc=ath10k@lists.infradead.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.