All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sven Schnelle <svens@stackframe.org>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: compat-wireless-2014-05-22 breaks ath10k in an Archer C7 v2
Date: Mon, 09 Jun 2014 22:01:38 +0200	[thread overview]
Message-ID: <539612A2.60400@stackframe.org> (raw)
In-Reply-To: <CA+BoTQ=OogF--KzZS9SkQorjqHSCwp6MzM4yYojri4uGzH3+3w@mail.gmail.com>


Am 09.06.2014 07:07, schrieb Michal Kazior:
> On 7 June 2014 08:11, Sven Schnelle <svens@stackframe.org> wrote:
>> Hi Kalle,
>>
>> Am 07.06.2014 07:36, schrieb Kalle Valo:
>>
>>> Kamal Koshy <kamal.koshy@gmail.com> 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.
> The data looks very similar to board.bin (2116 bytes and familiar hex
> patterns). Can anyone replacing using it as the
> /lib/firmware/ath10k/QCA988X/hw2.0/board.bin?
>

Doesn't make a difference. The flash layout is the same on my 
engineering sample,
and i've extracted board.bin from the flash layout. Can anyone explain 
how OTP
works? It looks to me like otp is only run if calibration data in flash 
is invalid in the
proprietary driver.

Thanks
Sven

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

  reply	other threads:[~2014-06-09 20:02 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 [this message]
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=539612A2.60400@stackframe.org \
    --to=svens@stackframe.org \
    --cc=ath10k@lists.infradead.org \
    --cc=michal.kazior@tieto.com \
    /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.