qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: Kevin O'Connor <kevin@koconnor.net>
Cc: seabios@seabios.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] pci vga: Support VGA behind bridges
Date: Fri, 01 Mar 2013 09:33:42 -0700	[thread overview]
Message-ID: <1362155622.2532.287.camel@bling.home> (raw)
In-Reply-To: <20130301040332.GA31112@morn.localdomain>

On Thu, 2013-02-28 at 23:03 -0500, Kevin O'Connor wrote:
> On Thu, Feb 28, 2013 at 10:52:49AM -0700, Alex Williamson wrote:
> > We currently expect to find VGA devices on the root bus but we will
> > also support them below bridges iff the VGA routing across the bridges
> > is pre-configured.  This patch maintains that behavior, but also
> > enables SeaBIOS to enable VGA routing to the first VGA class device it
> > finds when there is no preconfigured device.  This allows us to
> > support VGA devices behind root ports and bridges without special
> > setup from QEMU.
> [...]
> > --- a/src/optionroms.c
> > +++ b/src/optionroms.c
> > @@ -439,13 +439,47 @@ vgarom_setup(void)
> 
> I don't think that optionroms.c is the right place for this logic.  On
> coreboot, Xen, and CSM, SeaBIOS shouldn't be touching the PCI config.
> It's only QEMU that would need this logic, so something like pciinit.c
> is where this logic should go.

Ok, I can look at finding a spot for it in pciinit.  Note though that
there's nothing QEMU specific about this, if other platforms are already
enabling a route to a VGA device, there's no change.  If something
sneaks through without a VGA device enabled, this should generically
enable the first device.  Thanks,

Alex

           reply	other threads:[~2013-03-01 16:33 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20130301040332.GA31112@morn.localdomain>]

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=1362155622.2532.287.camel@bling.home \
    --to=alex.williamson@redhat.com \
    --cc=kevin@koconnor.net \
    --cc=qemu-devel@nongnu.org \
    --cc=seabios@seabios.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).