From: Sebastian Gottschall <s.gottschall@dd-wrt.com>
To: Sven Eckelmann <sven.eckelmann@openmesh.com>, ath10k@lists.infradead.org
Cc: Ansuel Smith <ansuelsmth@gmail.com>
Subject: Re: 160 mhz crash
Date: Thu, 28 Jun 2018 11:56:02 +0200 [thread overview]
Message-ID: <c5cb2d9f-cbda-be1b-cdd8-cbae3b7886be@dd-wrt.com> (raw)
In-Reply-To: <1788770.Stodcpyumm@bentobox>
Am 28.06.2018 um 08:46 schrieb Sven Eckelmann:
> On Samstag, 16. Juni 2018 10:11:27 CEST Sebastian Gottschall wrote:
>> this is normal. i already posted a patch on this mailinglist to resolve
>> this issue, but
>>
>> but it hasnt found its way to the main source yes.
> Problem seems to be that the patch [1] has obvious style problems and open
> questions.
i understand that. but i dont see a problem with the code style since
the patch is small and not bad looking and on the second hand i was
tired to finish the discussion. it was frustrating me
anyone is welcome to enhance it. without it, the firmware will simply
crash. so its at least usefull to bring it in, in someway. it wont have
bad consequences.
consider also that the patch itself is basicly a port of the behaviour
of the propertiery qca driver. so think its correct and i'm running this
patch for months now
but another thing is that 2 patches are required for getting 160 mhz to
work. the first one which is required since firmware 3.4 was already
posted by me 2 years ago if i'm correct.
without the first patch 160 does not work at all. the second patch
posted 2 months ago is for 3.5 or newer but requires the first patch as well
Sebastian
>
> Kind regards,
> Sven
>
> [1] https://patchwork.kernel.org/patch/10372949/
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2018-06-28 9:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-15 21:04 160 mhz crash Ansuel Smith
2018-06-16 8:11 ` Sebastian Gottschall
2018-06-28 6:46 ` Sven Eckelmann
2018-06-28 9:56 ` Sebastian Gottschall [this message]
2018-07-03 14:58 ` Kalle Valo
2018-07-04 6:05 ` Sebastian Gottschall
2018-06-28 9:56 ` Sebastian Gottschall
2018-06-28 12:24 ` Sven Eckelmann
2018-06-29 4:12 ` Sebastian Gottschall
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=c5cb2d9f-cbda-be1b-cdd8-cbae3b7886be@dd-wrt.com \
--to=s.gottschall@dd-wrt.com \
--cc=ansuelsmth@gmail.com \
--cc=ath10k@lists.infradead.org \
--cc=sven.eckelmann@openmesh.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