qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] Problems with Prep IDE


From: J. Mayer
Subject: Re: [Qemu-devel] Problems with Prep IDE
Date: Sat, 16 Apr 2005 01:41:54 +0200

On Fri, 2005-04-15 at 23:58 +0300, Tero Kaarlela wrote:
> Hi,
> 
>      I am still trying to boot OS/2 PPC edition with Qemu. Non-contiguos 
> IO map & no support for Little-endian have been solved now thanks to J. 
> Mayer who sent me patches to work these out. Now bootloader gives me 
> following message:
> 
> IBM Microkernel bootloader press enter for manual boot(enter)
> 
> and I have following boot options to choose from:
> 
> cdrom
> hd
> 
> if I try to use either one of these Qemu gives me
> 
> outl: port= 0x0cf8   data=0x80006000
> inl: port= 0x0cfc
> (Bootloader continues with)
> Invalid PCI configuration
> Device initializion failed
> 
> Any ideas why is this?

There are two problems here:
first, the PREP PCI controller does not map its legacy ISA IO ports.
This is a bug.
But fixing this point is not sufficient to make the loader happy:
it tries to access the PCI device 0x60 (96) which does not exists. Then,
I think the lack of devices description in Open Hack'Ware residual data
can be a good suspect for this. Or it can be that real PREP machine
always have the IDE (or SCSI !) controller mapped as PCI device 0x60,
but I'm very suspicious about this.

> And I have also another note I have made:
> 
> Boot loader catches a bug if I try to use any other machine model(in 
> bootinfos.c) than IBM PPS Model 6050.
> 
> If I give I 6070 Qemu catches a bug. I have done some researching and 
> 6070 & all other models accepted by this bootloader have "thing" called 
> PCI_ACCESS_DEVICE. 6050 does not have this might this be the reason why 
> 6050 is the only machine of these that boots? And if someone knows what 
> is this thing pls tell me too :)

There still have two possibilities. The first would be that ther's a bug
in the info given by Open Hack'Ware then OS/2 loader gets confused then
crashes. The second is still the lack of hardware description in Open
Hack'Ware residual data.
You may try to hardcode a simple hardware description (just PCI with
IDE, for example) there...

-- 
J. Mayer <address@hidden>
Never organized





reply via email to

[Prev in Thread] Current Thread [Next in Thread]