In message <[EMAIL PROTECTED]> you wrote: > On Wed, Dec 13, 2006 at 10:35:08AM +0900, Horms wrote: > > On Fri, Dec 08, 2006 at 10:32:15AM +1100, Michael Neuling wrote: > > > > >Is there a kexec-tools patch too? How does second kernel know about > > > > >the location of the first kernel's initrd to be reused? > > > > > > > > > > > > > > kexec-tools has to be modified to pass the first kernel initrd. On > > > > powerpc, initrd locations are exported using device-tree. At present, > > > > kexec-tool ignores the first kernel initrd property values and creates > > > > new initrd properties if the user passes '--initrd' option to the kexec > > > > command. So, will be an issue unless first kernel device-tree is passed > > > > as buffer. > > > > > > We've been using the --devicetreeblob kexec-tools option available for > > > POWERPC. This enables you to setup the device tree (and hence, the > > > initrd points) as you like. > > > > > > I'm happy to put together a patch for kexec-tools. > > > > Please do. And please cc me on a copy that applies against kexec-tools-test ing. > > > > > Unfortunately this > > > is arch specific. A quick look through the x86, ia64, s390 and ppc64 > > > code shows the --initrd option for all these just reads the specified > > > initrd file, pushes it out to memory and uses the base and size pointers > > > to setup the next boot. We'd obviously just skip to the last stage. > > > > > > So what's the kexec-tools option called? --initrd-location <base> <size> ? > > > > That sounds fine to me. I think its ok to make it arch specific for > > starters and then move it out to generic code later. That said, if > > you're feeling particularly entergetic, feel free to do the generic > > stuff now and just add null stubs for the other architectures (does > > that makes sense?). > > Did anything ever come of this?
Not yet, but it's on my todo list. Mikey _______________________________________________ fastboot mailing list [email protected] https://lists.osdl.org/mailman/listinfo/fastboot
