On Wed, Oct 6, 2010 at 1:43 AM, Eric W. Biederman firstname.lastname@example.org wrote:
Peter Stuge email@example.com writes:
Eric W. Biederman wrote:
At the moment I want to mandate a bzImage for x86, but I'm not certain if that is practical the way we build images for coreboot.
I think I need to ensure that linux builds a bImage. So that you can have an uncompress bzImage. For this embedded case.
bImage would help make mkelfImage's life easier staying forward compatible?
Wow. This project got paged out :(
Always working with a bzImage format would help with being compatible. Having an uncompressed kernel aka a bImage in that format would help having a smaller total size, by not needing to have a decompressor in both the kernel image and in coreboot.
-- coreboot mailing list: firstname.lastname@example.org http://www.coreboot.org/mailman/listinfo/coreboot
Hello! I can see where this is traveling to. It is indeed taking a long time to get there.
However what about the kexec tools? I freely admit that the kernel function is now a part of the basic kernel configuration. But what about the tools themselves? As it happens my newer Slackware Linux system is running a 126.96.36.199-smp kernel. (Dual P4 system, with features that lend itself to Coreboot, if it wasn't for specialized functions that machine claims to need.)
----- Gregg C Levine email@example.com "This signature fought the Time Wars, time and again."