From: "Michael S. Tsirkin" <mst@redhat.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
qemu-devel@nongnu.org, Anthony Liguori <anthony@codemonkey.ws>
Subject: Re: [Qemu-devel] [PATCH] pci: fix bridge IO/BASE
Date: Tue, 6 Mar 2012 15:42:10 +0200 [thread overview]
Message-ID: <20120306134209.GD12096@redhat.com> (raw)
In-Reply-To: <CAAu8pHtQw1VHLTWFoomacmnchbnV=Vez0_fhi9foTCAxPtJuRA@mail.gmail.com>
On Mon, Mar 05, 2012 at 06:34:51PM +0000, Blue Swirl wrote:
> On Sun, Mar 4, 2012 at 22:29, Michael S. Tsirkin <mst@redhat.com> wrote:
> > On Sun, Mar 04, 2012 at 09:54:02PM +0000, Blue Swirl wrote:
> >> >> 19.3.1.10 tells that the header type is 0, as you noted too. Still,
> >> >> the register layout matches bridge spec instead, for example there are
> >> >> bus number registers in place of BAR 2.
> >> >
> >> > Sorry I don't see this in 19.3.1
> >> > Where are these registers documented?
> >> > In my spec all registers from 0x10 on are greyed out which
> >> > it says above means 'not implemented'?
> >> > My spec also says 'Base Address' for 0x10 - 0x27.
> >> >
> >> > I see bus number and subordinate bus number
> >> > registers at 0x40 and 0x41, this is outside
> >> > the configuration header. The spec also says
> >> > they are unused.
> >>
> >> Oh, I somehow read that they were in bridge locations 0x18 and 0x19.
> >> Perhaps the is_bridge property should be removed after OpenBIOS no
> >> longer wants to write to the registers.
> >
> > So we are in agreement then?
> > The device seems to (more or less) go by the spec,
>
> QEMU is correct here as is your original commit. The only change
> (beside bug fixes for the problems you found, thanks) should be for
> is_bridge.
You mean remove is_bridge? Right.
> > but openbios gets confused, apparently by the absence of BARs.
> >
> > Can you try debugging openbios to see what is wrong?
>
> On second thought, I think 32 bit I/O was confusing OpenBIOS, probably
> the host bridge device not so much. PCI handling in OpenBIOS should be
> fixed.
We can make IO 32 bit. Want to try?
Anyway, so I won't revert this in core for now?
> > --
> > MST
next prev parent reply other threads:[~2012-03-06 13: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 [this message]
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
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=20120306134209.GD12096@redhat.com \
--to=mst@redhat.com \
--cc=anthony@codemonkey.ws \
--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 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).