My (feeble) understanding is that I *do* need to re-flash u-boot if I want to use the new u-boot and 2.6 in-stream kernel together, becasue of the device-tree issue, no?
Yes, you're right, sorry I misunderstood you.
I still have the 2.4.17 kernel in flash, and eventually my system boots into the 2.6.20 kernel built by Sylver. Though I may have correctly built a new u-boot, as far as I can tell there is no clear path to test it in RAM, since I get an 'invalid module format' error when I try to run the u-boot-load-hg.sh script from within my debian install, per the wiki instructions for the 2.6 mainstream kernel. And I don't want to try to flash it without testing it first, lest I become a resident of Brick City.
The uloader.o module only works under a 2.4 kernel. I tested it under a 2.4 kernel, but had troubles because I had uboot 1.1.4 in flash already and the environment screwed up the 1.2 uboot I was trying to test. I finally gave up and then mindbender pointed me to a known-good 1.2 uboot that I flashed the old fashioned way while in EM mode. (and then I still had troubles because of the environment issue, fixed by erasing the environment as I posted in the post above)
I can point you to the same uboot that mindbender pointed me to, it works
Note, you can tell by the filename that it's for an HG. If you don't have an HG, don't flash it!
I see timtimred also has another uboot download,
that I suppose would work for original kuro (?) but "hd" confuses me a little so maybe ask timtimred to be sure if you don't have an HG.