On 2017-01-31 16:04, Zoltan Gyarmati wrote: > On 01/31/2017 10:19 AM, Felix Fietkau wrote: >> On 2017-01-29 22:37, Philip Prindeville wrote: >>> Hi. >>> >>> I’m working on a project where I need to be able to force certain >>> kernel configuration parameters from a script, to automate building >>> tailored kernels for performance testing, certification, etc. >>> >>> I love the way that I can use “scripts/diffconfig.sh” to save the >>> deltas into a file… update the cloning/checkout of master over time, >>> yet retain my saved overrides by doing a “cp ../my.config .config ; >>> make defconfig oldconfig” and always end up with a known/good >>> configuration. >>> >>> Alas, I can’t do the same for the target kernel in a scripted way. >>> >>> I’d like to put out a bounty for doing so. If you’re interested, >>> contact me via email to discuss the deliverable and the terms of >>> payment. >>> >>> Ideally, this would be of broad enough applicability that I’d want to >>> upstream this back to OpenWRT for everyone, so keep that in mind as >>> well. >> This is already implemented. You can put any kernel configuration >> overrides into env/kernel-config. >> Generating those is fairly easy too, you can use this command: >> make kernel_menuconfig CONFIG_TARGET=env >> You can also put a full kernel config in that file instead of a delta. >> Running make kernel_oldconfig CONFIG_TARGET=env afterwards will reduce >> that full config to a delta relative to the defaults that LEDE uses. > > Dear Felix & All, > > might be slightly off-topic, but: Is there any similar mechanism to > customize/override not only the kernel config but also the device tree file? Not really. What's your use case for this?
- Felix _______________________________________________ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
