Filter
Top Products
Intel
®
IXP400 Software
Access-Layer Components: NPE Message Handler (IxNpeMh) API
Programmer’s Guide IXP400 Software Version 2.0 April 2005
Document Number: 252539, Revision: 007 229
7. Because this is a solicited message, the first ID-matching callback is removed from the
solicited callback list and invoked to pass the message back to the client.
If no ID-matching callback is found, the message is discarded and an error reported.
15.6 Receiving Unsolicited Messages from an NPE to
Client Software
The scenario of receiving unsolicited messages from an NPE to client software (as shown in
Figure 73) is:
1. At initialization, the client registers an unsolicited callback for a particular NPE and a message
ID.
2. After some time, the NPEs “outFIFO not empty” interrupt invokes the IxNpeMh component’s
ISR.
3. Within the ISR, the IxNpeMh component receives a message from the specific NPE.
4. The IxNpeMh component determines if this message ID has an unsolicited callback registered
for it.
If the message ID does not have a registered unsolicited callback, the message is solicited.
(See “Sending an NPE Message with Response” on page 228.)
Figure 72. Message with Response from Intel XScale
®
Core Software Client to an NPE
Client
IxNpeMh
NPE B NPE CNPE A
Customer / Demo Code
Access Driver
NPEs
1. Send Message
callback n+k
...
callback n+1
callback n
0x00 callback
0x01 callback
...
0xff callback
2. Save Callback
3. Send
Message
6. Get Callback
7. Response Callback
4. Message
Interrupt
5. Receive
Message
B2396-01