In your own target build, yes this is from your own build-config. Roughly put, the way I see it is that it captures all the changes that occurred from the make menuconfig up to make. It's the make command that generates this config.seed file.
AFAIK if you delete your .config file, issue make menuconfig and only select the target and exit, you'll end up with the same config/settings used by the buildbot.
thx now i have it. I was wondered about the 256 MB root partition in the normal .config from a fresh make menuconfig. I think this is the max value where the compiler from source and image-builder don't create images and only compile sources. My wdr2200 only have 8 Mb flash. But important is the kernel config for my architecture, i know :).
Thx great Links. Now after recompile i know the complete source-file from the modem is functioned mach-wnr2200.c but complely hacked from the openwrt-community and the usb-port functioned but the other gpio-led-requests are not functioned. All patches from the openwrt-community are taken about a few patch process that never be used in the lede-source.
And now i must bugfix the mach-wnr2200.c with few suggestions from the openwrt-com and even test needs a recompile from this driver why its a internal kernel-module.
Now i know that my problem is not a missing package from the original buildbot-process:).
No good news for me:). I download LEDE for my old wnr2200 and for extroot i must bugfixing an kernel-driver and recompile a few hours:). Smile.