Questions about input-ready propagation

Hi,

I thought I understood input-ready propagation but upon
rereading the discussion in the standard on pages 25 and
26 there are a few things I am wondering about:

  1) It appears that the intent of the IsReady() callback
     and input-ready propagation is for the software side
     to send exactly one message per IsReady() callback
     for the port of interest. But the SCE-MI infrastructure
     is not required to enforce this.

  2) Given the infrastructure is not enforcing the throttled
     flow of messages, what is supposed to happen with
     input-ready propagation if two messages occur at the
     port back-to-back? Is the infrastructure supposed to
     generate an IsReady() callback for each message or only
     once for the batch of back-to-back messages? Or is this
     implementation defined?

  3) The waveforms on p. 26 show input-ready propagation
     happening on the first rising edge of uclock where ReceiveReady
     is detected high either after being deasserted, right after a
     message moved, or right after ureset ended. Is to be taken
     literally or does the implementation have some leeway as to
     how quickly the input-ready condition is propagated? I
     suppose the answer here must be yes as there is no requirement
     defining an upper bound on when the input-ready condition
     should be seen on the SW side.

Thanks,
Per
Received on Mon May 3 09:21:14 2004