qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: BALATON Zoltan <balaton@eik.bme.hu>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Multiple pci buses
Date: Sat, 15 Mar 2014 22:21:31 +0100 (CET)	[thread overview]
Message-ID: <alpine.LMD.2.02.1403152213250.5373@jedlik.phy.bme.hu> (raw)

Hello,

I'm trying to change hw/ppc/mac_newworld.c and hw/pci-host/uninorth.c to 
bring the mac99 machine type closer to what's seen in these dumps:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=604134
http://nandra.segv.jp/NetBSD/G4.dump-device-tree.txt
http://raveland.org/ports/eeprom.txt
http://mail-index.netbsd.org/port-macppc/2007/10/24/0000.html

This machine seems to have 3 pci busses but the third is not important 
just the other two:

ff8721c0: /pci@f0000000
ff898cd0:   /uni-north-agp@b
ff898f40:   /ATY,Rage128Ps@10
ff873268: /pci@f2000000
ff8742d8:   /pci-bridge@d
ff876368:     /mac-io@7

The first is actually an AGP bus with the onboard graphics card and the 
second is where other devices are. It would be enough to create an empty 
bus without the AGP graphics card for now and have the devices on the 
second bus. The pci_pmac_init function in uninorth.c seems to have some 
commented out code to try to model this but that does not work. Can 
someone who understands this better please explain what should be done to 
model the above? How to create two pci buses and connect them to separate 
memory regions?

Thank you,
BALATON Zoltan

             reply	other threads:[~2014-03-15 21:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-15 21:21 BALATON Zoltan [this message]
2014-03-16 17:06 ` [Qemu-devel] Multiple pci buses BALATON Zoltan
2014-03-17  2:09 ` Alexey Kardashevskiy
2014-03-17 16:51 ` Andreas Färber
2014-03-17 22:14   ` BALATON Zoltan
2014-03-19 22:36     ` Andreas Färber
2014-03-20  9:42       ` BALATON Zoltan

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=alpine.LMD.2.02.1403152213250.5373@jedlik.phy.bme.hu \
    --to=balaton@eik.bme.hu \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).