From: Ben Greear <greearb@candelatech.com>
To: Sebastian Gottschall <s.gottschall@dd-wrt.com>,
Rajkumar Manoharan <rmanohar@qti.qualcomm.com>,
ath10k@lists.infradead.org
Cc: linux-wireless@vger.kernel.org, rmanohar@codeaurora.org,
Felix Fietkau <nbd@nbd.name>
Subject: Re: [PATCH] ath10k: fix system hang at qca99x0 probe on x86 platform
Date: Sat, 23 Jul 2016 14:55:37 -0700 [thread overview]
Message-ID: <5793E7D9.60707@candelatech.com> (raw)
In-Reply-To: <6495e664-5da8-a11b-0bd5-15dc24c51edf@dd-wrt.com>
On 07/23/2016 02:11 AM, Sebastian Gottschall wrote:
> from my point of view this patch is just shit. it trunkates the maximum allocated memory to a certain value.
> so firmware requests 800 kb memory but just gets 256kb. so out of bound memory access is guaranteed at all.
At least some of the firmware logic attempts to deal with this segmentation. 9984 firmware had bugs in one area that I fixed,
but probably there are other bugs and that is why it fails for 9980 firmware.
Even if I fix my firmware, that doesn't help everyone else with stock firmware.
At best, maybe enable this type of logic for only exact firmware with proper feature
flag showing that it is known to work with it.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
prev parent reply other threads:[~2016-07-23 22:09 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-14 6:17 [PATCH] ath10k: fix system hang at qca99x0 probe on x86 platform Rajkumar Manoharan
2016-06-29 13:55 ` Sebastian Gottschall
2016-06-29 14:04 ` Sebastian Gottschall
2016-06-29 14:10 ` Sebastian Gottschall
2016-06-29 16:35 ` Manoharan, Rajkumar
2016-06-29 16:58 ` Sebastian Gottschall
2016-06-30 7:09 ` Michal Kazior
2016-07-19 15:25 ` Manoharan, Rajkumar
2016-07-19 16:13 ` Adrian Chadd
2016-07-19 16:53 ` Ben Greear
2016-07-19 17:00 ` Adrian Chadd
2016-07-20 5:38 ` Michal Kazior
2016-07-20 5:44 ` Adrian Chadd
2016-07-20 6:05 ` Michal Kazior
2016-07-20 6:11 ` Adrian Chadd
2016-07-20 6:27 ` Michal Kazior
2016-07-20 8:49 ` Sebastian Gottschall
2016-07-20 8:51 ` rx rate issue Sebastian Gottschall
2016-07-20 10:23 ` Michal Kazior
2016-07-20 10:50 ` Sebastian Gottschall
2016-07-20 11:03 ` Michal Kazior
2016-07-20 11:10 ` Sebastian Gottschall
2016-07-20 11:32 ` Michal Kazior
2016-07-20 11:12 ` Sebastian Gottschall
2016-07-20 16:42 ` Ben Greear
2016-07-20 16:50 ` Sebastian Gottschall
2016-07-25 14:37 ` 9984 issues Sebastian Gottschall
2016-07-25 14:43 ` Ben Greear
2016-07-25 15:09 ` Sebastian Gottschall
2016-07-25 16:03 ` Adrian Chadd
2016-07-25 16:31 ` Sebastian Gottschall
2016-07-25 17:22 ` Adrian Chadd
2016-07-26 1:11 ` Sebastian Gottschall
2016-07-26 2:26 ` Ben Greear
2016-07-26 2:40 ` Sebastian Gottschall
2016-07-26 9:31 ` 9984 issues solution Sebastian Gottschall
2016-07-26 10:27 ` Michal Kazior
[not found] ` <d5410503-fd51-5076-82 ,36-c296346f5d7f@dd-wrt.com>
[not found] ` <BAY176-W27264163A549F6C69777EFB60D0@phx.gbl>
2016-07-26 3:06 ` Not able to capture qos data packets - QCA988x sudheer thota
2016-07-26 6:21 ` Michal Kazior
2016-07-26 11:53 ` sudheer thota
[not found] ` <BAY176-W426C633D2FC24792734487B90F0@phx.gbl>
2016-07-27 6:51 ` RIFS packets missing on ath10k monitor sudheer thota
2016-07-20 17:02 ` [PATCH] ath10k: fix system hang at qca99x0 probe on x86 platform Adrian Chadd
2016-09-26 16:53 ` [PATCH] ath10k: fix system hang at qca99x0 probe on x86 platform (DMA32 issue) Ben Greear
2016-07-20 16:48 ` [PATCH] ath10k: fix system hang at qca99x0 probe on x86 platform Ben Greear
2016-07-20 5:36 ` Michal Kazior
2016-07-20 16:52 ` Ben Greear
2016-07-22 22:43 ` Ben Greear
2016-07-23 9:11 ` Sebastian Gottschall
2016-07-23 9:45 ` Manoharan, Rajkumar
2016-07-23 21:55 ` Ben Greear [this message]
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=5793E7D9.60707@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@nbd.name \
--cc=rmanohar@codeaurora.org \
--cc=rmanohar@qti.qualcomm.com \
--cc=s.gottschall@dd-wrt.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;
as well as URLs for NNTP newsgroup(s).