Searched refs:IRB (Results 1 – 7 of 7) sorted by relevance
197 # r9: IRB address
737 TachLiteIRB IRB; // I/O Request Block, gets copied to ERQ member
4058 pIRB = &Exchanges->fcExchange[*fcExchangeIndex].IRB; in cpqfcTSBuildExchange()4579 pExchange->IRB.Req_A_Trans_ID = ExchangeID & 0x7FFF; // 15-bit field in cpqfcTSStartExchange()4700 &pExchange->IRB, 32); // fixed (hardware) length! in cpqfcTSStartExchange()
888 response block (IRB) as part of the device status block in dev_id->ii.irb.980 basing its processing decisions on the interruption response block (IRB) that981 is part of the dev_id buffer area. The IRB area represents the interruption984 (DEVSTAT_STATUS_PENDING), the IRB information may or may not show the complete
1685 from which you receive an Interruption response block (IRB). If you get channel & device end 1686 status in the IRB without channel checks etc. your IO probably went okay. If you didn't you1687 probably need a doctorto examine the IRB & extended status word etc.1690 be presented in the Extended status word in the IRB if not you have to issue a
1100 .long SYMBOL_NAME(do_IRQ) ! 120 0x1100 IRBlaster IRB