From: "Michael S. Tsirkin" <mst@redhat.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
Avi Kivity <avi@redhat.com>,
Anthony Liguori <anthony@codemonkey.ws>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] pci: fix bridge IO/BASE
Date: Sun, 4 Mar 2012 18:42:17 +0200 [thread overview]
Message-ID: <20120304164044.GA15384@redhat.com> (raw)
In-Reply-To: <CAAu8pHu8E13bP35A2=2GLyk6vkkZsNiKrakbibY+K1tgcju-WQ@mail.gmail.com>
On Sun, Mar 04, 2012 at 02:26:13PM +0000, Blue Swirl wrote:
> > It seems to have to do with the host bridge.
> > It's unusual to have host bridge present itself
> > as a pci to pci bridge but there it is.
>
> It looks like the I/O base calculations in OpenBIOS are confused
Where's the source for that, BTW? Have build instructions?
> by
> host bridge, after that all BARs are wrong. OpenBIOS also thinks that
> the host bridge is a device and attempts to configure six BARs instead
> of two.
According to the spec it is a device, so should be ok?
If I just make BAR4 writeable we get past the
bios screen at least.
Maybe openbios gets confused if a device has no BARs?
Do things work for you with the patch below?
All it does is make BAR4 writeable, accesses go nowhere.
diff --git a/hw/apb_pci.c b/hw/apb_pci.c
index 1d25da8..fae841f 100644
--- a/hw/apb_pci.c
+++ b/hw/apb_pci.c
@@ -433,6 +433,7 @@ static int pbm_pci_host_init(PCIDevice *d)
pci_set_word(d->config + PCI_STATUS,
PCI_STATUS_FAST_BACK | PCI_STATUS_66MHZ |
PCI_STATUS_DEVSEL_MEDIUM);
+ pci_set_long(d->wmask + 0x20, 0xfffffff0);
return 0;
}
@@ -444,7 +445,6 @@ static void pbm_pci_host_class_init(ObjectClass *klass, void *data)
k->vendor_id = PCI_VENDOR_ID_SUN;
k->device_id = PCI_DEVICE_ID_SUN_SABRE;
k->class_id = PCI_CLASS_BRIDGE_HOST;
- k->is_bridge = 1;
}
static TypeInfo pbm_pci_host_info = {
--
MST
next prev parent reply other threads:[~2012-03-04 16:42 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-04 9:46 [Qemu-devel] [PATCH] pci: fix bridge IO/BASE Michael S. Tsirkin
2012-03-04 10:27 ` Blue Swirl
2012-03-04 12:21 ` Michael S. Tsirkin
2012-03-04 12:37 ` Blue Swirl
2012-03-04 13:28 ` Michael S. Tsirkin
2012-03-04 13:38 ` Blue Swirl
2012-03-04 14:23 ` Michael S. Tsirkin
2012-03-04 14:35 ` Blue Swirl
2012-03-04 15:22 ` Michael S. Tsirkin
2012-03-04 17:07 ` Blue Swirl
2012-03-04 17:35 ` Michael S. Tsirkin
2012-03-04 19:51 ` Blue Swirl
2012-03-04 20:02 ` Michael S. Tsirkin
2012-03-04 20:32 ` Blue Swirl
2012-03-04 21:28 ` Michael S. Tsirkin
2012-03-04 21:54 ` Blue Swirl
2012-03-04 22:29 ` Michael S. Tsirkin
2012-03-05 18:34 ` Blue Swirl
2012-03-06 13:42 ` Michael S. Tsirkin
2012-03-04 21:56 ` Mark Cave-Ayland
2012-03-04 15:41 ` Michael S. Tsirkin
2012-03-04 13:38 ` Michael S. Tsirkin
2012-03-04 12:28 ` Avi Kivity
2012-03-04 12:38 ` Blue Swirl
2012-03-04 12:41 ` Avi Kivity
2012-03-04 12:46 ` Blue Swirl
2012-03-04 13:21 ` Michael S. Tsirkin
2012-03-04 13:22 ` Michael S. Tsirkin
2012-03-04 13:33 ` Blue Swirl
2012-03-04 14:08 ` Michael S. Tsirkin
2012-03-04 14:26 ` Blue Swirl
2012-03-04 16:42 ` Michael S. Tsirkin [this message]
2012-03-04 17:49 ` Blue Swirl
2012-03-04 18:11 ` Mark Cave-Ayland
2012-03-04 19:27 ` Michael S. Tsirkin
2012-03-04 19:43 ` Michael S. Tsirkin
2012-03-04 19:27 ` Michael S. Tsirkin
2012-03-04 12:33 ` Michael S. Tsirkin
2012-03-04 12:35 ` Avi Kivity
2012-03-04 12:35 ` Michael S. Tsirkin
2012-03-04 12:42 ` Blue Swirl
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=20120304164044.GA15384@redhat.com \
--to=mst@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=blauwirbel@gmail.com \
--cc=mark.cave-ayland@ilande.co.uk \
--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.