From: Brian P. <bri...@tu...> - 2005-05-17 23:34:49
|
aac...@ad... wrote: > Hi. > > I had a question about the NOP spu. I noticed that for Extended Opcode > calls which return information all happen to call functions within the > state_tracker\state_regcombiner.c file. The NOP SPU doesn't do anything like that. See spu/nop/nopspu.c > I assume this is to maintain some sort of state on the crserver > side. Does the application client sit and wait to receive a return > call (crNetSend->crNetRecv) for these Extended Opcode calls, or is it > left waiting forever? > > Does anyone have a good explanation as to what the NOP does when it > receives these Extended Opcodes? Are you sure you're talking about the NOP SPU? -Brian |