SCE-MI 1.0/1.1: Input ready propagation and reset

Hi,

let's take a brief break from the SCE-MI 2.0 discussions and consider
the following.  On Fig 8, p. 24 in SCE-MI 1.1.0, it is shown how
input-ready propagation happens right after ureset deasserts when
ReceiveReady is asserted.  On p. 54 in the paragraph on the top of
the page and the NOTE below Fig. 17 it is implied that messages can
be transferred during reset.  Although it talks about output messages
I do not think we have disallowed input messages to be transferred.

So here is the apparent contradiction: on one hand we allowed messages
to be transferred during reset, on the other hand input-ready
propagation does not seem to be allowed during reset.

There is a follow on question to all of this because for message
transfer to happen, ports must be bound.  So as far as I remember
the exact event that starts the reset process is not specified in
the spec.  Please correct me if I am wrong here.  I have assumed
that it is triggered by SceMi::Init().  If SceMi::Init() triggers
the reset, then the application must be awfully quick to bind its
ports if it intends to transfer messages during reset, or the user
must specify an extremely long reset sequence.  Alternatively,
one could start the reset process on the very first call of
ServiceLoop().  This would allow (essentially infinite) time to bind
all ports and then transfer messages during reset.

Is this whole idea of transferring messages during reset just a bad
idea?

If Duaine and/or John S. could spare a few moments to answer the
above questions, I'd appreciate it.  I am once again (perhaps
naively) hoping we can clarify the intent without opening up
another can of worms :-)

Thanks,
Per

-- 
Per Bojsen                                Email: <bojsen@zaiqtech.com>
Zaiq Technologies, Inc.                   WWW:   http://www.zaiqtech.com
78 Dragon Ct.                             Tel:   781 721 8229
Woburn, MA 01801                          Fax:   781 932 7488