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: Mon, 9 Jun 2014 11:28:29 +0300 [thread overview]
Message-ID: <87lht6h4gi.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <53944E64.9000002@elisanet.fi> (Matti Laakso's message of "Sun, 08 Jun 2014 13:52:04 +0200")
Matti Laakso <malaakso@elisanet.fi> writes:
>> ------------------------------------------------------------------------
>> Hi Kalle,
>>
>> Am 07.06.2014 07:36, schrieb Kalle Valo:
>> >/ Kamal Koshy <kamal.koshy at gmail.com <http://lists.infradead.org/mailman/listinfo/ath10k>> writes:
>> />/
>> />>/ Attaching the result of dd if=/dev/mtd4 > ~/mtd4
>> />/ Thanks, I'll take a look at that later. But before that, do you know
>> />/ what's the mac address of the QCA9880 device with the proprietary
>> />/ driver? (_not_ with ath10k) That would help searching for the
>> />/ calibration data.
>> />/
>> /To me it looks like ath9k calibration data starts at 0x1000, and ath10k
>> calibration data
>> starts at 0x5000 in that mtd image. That's the same as on my board.
>>
>> Sven
>>
>
> Yeah, that's definitely the case.
>
> I think we need something like this for ath10k:
>
> https://github.com/kvalo/ath/blob/master/include/linux/ath9k_platform.h
>
> which we can then populate in the mach-file.
Yeah, we need that. But before that an ugly workaround is to do what
Michal suggests (copy the content to board.bin and skip otp.bin
execution in ath10k).
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2014-06-09 8:29 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CALCETrU=8+tnptdfva4p27nA-5=E31DwXagoLqUxYcLtEKrB+w@mail.gmail.com>
2014-05-29 7:48 ` compat-wireless-2014-05-22 breaks ath10k in an Archer C7 v2 Michal Kazior
2014-05-29 17:52 ` Andy Lutomirski
2014-06-05 10:26 ` Kalle Valo
2014-06-05 16:04 ` Andy Lutomirski
2014-06-05 16:08 ` Ben Greear
2014-06-05 16:23 ` Andy Lutomirski
2014-06-06 6:39 ` Kalle Valo
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 [this message]
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=87lht6h4gi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox