PCI drivers - memory mapped vs. I/O ports

From: Ed Vance (EdV@macrolink.com)
Date: Mon Mar 18 2002 - 14:50:41 EST

Next message: Jean Tourrilhes: "Killing tasklet from interrupt"
Previous message: Andrey Ulanov: "[PATCH] UFS bugfix, blocksize=16384"
Next in thread: Alan Cox: "Re: PCI drivers - memory mapped vs. I/O ports"
Reply: Alan Cox: "Re: PCI drivers - memory mapped vs. I/O ports"
Reply: Richard B. Johnson: "Re: PCI drivers - memory mapped vs. I/O ports"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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?

----------------------------------------------------------------
Ed Vance edv@macrolink.com
Macrolink, Inc. 1500 N. Kellogg Dr Anaheim, CA 92807
----------------------------------------------------------------

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Next message: Jean Tourrilhes: "Killing tasklet from interrupt"
Previous message: Andrey Ulanov: "[PATCH] UFS bugfix, blocksize=16384"
Next in thread: Alan Cox: "Re: PCI drivers - memory mapped vs. I/O ports"
Reply: Alan Cox: "Re: PCI drivers - memory mapped vs. I/O ports"
Reply: Richard B. Johnson: "Re: PCI drivers - memory mapped vs. I/O ports"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Sat Mar 23 2002 - 22:00:16 EST