> -Original Message-
> From: qemu-devel-bounces+mihai.caraman=freescale@nongnu.org
> [mailto:qemu-devel-bounces+mihai.caraman=freescale@nongnu.org] On
> Behalf Of Alexander Graf
> Sent: Friday, September 05, 2014 12:08 PM
> To: Purcareata Bogdan-B43198; qemu-...@nongnu.org
> Cc: qem
> -Original Message-
> From: qemu-devel-bounces+mihai.caraman=freescale@nongnu.org
> [mailto:qemu-devel-bounces+mihai.caraman=freescale@nongnu.org] On
> Behalf Of Alexander Graf
> Sent: Friday, September 05, 2014 12:08 PM
> To: Purcareata Bogdan-B43198; qemu-...@nongnu.org
> Cc: qem
Please ignore this mail.
> -Original Message-
> From: Peter Maydell [mailto:peter.mayd...@linaro.org]
> Sent: Wednesday, December 11, 2013 4:07 PM
> To: Alexander Graf
> Cc: Paolo Bonzini; Vlad Bogdan-BOGVLAD1; QEMU Developers; qemu-
> p...@nongnu.org; Sethi Varun-B16395; Wood Scott-B07421; Caraman Mihai
> Claudiu-
> On 11.12.2013, at 16:15, Alexander Graf < ag...@suse.de > wrote:
>
> Well, this really is a simplified view of the world.
>
> On real hardware the system boots up with caches disabled. Firmware is
> then responsible for enabling caches and flushing things as it goes.
> Firmware loads the kernel
On 11.12.2013, at 15:07, Peter Maydell wrote:
> But these are (emulated) ROMs, not an emulated bootloader.
> They ought to work like actual ROMs: QEMU as the emulator
> of the system/devices provides the contents of physical address
> space; KVM as the emulator of the CPU provides a CPU which
> do
