On Tue, Mar 1, 2016 at 4:07 PM, Peter Maydell wrote:
> On 1 March 2016 at 23:56, Alistair Francis
> wrote:
>> On Fri, Feb 26, 2016 at 8:22 AM, Peter Maydell
>> wrote:
>
>>> Writing directly to cpu->as is not very generic. In particular,
>>> how should this interact with TrustZone, where you mi
On 1 March 2016 at 23:56, Alistair Francis wrote:
> On Fri, Feb 26, 2016 at 8:22 AM, Peter Maydell
> wrote:
>> Writing directly to cpu->as is not very generic. In particular,
>> how should this interact with TrustZone, where you might want to
>> write the image to the Secure address space?
>
>
On Fri, Feb 26, 2016 at 8:22 AM, Peter Maydell wrote:
> On 19 February 2016 at 20:40, Alistair Francis
> wrote:
>> Add a generic loader to QEMU which can be used to load images or set
>> memory values.
>
> I'm not inherently opposed to this (it seems like a nice way
> to deal with the desire to l
On 19 February 2016 at 20:40, Alistair Francis
wrote:
> Add a generic loader to QEMU which can be used to load images or set
> memory values.
I'm not inherently opposed to this (it seems like a nice way
to deal with the desire to load arbitrary images), but it feels
a bit half-baked at the moment
Add a generic loader to QEMU which can be used to load images or set
memory values.
This only supports ARM architectures at the moment.
Signed-off-by: Alistair Francis
---
V3:
- Pass the ram_size to load_image_targphys()
V2:
- Add maintainers entry
- Perform bounds checking
- Register and un
