From: Grant Likely <grant.likely@xxxxxxxxxxxx> Date: Tue, 6 Jul 2010 01:00:06 -0600 > I'm curious... what are your plans here? Will you be keeping OF alive > between kexec()? Will the new kernel get the entire device tree from > fdt, or will it still be talking to OF? How will the fdt fragments as > Andres described above fit into sparc kexec (as opposed to generating > one big tree as in his first option)? On certain sparc64 systems, I have to stop making PROM calls early in the boot right after I fetch the device tree into the kernel. So yes for a kexec() I'll have to pass an fdt or similar to the child kernel. It could be a big linear fdt buffer, or fragments, it really doesn't matter all that much actually. -- To unsubscribe from this list: send the line "unsubscribe sparclinux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
