[OpenWrt-Devel] [PATCH] kernel: ath10k-ct: provide a build variant for small RAM devices
chunkeey at gmail.com
Sun Dec 15 06:00:48 EST 2019
On Wednesday, 11 December 2019 20:16:52 CET Paul Fertser wrote:
> Hey Ben,
> On Wed, Dec 11, 2019 at 10:06:26AM -0800, Ben Greear wrote:
> > On 12/11/19 6:44 AM, Paul Fertser wrote:
> > > According to many bugreports  the default ath10k-ct kernel
> > And also if you want to just have the makefile pass a -DBUILD_ATH10K_SMALL or something
> > like that and #ifdef code in the ath10k-ct driver, then I'd apply that patch to ath10k-ct
> > so that you don't need the patches.
> I am offering my patch to the OpenWrt maintainers as kind of a
> stop-gap measure to get ath10k-ct working for the release (or in any
> way they think is appropriate). Another approach they can choose is to
> select the upstream ath10k for those devices. Otherwise some
> previously supported boards will require manual intervention to get
> WiFi working after an upgrade.
> Regarding your fwcfg idea, I am not sure it will work as it seems the
> PCI initialisation is happening before fwcfg is parsed and applied.
> Adding a Kconfig option is another possibility.
> But what do you think about an additional module parameter, wouldn't
> it be the cleanest solution in the long run?
> BTW, according to the git logs the patches were initially added by
> Christian Lamparter, so I hope he can clarify the situation a
> bit. Probably there were some performance tests executed back than to
> measure the impact.
Heh no. These patches come up in discussions time and time again. And I
would rather see them being removed alltogether. What I can tell you is
that the Idea of limiting ath10k memory thirst came from Qualcomm itself.
If you look on the ML you can find the old posts like:
And for reference: Here's a independent bootlog (from pepe2k/Piotr Dymacz
no less) with the "Low Memory System" messages for the RT-AC58U:
More information about the openwrt-devel