[PATCH] gemini: Bump to kernel v5.10

Hauke Mehrtens hauke at hauke-m.de
Tue Apr 13 22:37:07 BST 2021

On 4/13/21 10:02 AM, Linus Walleij wrote:
> On Mon, Apr 12, 2021 at 8:32 PM Christian Lamparter <chunkeey at gmail.com> wrote:
>> Hmm, when building this with the BUILDBOT config (CONFIG_BUILDBOT)
>> and throw in the CONFIG_ALL_* for userspace + kernel modules for
>> good measure. It fails with the default world build (without the
>> V=s option) because the following symbols are not yet defined in
>> either the generic or gemini-specific kernel config.
>> At least CPU_THERMAL is also a show-stopper for apm82181 5.10,
>> so should these just be added added as either disabled
>> (# CONFIG_ ... is not set) or in case of CONFIG_PCIEASPM=X
>> (whatever the default is there) in target/linux/generic/config-5.10?
> Hm how do I help best with this? I don't always have the big picture of what
> OpenWRT needs, just working in my little corner :D
> I get as much as that we need to fix up target/linux/generic/config-5.10
> as none of these config options pertain to Gemini per se.
> I suppose I should make a separate patch for that setting them all to
> "# .... is not set" simply.
> I am unsure about the procedure to test it though, also I always get a
> bit confused about how these configs are even generated.
> Yours,
> Linus Walleij

Hi Linus,

The target kernel configurations should be small and most of the generic 
settings should be done in the target/linux/generic/config-* config file.
The target configuration only contains the extra configuration options 
or the options which are different.

For example do you really need CONFIG_OABI_COMPAT for gemini?

You should try to remove just most of the options which are not SoC 

You can add new generic options to target/linux/generic/config-5.10 
manually. For example "# CONFIG_MTD_PHYSMAP_IXP4XX is not set" would 
make sense there, if some target really needs it, the target kernel 
config can be activated for one target again.

You can refresh your kernel configuration like this:
make kernel_oldconfig CONFIG_TARGET=target
and this:
make kernel_oldconfig CONFIG_TARGET=subtarget

To test the new kernel configuration, building with all kernel modules 
activated is helpful. You can do it by activation CONFIG_ALL_KMODS=y in 
the OpenWrt configuration. This is what the build bot uses:


More information about the openwrt-devel mailing list