On 13.09.2011, at 11:00, Jan Kiszka wrote:
> On 2011-09-13 10:40, Alexander Graf wrote:
>> Btw, it still tries to execute invalid code even with your patch. #if 0'ing
>> out the memory region updates at least get the guest booting for me. Btw, to
>> get it working you also need a patch for the interrupt controller (another
>> breakage thanks to memory api).
>>
>> diff --git a/hw/heathrow_pic.c b/hw/heathrow_pic.c
>> index 51996ab..16f48d1 100644
>> --- a/hw/heathrow_pic.c
>> +++ b/hw/heathrow_pic.c
>> @@ -126,7 +126,7 @@ static uint64_t pic_read(void *opaque,
>> target_phys_addr_t addr,
>> static const MemoryRegionOps heathrow_pic_ops = {
>> .read = pic_read,
>> .write = pic_write,
>> - .endianness = DEVICE_NATIVE_ENDIAN,
>> + .endianness = DEVICE_LITTLE_ENDIAN,
>> };
>>
>> static void heathrow_pic_set_irq(void *opaque, int num, int level)
>>
>
> With out without this fix, with or without active chain-4 optimization,
> I just get an empty yellow screen when firing up qemu-system-ppc (also
> when using the Debian ISO). Do I need to specify a specific machine type?
Ugh. No, you only need this patch:
[PATCH] PPC: Fix via-cuda memory registration
which fixes another recently introduced regression :)
Alex
