>
> I already need a new format for LinuxBIOS, because I can't use
> bzImages.
>
[...]
>
> Personally I think all of that is just flawed. The bootloaders should
> be simple. They should be able to load the ramdisk at a fixed address
> (assuming the memory isn't reserved). And they shouldn't need to be
> changed every time the kernel has a problem.
>
And your solution is to come up with a new format that is (a) MORE
complex, (b) DIFFERENT, (c) incompatible?
Give me a break. You have just added so much complexity it's not even
funny. I can guarantee you that people *WILL* ask for every single
existing bootloader out there to support your new format. It's a support
nightmare for all of us that write bootloaders, and not just for you.
If your complaint is about the lack of a 32-bit entrypoint such can
probably be added to the existing format (it would require
Oh, and as far as "simple" is concerned, I should let you know that when I
work on syslinux, I count bytes. The existing protocol is definitely
suboptimal in that respect (this is due to some severe mistakes which were
done in the original initrd implementation), but we're stuck with it. All
you're accomplishing is creating two completely incompatible formats,
*BOTH* of which will need to be supported for the forseeable future.
-hpa
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/