Seems to be a problem for me.... I created a new trunk at the version you specified and copied in the patch files and the .config. You can't copy the kernel config file in as the build tree doesn't exist at this time (plus I think it should go into trunk/build_dir/linux-lantiq_danube/linux-3.2.12/kconfig?) The build fails when trying to apply a patch
Ric.
Code:
make[4]: Entering directory `/home/ric/openwrt/trunk/target/linux/lantiq'
if [ -s "/home/ric/openwrt/trunk/build_dir/linux-lantiq_danube/linux-3.2.12/patches/series" ]; then (cd "/home/ric/openwrt/trunk/build_dir/linux-lantiq_danube/linux-3.2.12"; if quilt --quiltrc=- next >/dev/null 2>&1; then quilt --quiltrc=- push -a; else quilt --quiltrc=- top >/dev/null 2>&1; fi ); fi
Applying patch platform/0901-MIPS-lantiq-machtypes-add-bthhv2b.patchpatching file arch/mips/lantiq/machtypes.h
Hunk #1 FAILED at 50.
1 out of 1 hunk FAILED -- rejects in file arch/mips/lantiq/machtypes.h
Patch platform/0901-MIPS-lantiq-machtypes-add-bthhv2b.patch does not apply (enforce with -f)make[4]: *** [/home/ric/openwrt/trunk/build_dir/linux-lantiq_danube/linux-3.2.12/.quilt_checked] Error 1make[4]:
Leaving directory `/home/ric/openwrt/trunk/target/linux/lantiq'
OK, have now done some debug...
Patches 0901xxx and 0902xxx are the problems. It looks like the patches were made against the files in the build directory after a make has completed. If you do a make clean and then try and apply the patches the files to be patched are different (looks like they haven't yet been patched by other patches). No idea how you fix this?
And some more debug.
The patch files need to be executed last in the chain so by removing the leading zero so all patches start with a 9 ensures this and the image now builds. The boot now finds the virtual machine but does not detect the flash chips.
Code:
[ 0.364000] ltq_asc.1: ttyLTQ1 at MMIO 0x1e100c00 (irq = 112) is a ltq_asc
[ 0.372000] console [ttyLTQ1] enabled, bootconsole disabled
[ 0.372000] console [ttyLTQ1] enabled, bootconsole disable
[ 0.388000] ltq_nor ltq_nor.0: probing failed
Will carry on debugging...