Re: Simulating an IRQ event

I am aware of the implications of the hardware acknowledging an interrupt
that didn't happen, I can fix that in the OAL. SetEvent() was what I wanted
but I didn't think I had access to the event handle so I wanted a function
like SetInterruptEvent( MY_SYSINTR).

The problem was a touch driver that didn't have a Pen down interrupt, I
wanted to simulate that happening without changing the MDD layer. I have now
found that the event has global scope, so a declaration:

extern HANDLE hTouchPanelEvent; //@globalvar HANDLE |
hTouchPanelEvent | Holds the event handle for

in my PDD allows me to get at it and use SetEvent()

--

Martin
"Steve Maillet (MVP)" <nospam@xxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:eIJZKdt$HHA.1188@xxxxxxxxxxxxxxxxxxxxxxx
It has been a long time since I have used that function and haven't
commited the documentation to memory.

Probably should use SetEvent then.

However, the docs don't warn you of the potential problems Dean pointed
out regarding the InterruptDone and the OAL. Generally it is a REALLY bad
idea to do this. Which leads me to ask the question of why you think you
need to do it?

Steve Maillet
http://www.EmbeddedFusion.com



.