PXI Registers: Difference between revisions
No edit summary |
|||
| Line 3: | Line 3: | ||
Each pxi_id corresponds to a Process9 PXI [[PXI_Services|command-handler]] thread which handles the actual command processing. With newer FIRM the pxi_id must be in a certain range. | Each pxi_id corresponds to a Process9 PXI [[PXI_Services|command-handler]] thread which handles the actual command processing. With newer FIRM the pxi_id must be in a certain range. | ||
There's a dedicated Process9 thread for receiving data from PXI, once it finishes receiving a request it copies the cmd_buf into a buffer for the corresponding pxi_id then signals an event so that the cmd-handler thread can process it. Once a cmd-handler thread finishes processing a command, the thread itself then sends the response over PXI. This means that multiple commands for different pxiIDs can be be handled at the same time, even when one cmd-handler completely hangs/etc for example. | |||
==Request== | ==Request== | ||