From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Christian Lamparter <chunkeey@googlemail.com>
Cc: ath10k@lists.infradead.org
Subject: Re: Crash when loading module
Date: Sun, 1 Sep 2013 09:15:06 +0300 [thread overview]
Message-ID: <87d2ot83v9.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <201308311731.26207.chunkeey@googlemail.com> (Christian Lamparter's message of "Sat, 31 Aug 2013 17:31:25 +0200")
Christian Lamparter <chunkeey@googlemail.com> writes:
>> Found a way now:
>>
>> http://lists.infradead.org/pipermail/ath10k/2013-August/000279.html
>>
>> Zaki, I would appreciate if you could test that patch and see if ath10k
>> still crashes (it shouldn't). And if you want to provide your full name
>> I can add your name to the Reported-by tag.
>
> I get this before it crashes now. (This is a QCA-9880-AR1A from TP-Link Archer C7)
>
> [ 271.140000] ath10k: Warning: chip id 0x043200ff is not known, expect problems
>
> Could it be, that this is just a typo, or are there several v1.0 chip_ids?
I found out (after I sent the patch) that the chip id actually contains
more than just the hardware revision. So when testing for hard revision
(hw1.0 vs hw2.0) we need to do:
(chip_id & 0xf00) >> 8
0x2 will be hw2.0 and 0x0 will be hw1.0. This seems to match with the
chip ids my boards have and also you what you have. I'll send a v2,
thanks for the feedback.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2013-09-01 6:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-31 15:31 Re: Crash when loading module Christian Lamparter
2013-09-01 6:15 ` Kalle Valo [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-08-16 9:46 Zaki
2013-08-28 5:40 ` Kalle Valo
[not found] ` <CABQkniBk-BUJW5Prjzw4J7jh=km15AZkNim523QZ+eU72=oJeQ@mail.gmail.com>
2013-08-28 6:32 ` Kalle Valo
2013-08-28 6:40 ` Zaki
2013-08-28 6:58 ` Bartosz Markowski
2013-08-28 7:13 ` Zaki
2013-08-28 7:46 ` Zaki
2013-08-28 7:59 ` Kalle Valo
2013-08-30 7:29 ` 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=87d2ot83v9.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=chunkeey@googlemail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox