On 16 August 2014 10:50, Piotr Król wrote:
> On Fri, Aug 15, 2014 at 11:54:55PM +0100, Peter Maydell wrote:
>> I'm not looking for advocacy, just for an explanation of what it's
>> doing, and in particular whether anybody's ever tested this on real
>> hardware. (Running guest code only on QEMU is
On Fri, Aug 15, 2014 at 11:54:55PM +0100, Peter Maydell wrote:
> I'm not looking for advocacy, just for an explanation of what it's
> doing, and in particular whether anybody's ever tested this on real
> hardware. (Running guest code only on QEMU is a recipe for bugs,
> because our emulation is oft
On 15 August 2014 19:02, Piotr Król wrote:
> On Fri, Aug 15, 2014 at 05:10:04PM +0100, Peter Maydell wrote:
>> For your stack issues, it looks like your code is trying to
>> use the area which is the flash as the stack. Since flash
>> isn't writeable, we ignore the writes and it's not very
>> usef
On Fri, Aug 15, 2014 at 05:10:04PM +0100, Peter Maydell wrote:
> For your stack issues, it looks like your code is trying to
> use the area which is the flash as the stack. Since flash
> isn't writeable, we ignore the writes and it's not very
> useful for stack. It looks like your code is assuming
On 15 August 2014 11:07, Piotr Król wrote:
> Hi all,
> I'm trying to boot latest coreboot on qemu-system-arm (-M vexpress-a9).
> I compiled qemu arm-softmmu from source (latest code) and trying to boot
> with:
>
> qemu-system-arm -M vexpress-a9 -m 1024M -nographic -bios build/coreboot.rom
>
> Firs
Hi all,
I'm trying to boot latest coreboot on qemu-system-arm (-M vexpress-a9).
I compiled qemu arm-softmmu from source (latest code) and trying to boot
with:
qemu-system-arm -M vexpress-a9 -m 1024M -nographic -bios build/coreboot.rom
First of all mtree looks strange because there are two aliases
