Kernel 2.6.29 and uBoot 1.3.2 possible?

[esky-sh]

Exactly the same thing has happened to me when I was upgrading from kernel 2.6.13 to 2.6.28.2. I guess that machine ID in the bootloader does not match ID in the kernel.
I've looked into 2.6.13 sources and found that ID used in /arch/arm/tools/mach-types was:
sbc2440 ARCH_SBC2440 SBC2440 782
And in 2.6.28.2 it is:
s3c2440 ARCH_S3C2440 S3C2440 362
So I modified /arch/arm/mach-s3c2440/mach-qq2440.c near the end of the file (PNX4008 is 782 in 2.6.28.2):
//MACHINE_START(S3C2440, "QQ2440V3")
//travesty because our QQ2440V3 board reports machine type 782 instead of 362
MACHINE_START(PNX4008, "QQ2440V3")
/* Maintainer: Ben Dooks <ben@fluff.org>, LeshaK <leshak@leshak.ru> */
Rebuilt the kernel and presto, it boots fine.
I guess that right thing to do is to modify bootloader to have right machine ID, but I'm not building my own loader yet. In fact, I'm using that god forsaken Vivi that came with the board.
Which brings me to the question for you, Peter, or anybody else using uBoot: how to flash uBoot image from Vivi?
Thanks in advance.

In supervivi menu, there is an 'a' command to burn bootable user application directly into nandflash. Of course you can burn your own u-boot image by this command.