From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Zaki <zaki.bm@gmail.com>
Cc: ath10k@lists.infradead.org
Subject: Re: Crash when loading module
Date: Fri, 30 Aug 2013 10:29:14 +0300 [thread overview]
Message-ID: <877gf3ab79.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <87ppsyiavy.fsf@kamboji.qca.qualcomm.com> (Kalle Valo's message of "Wed, 28 Aug 2013 09:32:01 +0300")
Kalle Valo <kvalo@qca.qualcomm.com> writes:
> Zaki <zaki.bm@gmail.com> writes:
>
>> The PCIe module is taken from Archer C7 V1 product's board. I am not
>> so sure if it is V2 hardware, though. I just depends on the debugging
>> msg that says it is V2 device.
>>
>> The way i force it to use legacy interrupt is by modifying the code to
>> skip MSI-X and MSI. The ath10k code is taken from ath.git master
>> branch.
>>
>> Thanks a lot for the link. If someone can verify that the module on
>> Archer C7 V1 is actually a V1 hardware, then it will be very helpful
>> also.
>
> To my knowledge Archer C7 has QCA9880 v1. Because the PCI ids are the
> same I'm not currently aware of any way to detect from ath10k if QCA9880
> v1 or v2 :(
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.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2013-08-30 7:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-16 9:46 Crash when loading module 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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-08-31 15:31 Christian Lamparter
2013-09-01 6:15 ` 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=877gf3ab79.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=zaki.bm@gmail.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