Hi Ben, > My only potential objection was that it might have been cleaner to > actually build prom_init.c as a separate binary alltogether and piggy > back it...
Yeah, I went through a number of options before settling on this one. Move prom_init.c into arch/powerpc/boot Pros: - 32 bit environment fits well with 32 bit OF interface - Clear separation enforced between prom_init.c and rest of kernel - Can build boot wrapper -mrelocatable, similar to ppc32 kernel Cons: - tools that assume we can boot a vmlinux will break. - distro bootloader tools - provisioning and test environments - profiling and debugging tools that currently use a vmlinux will break - oprofile, perf - Places more pressure on already fragile early memory map - have to uncompress the zImage somewhere in the RMO - prom_init.c needs to pull in quite a lot of kernel headers - seemed difficult to force them to build 32 bit - Increased simulator boot times due to uncompress stage Build prom_init.c 32 bit and attach the vmlinux as a binary blob. This means a vmlinux will be bootable, but profiling tools still wont work. Build prom_init.c 32 bit, tack it onto the end of the vmlinux and add a trampoline at the start of the vmlinux. This means a vmlinux will be bootable and profiling tools will work against it. Even so it feels gross to me. Anton _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
