From: Alex Williamson <alex.williamson@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org, mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH v4 2/2] pci: Teach PCI Bridges about VGA routing
Date: Sun, 03 Mar 2013 18:52:45 -0700 [thread overview]
Message-ID: <1362361965.2489.2.camel@bling.home> (raw)
In-Reply-To: <CAFEAcA-it7SJDgTh09fUiaVTbEig=WBsbXh=jm-+AghC+DDCkA@mail.gmail.com>
On Mon, 2013-03-04 at 09:39 +0800, Peter Maydell wrote:
> On 4 March 2013 01:21, Alex Williamson <alex.williamson@redhat.com> wrote:
> > --- a/hw/pci/pcie_port.c
> > +++ b/hw/pci/pcie_port.c
> > @@ -28,10 +28,12 @@ void pcie_port_init_reg(PCIDevice *d)
> > pci_set_word(d->config + PCI_SEC_STATUS, 0);
> >
> > /* Unlike conventional pci bridge, some bits are hardwired to 0. */
> > +#define PCI_BRIDGE_CTL_VGA_16BIT 0x10 /* VGA 16-bit decode */
>
> Shouldn't this #define be in pci_regs.h with the other PCI_BRIDGE_CTL_*
> constants?
See the existing define in pci.c. pci_regs.h is derived from the Linux
kernel header, which is not 100% complete. Ideally it would contain
this, but it doesn't currently so I'm following the existing example.
Thanks,
Alex
> > pci_set_word(d->wmask + PCI_BRIDGE_CONTROL,
> > PCI_BRIDGE_CTL_PARITY |
> > PCI_BRIDGE_CTL_ISA |
> > PCI_BRIDGE_CTL_VGA |
> > + PCI_BRIDGE_CTL_VGA_16BIT | /* Req, but no alias support yet */
> > PCI_BRIDGE_CTL_SERR |
> > PCI_BRIDGE_CTL_BUS_RESET);
> > }
>
> thanks
> -- PMM
next prev parent reply other threads:[~2013-03-04 1:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-03 17:21 [Qemu-devel] [PATCH v4 0/2] PCI learns about VGA Alex Williamson
2013-03-03 17:21 ` [Qemu-devel] [PATCH v4 1/2] pci: Add PCI VGA helpers Alex Williamson
2013-03-03 17:21 ` [Qemu-devel] [PATCH v4 2/2] pci: Teach PCI Bridges about VGA routing Alex Williamson
2013-03-04 1:39 ` Peter Maydell
2013-03-04 1:52 ` Alex Williamson [this message]
2013-03-04 9:09 ` Michael S. Tsirkin
2013-03-04 9:15 ` [Qemu-devel] [PATCH v4 0/2] PCI learns about VGA Michael S. Tsirkin
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=1362361965.2489.2.camel@bling.home \
--to=alex.williamson@redhat.com \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--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.