From: Matti Laakso <malaakso@elisanet.fi>
To: ath10k@lists.infradead.org
Subject: Re: Re: compat-wireless-2014-05-22 breaks ath10k in an Archer C7 v2
Date: Fri, 06 Jun 2014 10:59:32 +0200 [thread overview]
Message-ID: <539182F4.1080804@elisanet.fi> (raw)
In-Reply-To: <87r433ps7w.fsf@kamboji.qca.qualcomm.com>
> ------------------------------------------------------------------------
> Andy Lutomirski <luto at amacapital.net <http://lists.infradead.org/mailman/listinfo/ath10k>> writes:
>
> >/ On Thu, May 29, 2014 at 12:48 AM, Michal Kazior <michal.kazior at tieto.com <http://lists.infradead.org/mailman/listinfo/ath10k>> wrote:
> />>/ +ath10k at lists.infradead.org <http://lists.infradead.org/mailman/listinfo/ath10k>
> />>/
> />>/ On 28 May 2014 20:35, Andy Lutomirski <luto at amacapital.net <http://lists.infradead.org/mailman/listinfo/ath10k>> 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.
> />/
> />/ Ideally, someone from Atheros could figure out what the error is.
> /
> Michal already did. The error means that for some reason the
> calibaration data was not found from OTP. OTP is the storage area where
> the calibration data is normally stored within QCA9880.
>
> >/ Barring that, the card seems to work okay without otp (I don't even
> />/ know what otp is), so just warning and continuing to load might be
> />/ better than bailing.
> /
> This means that your card is not properly calibrated and it doesn't
> function in an optimal way (for example range or throughput is less than
> what it could be).
>
> Do you see that with all Archer C7 v2 devices or with just one? One
> possibility is that the calibration data is actually stored outside of
> QCA9880 board, for example in the host flash or similar. I don't have
> that AP, can someone else see where the calibration data is stored?
>
> I know that ath9k supports this kind of setup, most likely ath10k should
> as well.
>
> --
> Kalle Valo
>
C7 v1 has the AR9550 calibration data in flash in the last 64 kiB,
likely C7 v2 as well. Could someone with v2 and OpenWrt use dd to dump
the contents of the "art" partition (/dev/mtdblock4 IIRC) and upload it
somewhere? I think it would be easy to see whether there is just the
calibration data for AR9550 or if there is also data for QCA9880.
Matti
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2014-06-06 9:00 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 [this message]
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=539182F4.1080804@elisanet.fi \
--to=malaakso@elisanet.fi \
--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.