On 2 January 2014 05:50, Peter Crosthwaite <peter.crosthwa...@xilinx.com> wrote:
> I'm wondering whether blob loading is actually a reset step not an
> init.
load_image_targphys() uses the rom blob loader code from hw/core/loader.c,
which already supports reloading the blob on machine reset if necessary.
That raises some more general design questions:
* how is this expected to interact with rom blob loading, -machine firmware=,
etc? What are the guidelines for when to use one or the other? Should
this be rolled into the rom blob code rather than being a bolt-on extra?
* I'm unconvinced by the general approach of having a device with an
address property
* would it be useful if the rom blob loading was extended/reworked so that
you could load a rom blob into a MemoryRegion? We want that for
the SPARC TCX ROM blobs as well; maybe it would help here too,
though I haven't thought much about it.
thanks
-- PMM
