From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
Cc: Greg KH <greg@kroah.com>, Andrew Morton <akpm@osdl.org>,
Jon Smirl <jonsmirl@gmail.com>,
linux-pci@atrey.karlin.mff.cuni.cz, linux-kernel@vger.kernel.org
Subject: Re: [patch 2.6] remove PCI_BRIDGE_CTL_VGA handling from setup-bus.c
Date: Thu, 14 Jul 2005 14:53:27 +0100 [thread overview]
Message-ID: <20050714145327.B7314@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20050714155344.A27478@jurassic.park.msu.ru>; from ink@jurassic.park.msu.ru on Thu, Jul 14, 2005 at 03:53:44PM +0400
On Thu, Jul 14, 2005 at 03:53:44PM +0400, Ivan Kokshaysky wrote:
> The setup-bus code doesn't work correctly for configurations
> with more than one display adapter in the same PCI domain.
> This stuff actually is a leftover of an early 2.4 PCI setup code
> and apparently it stopped working after some "bridge_ctl" changes.
> So the best thing we can do is just to remove it and rely on the fact
> that any firmware *has* to configure VGA port forwarding for the boot
> display device properly.
What happens when there is no firmware?
I'm sure this code would not have been added had there not been a reason
for it. Do we know why it was added?
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
next prev parent reply other threads:[~2005-07-14 13:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-14 11:53 [patch 2.6] remove PCI_BRIDGE_CTL_VGA handling from setup-bus.c Ivan Kokshaysky
2005-07-14 13:27 ` Jon Smirl
2005-07-14 13:53 ` Russell King [this message]
2005-07-14 14:07 ` Jon Smirl
2005-07-14 21:46 ` Ivan Kokshaysky
2005-07-14 22:39 ` Jon Smirl
2005-07-14 23:08 ` Ivan Kokshaysky
2005-07-15 14:33 ` Benjamin Herrenschmidt
2005-07-14 21:44 ` Ivan Kokshaysky
2005-07-14 22:42 ` Jon Smirl
2005-07-14 23:33 ` Ivan Kokshaysky
2005-07-18 19:51 ` Grant Grundler
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=20050714145327.B7314@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=ink@jurassic.park.msu.ru \
--cc=jonsmirl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
/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