[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Disconnect at BAR Boundary
- To: Mailing List Recipients <pci-sig-request@znyx.com>
- Subject: Disconnect at BAR Boundary
- From: kands@usa.net
- Date: Mon, 20 Jan 1997 17:09:35
- Resent-Date: Mon, 20 Jan 1997 17:09:35
- Resent-From: pci-sig-request@znyx.com
- Resent-Message-Id: <"zFHvU.0.m92.vU1vo"@dart>
- Resent-Sender: pci-sig-request@znyx.com
Hi,
I have a Question regarding the burst access crossing a Bar Boundary.
Suppose A master starts a memory access very close to the bar boundary
and does a burst memory write(posted) to the application which crosses
the boundary in between. Is is very essential that the target must
issue a disconnect exactly at the BAR boundary or is it sufficient enough if the target takes care that the appliction to which the write was target does not get affected due to the write which occured accross
the BAR Boundary.
I am not able to find any where in the 2.1 specs which discusses or states clearly about this issue.
I would also like to know the pros and cons if there was not exact
disconnect at the BAR Boundary but some time later as this was a
posted xactions.
It would be nice if you could clarify the same issue in the case of
prefetchable reads too.
--thanks
--kands
û ô á