> ROM images are in form of binary blobs with no location information,
> they must be loaded to a known address. For boot ROMs, the address
> range would cover CPU hard reset entry vector.
So, for a BIOS or boot ROM that has been stripped, the board needs to
be hard-coded to not just load the imag
On Mon, Apr 2, 2012 at 22:57, Brian Vandenberg
wrote:
> I'm attempting to familiarize myself with the APIs used to add
> support for boards in qemu, and I have a few questions.
>
> * How does using load_elf differ from load_image_targphys?
>
> As an example, many of the boards I've looked at hav
I'm attempting to familiarize myself with the APIs used to add
support for boards in qemu, and I have a few questions.
* How does using load_elf differ from load_image_targphys?
As an example, many of the boards I've looked at have a hard-coded
entrypoint. In mpc8455, it looks as though it d
