[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: FW: Re[2]: PCI I/O Space Consumption Limitation
- To: Mailing List Recipients <pci-sig-request@znyx.com>
- Subject: Re: FW: Re[2]: PCI I/O Space Consumption Limitation
- From: Mark Gonzales <markg@scic.intel.com>
- Date: Thu, 22 Aug 1996 14:07:37 -0700
- Cc: markg@ichips.intel.com
- Resent-Date: Thu, 22 Aug 1996 14:07:37 -0700
- Resent-From: pci-sig-request@znyx.com
- Resent-Message-Id: <"1SlKK2.0.v22.9oC7o"@dart>
- Resent-Sender: pci-sig-request@znyx.com
"Taylor, Mike" writes
>I thought PCI/ISA bridges used subtractive decode and therefore were only
>active in address spaces not acknowledged by any PCI bus. Aliasing by an
>ISA card would therefore be prevented in any PCI used I/O space. The 256
>bytes per I/O BAR restriction is therefore not due to ISA limitations.
I believe that legacy *device drivers* make use of the I/O address
aliasing property. So, if a new device claimed an alias of a legacy I/O
port, it would receive I/O accesses intended for the legacy device, and
both devices would fail to work.
I/O space accesses are usually much lower performance than memory space
accesses, so I wouldn't recommend using I/O space in a new device
design anyway.
--Mark
r x e