Re: Closing a thread that is waiting for Irq
- From: "Voidcoder" <voidcoder@xxxxxxxxx>
- Date: Thu, 30 Jun 2005 03:47:03 -0700
it was "... or whatever you want ..." in my post :)
"Steve Maillet (eMVP)" <nospam1@xxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:ulH2K8KfFHA.1372@xxxxxxxxxxxxxxxxxxxxxxx
> Instead of a global flag you can use the little known Event Data functions
> GetEventData and SetEventData to store the abort flag. This is preferred
> to forcing the event closed as closing the event generates an error
> condition and you can't distinguish it from a real error.
>
>
> --
> Steve Maillet
> EmbeddedFusion
> www.EmbeddedFusion.com
> smaillet at EmbeddedFusion dot com
>
>
.
- Follow-Ups:
- Re: Closing a thread that is waiting for Irq
- From: Igge H
- Re: Closing a thread that is waiting for Irq
- References:
- Closing a thread that is waiting for Irq
- From: Igge H
- Re: Closing a thread that is waiting for Irq
- From: Anthony Pellerin
- Re: Closing a thread that is waiting for Irq
- From: Voidcoder
- Re: Closing a thread that is waiting for Irq
- From: Steve Maillet \(eMVP\)
- Closing a thread that is waiting for Irq
- Prev by Date: Re: How to determine which ceddk api to use
- Next by Date: Re: XScale sleep mode
- Previous by thread: Re: Closing a thread that is waiting for Irq
- Next by thread: Re: Closing a thread that is waiting for Irq
- Index(es):
Relevant Pages
|
|