Does PERR# break LOCK#?

[Tom Jones <tjones@sebringnetworks.com>]

Hello,

I have a question relating to LOCK# handling. Section F.2: "Starting an
Exclusive Access" of R2.2 states:

	"Once the first data phase completes with both TRDY# and IRDY#
asserted, the exclusive operation is established and the master keeps LOCK#
asserted until either the lock operation completes or an error (Master-Abort
or Target-Abort) causes an early termination."

Given this I would assume that detection and recognition of a data parity
error on read or PERR# on write would not cause an early termination of the
exclusive access operation.

Does anyone have a different interpretation?

Thanks in advance,

Thomas C. Jones
Sr. MTS
Sebring Networks
tjones@sebringnetworks.com
408-871-7406