From: Jon Smirl <jonsmirl@gmail.com>
To: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
Cc: Greg KH <greg@kroah.com>, Andrew Morton <akpm@osdl.org>,
linux-pci@atrey.karlin.mff.cuni.cz, linux-kernel@vger.kernel.org,
Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: Re: [patch 2.6] remove PCI_BRIDGE_CTL_VGA handling from setup-bus.c
Date: Thu, 14 Jul 2005 18:39:43 -0400 [thread overview]
Message-ID: <9e47339105071415392ef2eb2e@mail.gmail.com> (raw)
In-Reply-To: <20050715014611.B613@den.park.msu.ru>
On 7/14/05, Ivan Kokshaysky <ink@jurassic.park.msu.ru> wrote:
> On Thu, Jul 14, 2005 at 10:07:34AM -0400, Jon Smirl wrote:
> > I'm don't think it has ever been working in the 2.6 series. If you are
> > getting rid of it get rid of the #define PCI_BRIDGE_CTL_VGA in pci.h
> > too since this code was the only user.
>
> No. The PCI_BRIDGE_CTL_VGA is not something artificial, it just describes
> some well defined hardware bit in the p2p bridge config header, so anyone
> working on VGA switching API will have to use it.
I had the wrong define, this is the one I was thinking of IORESOURCE_BUS_HAS_VGA
> > This code is part of VGA arbitration which BenH is addressing with a
> > more globally comprehensive patch. Ben's code will probably replace
> > it.
>
> Yes, I've heard Ben is working on this, but I've yet to see the code. ;-)
> Any pointers?
>
> Ivan.
>
--
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2005-07-14 22:43 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
2005-07-14 14:07 ` Jon Smirl
2005-07-14 21:46 ` Ivan Kokshaysky
2005-07-14 22:39 ` Jon Smirl [this message]
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=9e47339105071415392ef2eb2e@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=akpm@osdl.org \
--cc=benh@kernel.crashing.org \
--cc=greg@kroah.com \
--cc=ink@jurassic.park.msu.ru \
--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