Implement plan for kernel tools
This covers: - merging the kernel tools into the tree itself, and not using them as a separate repo. They will be maintained in an external tree as well for other project use - updating the kernel tools to use updated configuration fragment processing scripts (i.e. the hopefully upstream merge_config.sh scripts) - support for multiple meta data sources - ability to patch the meta branch - ability to be queried for optional kernel configs - ability to support arbitrary kernel repos
This also include configuration management modes, where: - kernel defconfig processing is not used, but instead "all no config" or other modes - defconfigs can be passed as a full override, and not as just another "really big" fragment on top of the base configs. This only applies to existing BSPs and is a way to define a new base for special configuration work.
The following parts remain and will be done in M3 (4D): - support for multiple meta data sources - ability to patch the meta branch - ability to be queried for optional kernel configs
This is resolved: - the meta branch has a file that summarizes the optional kernel features - instead of multi meta branches and patching the meta branch, a cleaner solution of allowing full out of tree feature specification was implemented. This has the same net impact, and does not require complex git repository manipulations.
After discuss with Bruce, this feature doesn't need extra testing. “The visible part of this is TomZ's BSP tool. It's using all of these enhancements to work. So if we can build BSPs and Tom's tools work, that's all the testing that it needs.”