From: Grant Grundler <grundler@parisc-linux.org>
To: Jesse Barnes <jbarnes@sgi.com>
Cc: Grant Grundler <grundler@parisc-linux.org>,
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 13:12:00 -0700 [thread overview]
Message-ID: <20050128201200.GE32135@colo.lackof.org> (raw)
In-Reply-To: <200501281141.16450.jbarnes@sgi.com>
On Fri, Jan 28, 2005 at 11:41:16AM -0800, Jesse Barnes wrote:
> Yeah, I think I understand. We could probably do the same thing on sn2
> as you do on parisc--add a 'segment 0' offset to the port so that it's routed
> correctly. I think that's a little less flexible than adding a new resource
> though, since it makes it harder for drivers to support more than one device
> or devices on non-segment 0 busses.
To be clear, the parisc code defines this in include/asm-parisc/pci.h:
#define HBA_PORT_SPACE_BITS 16
#define PCI_PORT_HBA(a) ((a) >> HBA_PORT_SPACE_BITS)
and PCI_PORT_HBA gets used in arch/parisc/kernel/pci.c.
Offhand, I don't know if ia64 has the equivalent.
But it sounds like it might need it.
grant
next prev parent reply other threads:[~2005-01-28 20:14 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
2005-01-28 19:33 ` Grant Grundler
2005-01-28 19:41 ` Jesse Barnes
2005-01-28 20:12 ` Grant Grundler [this message]
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=20050128201200.GE32135@colo.lackof.org \
--to=grundler@parisc-linux.org \
--cc=greg@kroah.com \
--cc=jbarnes@sgi.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox