From: Bjorn Helgaas <bjorn_helgaas@hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] [PATCH] 2.5.18 early printk, PCI segment, multi-IOMMU support
Date: Tue, 23 Jul 2002 15:22:48 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590701905817@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701905804@msgid-missing>
> Bjorn> 60_pci_tra.diff Add support for PCI root bridges with
> Bjorn> non-zero translation offsets.
>
> This one handles only memory offsets. Any particular reason for this?
> Perhaps there should be at least a check which will warn/panic if a
> non-zero I/O offset is found?
Yup, there's a reason, but it's kind of lame: I haven't figured
out how to deal with I/O offsets yet :-) That gets into how
I/O spaces other than the legacy 64Kb space are described in
ACPI, and how the kernel accesses them. So handling I/O
offsets will (I think) involve more extensive changes to I/O
port addressing.
--
Bjorn Helgaas - bjorn_helgaas at hp.com
Linux Systems Operation R&D
Hewlett-Packard Company
prev parent reply other threads:[~2002-07-23 15:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-22 22:22 [Linux-ia64] [PATCH] 2.5.18 early printk, PCI segment, multi-IOMMU support Bjorn Helgaas
2002-07-23 5:43 ` David Mosberger
2002-07-23 15:22 ` Bjorn Helgaas [this message]
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-105590701905817@msgid-missing \
--to=bjorn_helgaas@hp.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.