From: Jeff Garzik <jgarzik@pobox.com>
To: James Bottomley <James.Bottomley@steeleye.com>
Cc: mjacob@feral.com, SCSI Mailing List <linux-scsi@vger.kernel.org>,
Andrew Vasquez <praka@san.rr.com>, Andrew Morton <akpm@digeo.com>
Subject: Re: qla2xxx and feral ISP updates in their respective BK trees
Date: Fri, 20 Jun 2003 14:34:18 -0400 [thread overview]
Message-ID: <20030620183417.GB9164@gtf.org> (raw)
In-Reply-To: <1056133068.1804.22.camel@mulgrave>
On Fri, Jun 20, 2003 at 01:17:46PM -0500, James Bottomley wrote:
> On Fri, 2003-06-20 at 12:25, Matthew Jacob wrote:
> > Oh- is parisc like PPC and doesn't really support io space? That is,
> > prefers memory mapped registers?
>
> Well, it does, for PCI (since it's required to by the spec). However,
> the cost of generating an I/O cycle is very high (you essentially go via
> some memory mapped registers in the bus controller). Parisc certainly
> prefers memory mapped registers.
Is there hardware that supports both PIO and MMIO... and actually
prefers PIO?
I know of no such situation -- outside of hardware bugs and driver bugs,
which force the use of PIO, where both are available.
Pretty much everybody prefers memory mapped registers :)
Jeff
next prev parent reply other threads:[~2003-06-20 18:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-18 21:29 qla2xxx and feral ISP updates in their respective BK trees James Bottomley
2003-06-19 15:51 ` Andrew Vasquez
2003-06-20 17:12 ` Matthew Jacob
2003-06-20 17:19 ` James Bottomley
2003-06-20 17:25 ` Matthew Jacob
2003-06-20 18:17 ` James Bottomley
2003-06-20 18:34 ` Jeff Garzik [this message]
2003-06-20 18:39 ` Matthew Jacob
2003-06-20 21:59 ` Jeff Garzik
2003-06-20 22:06 ` Matthew Jacob
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=20030620183417.GB9164@gtf.org \
--to=jgarzik@pobox.com \
--cc=James.Bottomley@steeleye.com \
--cc=akpm@digeo.com \
--cc=linux-scsi@vger.kernel.org \
--cc=mjacob@feral.com \
--cc=praka@san.rr.com \
/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.