2012/2/9 Paul Brook <paul@codesourcery.com>

> > So here are some of the problems im trying to solve with the bootloader:
> >
> > Smp bootstrap secondary CPUs while loading an elf (currently elfs will be
> > assumed to be not kernels).
> > Change the kernel, initrd and dtb load address on the command line.
> > Use my own SMP secondary bootloop.
> >
> > My intention with this patch was to set myself to do boot
> parameterizations
> > on the command line by just adding them as qdev props to the
> > arm_linux_loader and set them using -device instantiation. E.G. -device
> > arm_boot_loader,initrd_addr=0x10000000. But if I take the approach you
> are
> > suggesting, the for this initrd load address option, I would need to add
> > myself a command line option, fetch that command line option in every arm
> > machine model and then pass it to arm_load_kernel.
>
> No.  You just set/override properties on the device that the machine
> created.
> I thought we already had this, but it looks like the closest we have is
> -global.
>
> Something like "-property /devicepath/propertyname=value".
> This is something we need anyway.  Creating new devices with -device is of
> very limited value if you can't link existing device properties to that new
> device.  Remember that in the new world order we don't have magic
> bus-device,
> everything is done via link properlties.
>
>
Ok, that sounds more workable :). So i would add my initrd_addr property to
the bootloader as a qdev prop as I suggested before, then something like:

qemu-system-arm -M verstailepb -property
/foo/bar/arm_linux_loader.0,initrd_addr=0x10000000

?

Paul
>

Peter