On Sat, 2009-06-06 at 16:13 +0100, David Woodhouse wrote:
On Sat, 2009-06-06 at 15:29 +0100, David Woodhouse wrote:
> You could also try using kexec -- that should help eliminate yaboot
> bugs too.
Booting with kexec (after rebuilding it because for some reason we're
shipping a ppc32-capable kexec again, gr)
I needed this too, btw:
--- kexec/arch/ppc64/kexec-elf-rel-ppc64.c.orig 2009-06-06 16:27:10.000000000 +0100
+++ kexec/arch/ppc64/kexec-elf-rel-ppc64.c 2009-06-06 16:08:37.000000000 +0100
@@ -88,6 +88,11 @@ void machine_apply_elf_rel(struct mem_eh
| (value & 0x03fffffc);
break;
+ case R_PPC64_REL32:
+ /* Convert value to relative */
+ *(uint32_t *)location = value - address;
+ break;
+
case R_PPC64_ADDR16_LO:
*(uint16_t *)location = value & 0xffff;
break;
I blame yaboot...
I note that yaboot doesn't actually do any relocations when it loads the
relocatable kernel, while kexec does. Should it?
--
David Woodhouse Open Source Technology Centre
David.Woodhouse(a)intel.com Intel Corporation