Re: Can you MOP boot an install kernel directly?

[Paul Koning <paulkoning%comcast.net@localhost>]

> On Aug 4, 2025, at 10:25 PM, Johnny Billquist <bqt%softjar.se@localhost> wrote:
> 
> ...
> But think about it. Even detecting and processing the trigger requires something to receive and process a MOP message. And this could be for a CPU halted. How would you do that unless the controller itself understands MOP?

Clearly, supporting trigger requires controller support.  It's just like the later "Wake on LAN" message.  But supporting trigger just requires a pattern match; it doesn't require sending anything, much less executing a protocol state machine.

The next step typically is primary load, which uses a single message, so a single request/response.  Again, no real state machine.  The final stage is the secondary or system load, which transfers a sequence of messages so it requires a state machine that does sequence number handling, timeout and retry, etc.  The reason for the primary vs. later distinction is that the ROM boot just does the primary load, so it basically is a transmit and a receive, repeated until it works.

	paul