Re: Kernel config

HI;

On Do, 2019-06-13 at 09:27 +0200, Erich Titl wrote:
> Hi folks
> 
> I did some work on a specific kernel config for old wrap systems and
> got
> frustrated by 2 issues.
> 
> - despite my past advocacy for a difference based kernel config I
> found
> it was not very practical and does not save time

It depends on the task you need to accomplish. I have mixed results.

I have the suspicion that stuff from tah main config (i486) may leak
into e.g. wrap weher it's unwanted - on the other hand adding a feature
for all architectures is pretty easy the way we work today.


> - including kernel release information in the names of the config
> files
> does IMHO help anything and is _not_ version tool friendly

I disagree; the release information is used from
make/toolcahin/[architecture] and was introduced to allow a different
kernel version for an architectures that won't build with the current
kernel version.
Though this isn't used very often, I've used it during on beta versions
in the past - upgrading the kernel for ARCH=i386 whilst keeping the
older kernel version for ARCH=arm.

> So I would suggest to drop the diffing method and return to generic
> config name, e.g.
> 
> - drop the diffes and use enter the specific configurations into git

Both are there at the moment.

> - drop the kernel version in the config files and make them generic
> (inside the various kernel source there is never a version mentioned
> in
> the filenames.

See make/toolchain

Just my 2 cents
kp

> cheers
> 
> ET
> 
> 
> 
> _______________________________________________
> leaf-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/leaf-devel