Of course, the code that you've invoked when you do this will send an EOI to
the interrupt controller where there was no hardware interrupt. This will
inevitably dismiss some *other* interrupt, causing another ISR to be
skipped, causing indeterminate system behavior. (And this is just the most
obvious of problems here.)
"Madhusudan Narayan" wrote in message
You can try this.
You need to know(determine) the interrupt vector.
Suppose it is 0x53,
Now you can fake an interrupt using
__asm int 0x53
Note: you can't use variable names with "int" instruction. you might prefer
to use a switch statement.
On 3/19/07, firstname.lastname@example.org wrote:
Walter oney Programming the Microsoft Windows Driver Model:
Chapter 5 The I/O Request Packet:
The "Standard Model" for IRP Processing:
The StartIo Routine $B!'(BIn fact, sometimes the easiest way to
commence a new operation is to store some state information in your device
extension and then fake an interrupt
But how to "fake an interrupt" ???????
Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer