All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Matti Laakso <malaakso@elisanet.fi>
Cc: ath10k@lists.infradead.org
Subject: Re: compat-wireless-2014-05-22 breaks ath10k in an Archer C7 v2
Date: Fri, 6 Jun 2014 12:09:46 +0300	[thread overview]
Message-ID: <8738fimmjp.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <539182F4.1080804@elisanet.fi> (Matti Laakso's message of "Fri, 06 Jun 2014 10:59:32 +0200")

Moro,

Matti Laakso <malaakso@elisanet.fi> writes:

>> 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.
>
> C7 v1 has the AR9550 calibration data in flash in the last 64 kiB,
> likely C7 v2 as well.

Ok, then the chances are that QCA9880 calibration data is stored in the
flash 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.

Good idea.

-- 
Kalle Valo

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

  reply	other threads:[~2014-06-06  9:10 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 [this message]
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=8738fimmjp.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@qca.qualcomm.com \
    --cc=ath10k@lists.infradead.org \
    --cc=malaakso@elisanet.fi \
    /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.