[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
non-consistent byte enables
- To: Mailing List Recipients <pci-sig-request@znyx.com>
- Subject: non-consistent byte enables
- From: Suzie Gemignani <Suzie.Gemignani@tsc.tdk.com>
- Date: Tue, 12 Nov 96 11:12:45 PST
- Mailer: Elm [revision: 70.85]
- Resent-Date: Tue, 12 Nov 96 11:12:45 PST
- Resent-From: pci-sig-request@znyx.com
- Resent-Message-Id: <"wEvSG.0.iN.zmCYo"@dart>
- Resent-Sender: pci-sig-request@znyx.com
Hi everyone,
I'm struggling with the following question:
It says in the spec. (PCI spec. 2.1, pg.22, I/O read command) that
"The byte enables indicate the size of the transfer and must be
consistent with the byte address." What happens if they are not?
For example, let's say the master requests an I/O read with the
byte address AD(1:0) = 01. The Target then claims the access by
asserting DEVSEL#, but the byte enables are "0111" which would
correspond to AD(1:0) = 11. Should the target go ahead and
complete the read in order to provide parity? (pg.29 last paragraph)
If so, does it matter what data is returned?
I'd truly appreciate any insight.
Thanks,
Suzie.