On Thu, Aug 5, 2010 at 7:39 PM, Liu Yu-B13201 <B13201@xxxxxxxxxxxxx> wrote: > > >> -----Original Message----- >> From: kvm-ppc-owner@xxxxxxxxxxxxxxx >> [mailto:kvm-ppc-owner@xxxxxxxxxxxxxxx] On Behalf Of Hollis Blanchard >> Sent: Thursday, August 05, 2010 8:22 AM >> To: qemu-devel@xxxxxxxxxx >> Cc: kvm-ppc@xxxxxxxxxxxxxxx >> Subject: [PATCH 4/4] ppc4xx: load Bamboo kernel, initrd, and >> fdt at fixed addresses >> >> We can't use the return value of load_uimage() for the kernel >> because it >> can't account for BSS size, and the PowerPC kernel does not relocate >> blobs before zeroing BSS. >> >> Instead, we now load at the fixed addresses chosen by u-boot >> (the normal >> firmware for the board). >> > > What will us do if the uImage become bigger and fixed size is not > enough? That was my question to Edgar, which was not answered. In u-boot, one would change some environment variables. With this code in qemu, the only recourse would be to edit ppc440_bamboo.c and rebuild. Perhaps in the future we can do something more sophisticated by specifying load addresses in a qemu device tree, but I don't understand that stuff enough to know if that is an intended use. -Hollis -- To unsubscribe from this list: send the line "unsubscribe kvm-ppc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html