linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: root@chaos.analogic.com
Cc: Ed Vance <EdV@macrolink.com>,
	"'linux-kernel'" <linux-kernel@vger.kernel.org>
Subject: Re: PCI drivers - memory mapped vs. I/O ports
Date: Mon, 18 Mar 2002 21:17:41 -0500	[thread overview]
Message-ID: <3C969FC5.10504@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.3.95.1020318152604.29558A-100000@chaos.analogic.com>

Richard B. Johnson wrote:

>On Mon, 18 Mar 2002, Ed Vance wrote:
>
>>If a PCI device can be programmed equally well via I/O port space or memory
>>space, what are the reasons to chose one space over the other when writing
>>the driver?
>>

>Basically, if you have a choice, it's hands-down to use memory-mapped
>I/O space.
>

Yep, I couldn't agree more.

    Jeff





      reply	other threads:[~2002-03-19  2:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-18 19:50 PCI drivers - memory mapped vs. I/O ports Ed Vance
2002-03-18 20:32 ` Alan Cox
2002-03-18 20:36 ` Richard B. Johnson
2002-03-19  2:17   ` Jeff Garzik [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=3C969FC5.10504@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=EdV@macrolink.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=root@chaos.analogic.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).