On 5/12/19 10:37 PM, Daniel Engberg wrote:
> Hi,
>
> I'm not sure what the current release roadmap is but since 19.X release
> seems to slipping perhaps it's time to move working targets to 4.19 as
> 4.14 has barely 6 months away before EoL status since there seems to be
> a rather strong opinion
Hi Daniel,
On 5/12/19 10:24 PM, Daniel Engberg wrote:
> Hi,
>
> This patch seems to touch more things that just that... (4.19)
I did a "make kernel_oldconfig" to refresh the configuration. This was
either not done when this configuration was added, the generic
configuration changed or some new K
Hi,
I installed master branch openwrt onto Asus MAP-AC2200 AP. It has tri
band. Its based on IPQ4019 DK04 QCA reference platform. 2 radios
(2Ghz/5Ghz) on AHB bus and one 5GHZ on PCIe bus. Its generally working
fine except one problem in 5Ghz. On both the 5Ghz radios the RSSI is
pretty low on any 5
TL;DR
What would be a workable plan to reconcile mfgr_specific-board-name
at image-generation time with mfgr,specific-board-name at run time?
With the apparent tree-wide changes in progress to canonicalize board
naming of TARGET_DEVICES to mfgr_specific-board-name, there becomes a
disconnect b
This patch fixes `sysupgrade -n` when flashed with rootfs of the same
size as currently running, so the rootfs_data wouldn't get destroyed and
thus survive reboot. So let's fix it by always cleaning up the content
of the rootfs_data during sysupgrade.
Signed-off-by: Petr Štetiar
---
target/linux
Hi,
please make sure that the license info is only parsed when it is required by
the toplevel command being executed, look at the other usages of the PFM_*
macros in the source.
Without this, the in-memory representation of the package trees will consume
way more RAM due to the redundant license
