From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Michael Ellerman <michael@ellerman.id.au>
Cc: sparclinux@vger.kernel.org,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
klebers <klebers@linux.vnet.ibm.com>,
Brian King <brking@linux.vnet.ibm.com>,
Lucas Kannebley Tavares <lucaskt@linux.vnet.ibm.com>,
Bjorn Helgaas <bhelgaas@google.com>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH 3/3] powerpc: Set default VGA device
Date: Mon, 08 Apr 2013 08:39:01 +0200 [thread overview]
Message-ID: <1365403141.31207.16.camel@pasglop> (raw)
In-Reply-To: <20130408052124.GA9550@concordia>
On Mon, 2013-04-08 at 15:21 +1000, Michael Ellerman wrote:
> Looking at x86, ia64 and ours, there's a fair bit of difference.
>
> x86/ia64 both walk up the parents checking PCI_BRIDGE_CTL_VGA, which
> powerpc doesn't (though maybe it should?).
Unclear for several reasons.
That bit indicates that the bridge forwards the hard coded legacy VGA IO
ports and memory aperture. These are not necessary to get modern video
cards going. Only if legacy modes are used.
On x86, that tends to be the case (is it always even with EFI
nowadays ?).
On other architectures that is not necessarily the case. The firmware
can (and will) initialize the card using MMIO entirely and even if
possible disabling the legacy stuff, which means that turning those bits
on in the bridge is also unnecessary.
In fact, on such setups, the isn't really a concept of a "primary" video
card to begin with.
On the other hand, that also means that a video card initialized like
that is pretty much out of the grasp of the vga arbiter which has no
effect on it either.
Also be careful that while it may be relevant on x86, the VGA fwd bit is
not on the PCIe root complex on IBM machines.
Finally, P8 has no IO space at all...
> x86/ia64 set IORESOURCE_ROM_SHADOW, which powerpc doesn't.
>
> ia64 doesn't call vga_set_default_device(), x86 and powerpc do.
>
> So we'll merge this and maybe someone can tease out the common bits, but
> personally I don't see that there's an obvious chunk of generic logic.
Cheers,
Ben.
prev parent reply other threads:[~2013-04-08 6:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-04 21:58 [PATCH 3/3] powerpc: Set default VGA device Brian King
2013-04-05 6:52 ` Michael Ellerman
2013-04-05 15:38 ` Brian King
2013-04-05 20:24 ` Bjorn Helgaas
2013-04-08 5:21 ` Michael Ellerman
2013-04-08 6:39 ` Benjamin Herrenschmidt [this message]
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=1365403141.31207.16.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=bhelgaas@google.com \
--cc=brking@linux.vnet.ibm.com \
--cc=klebers@linux.vnet.ibm.com \
--cc=linux-pci@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lucaskt@linux.vnet.ibm.com \
--cc=michael@ellerman.id.au \
--cc=sparclinux@vger.kernel.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).