After 34 patches converting all sandybridge boards to Haswell-style SPD info, I now need to run abuild to see if I missed any, To save time, space, and possibly wear on my SSD I only want to run abuild on sandybridge boards (i.e. boards with NORTHBRIDGE_INTEL_SANDYBRIDGE Kconfig) and, for boards that don't force USE_NATIVE_RAMINIT, run it with that Kconfig off.
I ran this from my mechanical USB drive: $ util/abuild/abuild --timeless --skip_unset NORTHBRIDGE_INTEL_SANDYBRIDGE -R /usr/src/coreboot
And all boards get skipped. It seems right, until I saw these two known SNB boards getting skipped too, then I stopped the run.
Building board INTEL_DQ67SW (using default config) Building INTEL_DQ67SW Creating config file for INTEL_DQ67SW... INTEL_DQ67SW (Skipping CONFIG_NORTHBRIDGE_INTEL_SANDYBRIDGE not set) INTEL_DQ67SW config created. config file: coreboot-builds/INTEL_DQ67SW/config.build has incorrect config value INTEL_DQ67SW does not have NORTHBRIDGE_INTEL_SANDYBRIDGE set. Skipping at user's request. Building board INTEL_EMERALDLAKE2 (using default config) Building INTEL_EMERALDLAKE2 Creating config file for INTEL_EMERALDLAKE2... INTEL_EMERALDLAKE2 (Skipping CONFIG_NORTHBRIDGE_INTEL_SANDYBRIDGE not set) INTEL_EMERALDLAKE2 config created. config file: coreboot-builds/INTEL_EMERALDLAKE2/config.build has incorrect config value INTEL_EMERALDLAKE2 does not have NORTHBRIDGE_INTEL_SANDYBRIDGE set. Skipping at user's request.
Is what I did supposed to work?
For the second item about USE_NATIVE_RAMINIT, do I really have to set a board config for each and every MRC raminit board and turn it off there?
Hi Keith, Sorry about the late reply here. Responses inline:
Jul 25, 2023, 22:25 by buurin@gmail.com:
After 34 patches converting all sandybridge boards to Haswell-style SPD info, I now need to run abuild to see if I missed any, To save time, space, and possibly wear on my SSD I only want to run abuild on sandybridge boards (i.e. boards with NORTHBRIDGE_INTEL_SANDYBRIDGE Kconfig) and, for boards that don't force USE_NATIVE_RAMINIT, run it with that Kconfig off.
I ran this from my mechanical USB drive: $ util/abuild/abuild --timeless --skip_unset NORTHBRIDGE_INTEL_SANDYBRIDGE -R /usr/src/coreboot
And all boards get skipped. It seems right, until I saw these two known SNB boards getting skipped too, then I stopped the run.
Building board INTEL_DQ67SW (using default config) Building INTEL_DQ67SW Creating config file for INTEL_DQ67SW... INTEL_DQ67SW (Skipping CONFIG_NORTHBRIDGE_INTEL_SANDYBRIDGE not set) INTEL_DQ67SW config created. config file: coreboot-builds/INTEL_DQ67SW/config.build has incorrect config value INTEL_DQ67SW does not have NORTHBRIDGE_INTEL_SANDYBRIDGE set. Skipping at user's request. Building board INTEL_EMERALDLAKE2 (using default config) Building INTEL_EMERALDLAKE2 Creating config file for INTEL_EMERALDLAKE2... INTEL_EMERALDLAKE2 (Skipping CONFIG_NORTHBRIDGE_INTEL_SANDYBRIDGE not set) INTEL_EMERALDLAKE2 config created. config file: coreboot-builds/INTEL_EMERALDLAKE2/config.build has incorrect config value INTEL_EMERALDLAKE2 does not have NORTHBRIDGE_INTEL_SANDYBRIDGE set. Skipping at user's request.
Is what I did supposed to work?
Yes, that command line looks reasonable and actually works for me though for some reason it still says it's skipping it. I'll look at what the issue is there. Thanks for bringing this to my attention.
``` Building APPLE_MACBOOKAIR4_2 Creating config file for APPLE_MACBOOKAIR4_2... APPLE_MACBOOKAIR4_2 (Skipping CONFIG_NORTHBRIDGE_INTEL_SANDYBRIDGE not set) APPLE_MACBOOKAIR4_2 config created. Compiling APPLE_MACBOOKAIR4_2 image... APPLE_MACBOOKAIR4_2 built successfully. (took 34.356 seconds) ```
In the meantime, I added a script a little while back to do exactly what you want: util/scripts/testsoc
``` testsoc version 1.00 The testsoc script helps select boards to run test builds on. It searches through all of the mainboard Kconfig files for specified identifiers and then runs abuild on the mainboards it finds.
Usage: testsoc [options]
Options: -a | --abuild "<text>" Specify options to pass to abuild -C | --cpus <num> Specify number of CPUs to use -K | --kconfig <CONFIG> Search for Kconfig option (-K can be used multiple times) -n | --no_cros Don't run chromeos builds -h | --help Print usage and exit -D | --debug Print debug information. Use -DD to show all commands -V | --version Print the version and exit --nocolor Don't print color codes ```
Here's the command line you'd want. util/scripts/testsoc -K NORTHBRIDGE_INTEL_SANDYBRIDGE
For the second item about USE_NATIVE_RAMINIT, do I really have to set a board config for each and every MRC raminit board and turn it off there?
abuild lets you supply a saved config file to apply over the config normally used. This allows you to update settings. You should be able to make a config file with just the one setting CONFIG_USE_NATIVE_RAMINIT=y, then tell abuild to use that file with -K <filename>.
for the testsoc script, that would look like:
util/scripts/testsoc -K NORTHBRIDGE_INTEL_SANDYBRIDGE -a "-K <filename>"
coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-leave@coreboot.org
-
Keith Hui -
Martin Roth