On 09.02.21 11:02, Arthur Heymans wrote: Hi,
My question to the community is if it would be ok to allow for the build system integration code for KM and BPM generation to be integrated into the master branch before the code to the tooling is made public.
Please define 'integration' and 'made public' Can we already get this tool anywhere, as binary ? (just the source not published yet ?) IMHO, adding blobs to a source tree is always problematic, even more for stuff executed by the build process. Blobs for things like early init are something I could only live with as a temporary measure, hoping somebody takes the time for rever-engineering. (things microcode or firmware for some very special controller are different issue). With 'integration' I guess you mean, the tool is called somewhere in the build process. In that case, IMHO it could be expected as an external program (just like compiler, linker, etc) and being an optional dependency: eg. having an option like 'rebuild foobar' with a clear documentation the dependency on that external tool, where to get it, where it runs, etc. Once it's really open souce and can be built anywhere, I could imaging letting the coreboot build system also fetch and build that tool when needed. --mtx -- --- Hinweis: unverschlüsselte E-Mails können leicht abgehört und manipuliert werden ! Für eine vertrauliche Kommunikation senden Sie bitte ihren GPG/PGP-Schlüssel zu. --- Enrico Weigelt, metux IT consult Free software and Linux embedded engineering i...@metux.net -- +49-151-27565287 _______________________________________________ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-le...@coreboot.org
