From: "David S. Miller" <davem@redhat.com>
To: hpa@zytor.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PCI updates - 32-bit IO support
Date: Wed, 19 Dec 2001 21:30:19 -0800 (PST) [thread overview]
Message-ID: <20011219.213019.35013739.davem@redhat.com> (raw)
In-Reply-To: <9vrmea$mef$1@cesium.transmeta.com>
In-Reply-To: <20011218235024.N13126@flint.arm.linux.org.uk> <9vrmea$mef$1@cesium.transmeta.com>
From: "H. Peter Anvin" <hpa@zytor.com>
Date: 19 Dec 2001 19:37:46 -0800
You probably need to verify that 32-bit support is available (both on
the bridge and the peripherals), but if they are, there's no reason
not to use it on non-x86 architectures...
Don't the PCI specs actually talk about 24-bits in fact?
Russell does you box really have the full 32-bits or is it
really just 24-bits?
next prev parent reply other threads:[~2001-12-20 5:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-18 23:50 [PATCH] PCI updates - 32-bit IO support Russell King
2001-12-20 3:37 ` H. Peter Anvin
2001-12-20 5:30 ` David S. Miller [this message]
2001-12-20 5:57 ` H. Peter Anvin
2001-12-20 9:37 ` Russell King
2001-12-20 13:18 ` Ivan Kokshaysky
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=20011219.213019.35013739.davem@redhat.com \
--to=davem@redhat.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox