for the sake of an upcoming embedded linux class, i want to demonstrate how various files in the current u-boot contribute to, and are processed by, the initial configuration step to finally produce the resulting .config file.

first, a possibly dumb question -- is the .config file the sole generated artifact of the configuration process? it would appear to be based on using git to see what else was created, and .config seems to be it. is that true?

and getting into the meat of the question, as an example, i decided to document how u-boot processes numerous files to produce that .config file for the zynq zedboard, and i've already written some of that here:

https://crashcourse.ca/dokuwiki/doku.php?id=u-boot_configuration

the point is to show how, from the simple command:

$ make zynq_zed_defconfig

u-boot consults various Makefile, Kconfig, config.mk files, board files and so on to come up with the final .config.

if someone already did that once upon a time, that'd be great, but i'm going to guess i'm on my own here. thoughts?

rday