From: Jesse Barnes <jbarnes@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] [PATCH] 1/4 multi-ioport space support for 2.5
Date: Fri, 25 Apr 2003 17:18:39 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590723705609@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590723705599@msgid-missing>
On Fri, Apr 25, 2003 at 12:36:28PM +0100, Matthew Wilcox wrote:
> On Thu, Apr 24, 2003 at 06:05:37PM -0700, Jesse Barnes wrote:
> > I must be missing something. I understand that you've effectively
> > created legacy I/O port spaces for each pci controller, but I don't
> > see how that helps you with a driver that does e.g. inb(0x3e8). What
> > do you anticipate that your stuff will be used for? That would help
> > out a bit...
>
> Most drivers don't do that any more though. All PCI drivers just read
> their BARs and do inb() from there. There's no ISA devices on hp's
> ia64 boxes, so ISA probes aren't an issue. We've been doing something
> similar on PA for a while (io addresses are 0xBBiiii; the EISA bus if
> present gets bus 0) with no problems.
Ok, if that's the case, then SN boxes should be ok (I think), since
we'll mess around with the BARs in pci_fixup so that they're all
accessible.
Jesse
next prev parent reply other threads:[~2003-04-25 17:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-24 22:25 [Linux-ia64] [PATCH] 1/4 multi-ioport space support for 2.5 Bjorn Helgaas
2003-04-24 22:37 ` Jesse Barnes
2003-04-25 0:44 ` Bjorn Helgaas
2003-04-25 1:05 ` Jesse Barnes
2003-04-25 11:36 ` Matthew Wilcox
2003-04-25 16:13 ` Bjorn Helgaas
2003-04-25 17:18 ` Jesse Barnes [this message]
2003-05-09 23:20 ` David Mosberger
2003-05-09 23:31 ` David Mosberger
2003-05-12 20:58 ` Bjorn Helgaas
2003-05-12 22:50 ` David Mosberger
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=marc-linux-ia64-105590723705609@msgid-missing \
--to=jbarnes@sgi.com \
--cc=linux-ia64@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 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.