> I used the tftp/bootp protocol to load the kernel, the initrd and > the fdt into RAM from u-boot (the auto-boot), and then pass the > three addresses (fixed) to the bootm command in order: bootm > 0x100000 0x200000 0x3000000. Of course, I had to extend the BOOTP > protocol with an OEM extension to allow Bootp to know about the FDT, > but that facility was already in U-Boot -- you simply need to look.
So you had to extend an RFC protocol to boot some form of Linux. Sure, that's the way thing go - I'm gonna fix my bootp server right now to support the wicked way Linux on ARM does things, just so that I get a thin chance for a kernel to recognize the world it's running in. Am I the only one to think that we are trying to walk on our heads where the way to boot a kernel is to chainsaw a good-old-comes-with-an-RFC protocol to the greedy needs of a particular operating system? > They do risk being spoiled by their own success ... OK ... everyone > drop arm, and go to MIPS -- immediately! 8-) I'd drink to that.
