[EXT] config_default vs subtargets having their own config_<ver>?

[Andy Tang]

Hi Tim,

Please see my reply inline.

> -----Original Message-----
> From: Tim Harvey <tharvey at gateworks.com>
> Sent: 2023年3月7日 6:33
> To: Andy Tang <andy.tang at nxp.com>
> Cc: OpenWrt Development List <openwrt-devel at lists.openwrt.org>; Piotr
> Dymacz <pepe2k at gmail.com>
> Subject: Re: [EXT] config_default vs subtargets having their own config_<ver>?
> 
> Caution: EXT Email
> 
> On Sun, Mar 5, 2023 at 10:25 PM Andy Tang <andy.tang at nxp.com> wrote:
> >
> > Hi Tim,
> >
> > Thanks for doing this.
> > I suggest to have config_<kver> for each subtargs in the subtarget dirs..
> >
> 
> Andy,
> 
> I would tend to agree that config_<kever> makes more sense. I'm not sure I
> understand what the point of the config_default files were; I can't find any
> documentation and I'm confused at how OpenWrt creates the .config file for
> the kernel build directory.
> 
> I'm also not understanding how 'make kernel_menuconfig' deals with multiple
> config file fragments and how to separate the configs between subtargets.
Since there is no document about config_default files, we can replace it with config_<kever>.
It is clearer what this config file for.
You can use command "make -j1 V=s" to see how the .config file was created.

> 
> I have a created a minimal defconfig for imx/cortexa7, imx/cortexa9, and
> imx/cortex53 by building these subtargets then doing a 'make -C
> <kernel_builddir> savedefconfig' but now I'm not sure how to be split them
> up.
I am not a fan of this minimal defconfig. It will mix config up.
Changing the config of one platform will affect others.
It is better one platform has its own config file in my point of view.

BR,
Andy
> 
> > I have sent the patches for adding the imx8 platform.
> > But it can't be accepted due to the firmware issue.
> > Basically the DDR firmware for im8x was released by a self-extracted
> binary.
> > When extracted, customer need to accept the EULA which is not accepted
> by OpenWRT community.
> >
> > Have you solved this problem?
> >
> 
> Yes, I saw your patches and what followed. My solution is to eliminate the
> boot firmware which also removes the added complication that the various
> imx8 soc's have binary incompatible firmware and locations that it needs to be
> flashed to.
> 
> Best Regards,
> 
> Tim
> 
> > BR,
> > Andy
> >
> > > -----Original Message-----
> > > From: Tim Harvey <tharvey at gateworks.com>
> > > Sent: 2023年3月4日 8:20
> > > To: OpenWrt Development List <openwrt-devel at lists.openwrt.org>
> > > Cc: Piotr Dymacz <pepe2k at gmail.com>; Andy Tang
> <andy.tang at nxp.com>
> > > Subject: [EXT] config_default vs subtargets having their own config_<ver>?
> > >
> > > Caution: EXT Email
> > >
> > > Greetings,
> > >
> > > I'm working on cortexa53 support for target/linux/imx for imx8
> > > support and am not quite clear how best to take care of kernel
> > > config. There is a lot of differences in kernel config for
> > > cortexa7/cortexa9/cortexa53 with regards to IMX SoC's.
> > >
> > > I see some targets have config_default files in the subtarget dirs
> > > and others have config_<kver>.
> > >
> > > What is the recommended way of defining kernel config per subtarget
> > > and how is it recommended to come up with those split up config files?
> > >
> > > Best Regards,
> > >
> > > Tim