* [Qemu-devel] PPC PReP PCI host bridge
@ 2005-02-14 17:40 Thayne Harbaugh
2005-02-14 22:21 ` J. Mayer
0 siblings, 1 reply; 2+ messages in thread
From: Thayne Harbaugh @ 2005-02-14 17:40 UTC (permalink / raw)
To: qemu-devel
I previously sent a patch to add a PCI host bridge to PPC PReP - it
hasn't been applied. Currently, PReP lacks a PCI host bridge and only
has a PCI to PCI bridge. Without a host bridge, PReP doesn't work
correctly. I'm wondering when a correct host bridge, either the one I
submitted or another one, will be added? I'd like to know so that
OpenHackWare can be configured to recognize it.
-------- Forwarded Message --------
> From: Thayne Harbaugh <thayne@realmsys.com>
> Index: qemu-0.6.1/hw/pci.c
> ===================================================================
> --- qemu-0.6.1/hw/pci.c (.../qemu-0.6.1) (revision 7)
> +++ qemu-0.6.1/hw/pci.c (.../external/qemu-0.6.1) (working copy)
> @@ -698,10 +698,25 @@
> PPC_PCIIO_write, s);
> cpu_register_physical_memory(0x80800000, 0x00400000, PPC_io_memory);
>
> - d = pci_register_device(s, "PREP PCI Bridge", sizeof(PCIDevice), 0,
> - NULL, NULL);
> + /* PCI host bridge */
> + d = pci_register_device(s, "PREP Host Bridge - Motorola Raven", sizeof(PCIDevice),
> + 0, NULL, NULL);
> + d->config[0x00] = 0x57; // vendor_id : Apple
> + d->config[0x01] = 0x10;
> + d->config[0x02] = 0x01; // device_id
> + d->config[0x03] = 0x48;
> + d->config[0x08] = 0x00; // revision
> + d->config[0x0A] = 0x00; // class_sub = pci host
> + d->config[0x0B] = 0x06; // class_base = PCI_bridge
> + d->config[0x0C] = 0x08; // cache_line_size
> + d->config[0x0D] = 0x10; // latency_timer
> + d->config[0x0E] = 0x00; // header_type
> + d->config[0x34] = 0x00; // capabilities_pointer
>
> - /* XXX: put correct IDs */
> + /* PCI to PCI bridge */
> + d = pci_register_device(s, "PREP PCI Bridge - Digital 21154", sizeof(PCIDevice),
> + 0xa0 << 3, NULL, NULL);
> + /* same values as PearPC - check this */
> d->config[0x00] = 0x11; // vendor_id
> d->config[0x01] = 0x10;
> d->config[0x02] = 0x26; // device_id
> @@ -710,6 +725,7 @@
> d->config[0x0a] = 0x04; // class_sub = pci2pci
> d->config[0x0b] = 0x06; // class_base = PCI_bridge
> d->config[0x0e] = 0x01; // header_type
> +
> return s;
> }
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [Qemu-devel] PPC PReP PCI host bridge
2005-02-14 17:40 [Qemu-devel] PPC PReP PCI host bridge Thayne Harbaugh
@ 2005-02-14 22:21 ` J. Mayer
0 siblings, 0 replies; 2+ messages in thread
From: J. Mayer @ 2005-02-14 22:21 UTC (permalink / raw)
To: qemu-devel
On Mon, 2005-02-14 at 18:40, Thayne Harbaugh wrote:
> I previously sent a patch to add a PCI host bridge to PPC PReP - it
> hasn't been applied. Currently, PReP lacks a PCI host bridge and only
> has a PCI to PCI bridge. Without a host bridge, PReP doesn't work
> correctly.
You're correct saying that the PCI configuration is not correct,
compared to a real PREP machine, but what OS did you try that does not
run with current configuration ? As Linux (at least 2.4) does run well
with this configuration, then I'd like to know what other OSes you tried
and even more which ones you did boot succesfully !
> I'm wondering when a correct host bridge, either the one I
> submitted or another one, will be added? I'd like to know so that
> OpenHackWare can be configured to recognize it.
I added the support for this bridge in the latest snapshot I sent you
(0.4-pre1c)
which is now also available here:
<http://perso.magic.fr/l_indien/OpenHackWare/0.4-pre1/OpenHackWare_svn-0.4-pre1c.tar.bz2>
[...]
--
J. Mayer <l_indien@magic.fr>
Never organized
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2005-02-14 22:59 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-02-14 17:40 [Qemu-devel] PPC PReP PCI host bridge Thayne Harbaugh
2005-02-14 22:21 ` J. Mayer
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).