All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tero Kaarlela <turo.kaarlela@co.inet.fi>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Problems with Prep IDE
Date: Fri, 22 Apr 2005 21:52:42 +0300	[thread overview]
Message-ID: <426947FA.40007@co.inet.fi> (raw)
In-Reply-To: 1113608514.11980.55.camel@rapid

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	other threads:[~2005-04-22 18:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-15 20:58 [Qemu-devel] Problems with Prep IDE Tero Kaarlela
2005-04-15 23:41 ` J. Mayer
2005-04-22 18:52   ` Tero Kaarlela [this message]
2005-04-22 18:59     ` Tero Kaarlela
2005-04-22 20:54       ` [Qemu-devel] Problems with Prep IDE more info Tero Kaarlela
2005-04-22 22:59         ` Hetz Ben Hamo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=426947FA.40007@co.inet.fi \
    --to=turo.kaarlela@co.inet.fi \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.