From: Michal Kazior <michal.kazior@tieto.com>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Linux Wireless List <linux-wireless@vger.kernel.org>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: compat-wireless-2014-05-22 breaks ath10k in an Archer C7 v2
Date: Thu, 29 May 2014 09:48:55 +0200 [thread overview]
Message-ID: <CA+BoTQmUyvTr+ga81EacbMkE4UVtMBP2PfBs_vH-PF4OvHuZQg@mail.gmail.com> (raw)
In-Reply-To: <CALCETrU=8+tnptdfva4p27nA-5=E31DwXagoLqUxYcLtEKrB+w@mail.gmail.com>
+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.
Michał
WARNING: multiple messages have this Message-ID (diff)
From: Michal Kazior <michal.kazior@tieto.com>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Linux Wireless List <linux-wireless@vger.kernel.org>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: compat-wireless-2014-05-22 breaks ath10k in an Archer C7 v2
Date: Thu, 29 May 2014 09:48:55 +0200 [thread overview]
Message-ID: <CA+BoTQmUyvTr+ga81EacbMkE4UVtMBP2PfBs_vH-PF4OvHuZQg@mail.gmail.com> (raw)
In-Reply-To: <CALCETrU=8+tnptdfva4p27nA-5=E31DwXagoLqUxYcLtEKrB+w@mail.gmail.com>
+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.
Michał
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2014-05-29 7:48 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 [this message]
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
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=CA+BoTQmUyvTr+ga81EacbMkE4UVtMBP2PfBs_vH-PF4OvHuZQg@mail.gmail.com \
--to=michal.kazior@tieto.com \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=luto@amacapital.net \
/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.