On Thu, Sep 04, 2025 at 03:56:26PM +0200, Marek Vasut wrote: > On 9/4/25 10:19 AM, Philip Oberfichtner wrote: > > On Wed, Sep 03, 2025 at 02:51:44PM +0200, Marek Vasut wrote: > > > On 9/3/25 12:56 PM, Philip Oberfichtner wrote: > > > > > > > diff --git a/configs/am62x_beagleplay_a53_defconfig > > > > b/configs/am62x_beagleplay_a53_defconfig > > > > index 05853317fea..dfac96379ce 100644 > > > > --- a/configs/am62x_beagleplay_a53_defconfig > > > > +++ b/configs/am62x_beagleplay_a53_defconfig > > > > @@ -20,6 +20,7 @@ CONFIG_SPL_HAS_BSS_LINKER_SECTION=y > > > > CONFIG_SPL_BSS_START_ADDR=0x80c80000 > > > > CONFIG_SPL_BSS_MAX_SIZE=0x80000 > > > > CONFIG_SPL_STACK_R=y > > > > +CONFIG_HAS_SPL_SIZE_LIMIT=y > > > How much of this massive config file patching can be done using some > > > "select" in Kconfig file ? > > > > I'm not following you here. I'm only adding CONFIG_HAS_XXX_SIZE_LIMIT > > wherever there already was an explicit CONFIG_XXX_SIZE_LIMIT in the > > defconfig before. I'm not changing anything here. Can you please > > elaborate on what it is that your asking for? > > Can this massive configs/ update be avoided by using a default value / > select / imply in some Kconfig file ?
No, I'm afraid it cannot ...
