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: Tero Kaarlela
Subject: Re: [Qemu-devel] Problems with Prep IDE
Date: Fri, 22 Apr 2005 21:52:42 +0300
User-agent: Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.0.1) Gecko/20020919 IBM Web Browser for OS/2

J. Mayer wrote:

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.

  Ok,

     What I have made now:

        1. Changed vendor id of PREP Pci bridge from 1011 to 1014 (ibm)
2. Tried booting and noticed that Bootloader did: pci_config_read: PCI Bridge address:10 value: 0xffffffff
        3. Found out that address 10 should have base adress in it.
        4. modified this with:

                       d->config[0x10] = 0x08
                       d->config[0x10] = 0x00
                       d->config[0x10] = 0x00
                       d->config[0x10] = 0xF0
              to be 0xF0000008

   Is this ok?(I just figured it out somehow)

      Now bootloader gives me:

       dma:command 0x24 not supported
       dma:command 0x25 not supported

  Just figuring out what these commands are....


Tero





reply via email to

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