From: Jesse Barnes <jbarnes@sgi.com>
To: Grant Grundler <grundler@parisc-linux.org>
Cc: Jon Smirl <jonsmirl@gmail.com>, Greg KH <greg@kroah.com>,
Russell King <rmk+lkml@arm.linux.org.uk>,
Jeff Garzik <jgarzik@pobox.com>, Matthew Wilcox <matthew@wil.cx>,
linux-pci@atrey.karlin.mff.cuni.cz,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: Fwd: Patch to control VGA bus routing and active VGA device.
Date: Fri, 28 Jan 2005 10:41:41 -0800 [thread overview]
Message-ID: <200501281041.42016.jbarnes@sgi.com> (raw)
In-Reply-To: <20050128173222.GC30791@colo.lackof.org>
On Friday, January 28, 2005 9:32 am, Grant Grundler wrote:
> On Thu, Jan 27, 2005 at 08:28:43AM -0800, Jesse Barnes wrote:
> > But then again,
> > I suppose if a platform supports more than one legacy I/O space,
>
> Eh?! there can only be *one* legacy I/O space.
> We can support multipl IO port spaces, but only one can be the "legacy".
What do you mean? If you define legacy I/O space to be
0x0000000000000000-0x000000000000ffff, then yes of course you're right. But
if you mean being able to access legacy ports at all, then no. On SGI
machines, there's a per-bus base address that can be used as the base for
port I/O, which is what I was getting at.
> Moving the VGA device can only function within that legacy space
> the way the code is written now (using hard coded addresses).
> If it is intended to work with multiple IO Port address spaces,
> then it needs to use the pci_dev->resource[] and mangle that appropriately.
There is no resource for some of the I/O port space that cards respond to. I
can set the I/O BAR of my VGA card to 0x400 and it'll still respond to
accesses at 0x3bc for example. That's what I mean by legacy space--space
that cards respond to but don't report in their PCI resources.
Jesse
next prev parent reply other threads:[~2005-01-28 18:47 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-18 3:43 Patch to control VGA bus routing and active VGA device Jon Smirl
2005-01-18 17:46 ` Jesse Barnes
2005-01-18 19:38 ` H. Peter Anvin
2005-01-18 21:06 ` Jesse Barnes
2005-01-22 19:04 ` Jon Smirl
2005-01-24 17:25 ` Jesse Barnes
2005-01-24 17:53 ` Jesse Barnes
[not found] ` <41ED3BD2.1090105@pobox.com>
[not found] ` <9e473391050122083822a7f81c@mail.gmail.com>
[not found] ` <200501240847.51208.jbarnes@sgi.com>
[not found] ` <20050124175131.GM31455@parcelfarce.linux.theplanet.co.uk>
2005-01-24 19:17 ` Fwd: " Jon Smirl
2005-01-24 19:42 ` Jeff Garzik
2005-01-24 19:55 ` Russell King
2005-01-24 23:11 ` Jon Smirl
2005-01-25 4:24 ` Greg KH
2005-01-27 9:59 ` Jon Smirl
2005-01-27 16:28 ` Jesse Barnes
2005-01-28 17:32 ` Grant Grundler
2005-01-28 18:36 ` Jon Smirl
2005-01-28 19:15 ` Grant Grundler
2005-01-28 19:26 ` Jon Smirl
2005-01-28 19:34 ` Grant Grundler
2005-01-28 18:41 ` Jesse Barnes [this message]
2005-01-28 19:33 ` Grant Grundler
2005-01-28 19:41 ` Jesse Barnes
2005-01-28 20:12 ` Grant Grundler
2005-01-28 20:00 ` Matthew Wilcox
2005-01-28 20:07 ` Russell King
2005-01-31 16:01 ` Alan Cox
2005-02-01 6:38 ` Greg KH
2005-02-01 16:24 ` Jon Smirl
2005-01-30 7:51 ` Jon Smirl
2005-01-24 20:14 ` Matthew Wilcox
2005-01-24 20:22 ` Matthew Wilcox
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=200501281041.42016.jbarnes@sgi.com \
--to=jbarnes@sgi.com \
--cc=greg@kroah.com \
--cc=grundler@parisc-linux.org \
--cc=jgarzik@pobox.com \
--cc=jonsmirl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=matthew@wil.cx \
--cc=rmk+lkml@arm.linux.org.uk \
/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.