Re: Mutual exclusion between the OAL and a kernel mode driver
- From: "Dean Ramsier" <ramsiernospam@xxxxxxxxxx>
- Date: Thu, 24 Apr 2008 15:37:10 -0400
There is no synchronization mechanism available in the OAL other than
critical sections. You can either get creative with critical sections or
you have to move all I2C access code to the OAL.
This is a limitation of the CE6 kernel which I hope gets fixed in the next
version. Shared I2C accesses necessitated by an external real time clock is
the classic example of this issue.
--
Dean Ramsier - eMVP
BSQUARE Corporation
"snichols" <snichols@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:F846F7E6-BD52-4760-8A3D-6F078C465DD0@xxxxxxxxxxxxxxxx
I need to protect my i2c bus between my RTC functions int OAL and my kernel
mode i2c driver in 6.0. Any type of CreateEvent / Mutex call from within
my
OAL causes a hang. I hate to resort to a flag in driver global. :-)
.
- References:
- Mutual exclusion between the OAL and a kernel mode driver
- From: snichols
- Mutual exclusion between the OAL and a kernel mode driver
- Prev by Date: Mutual exclusion between the OAL and a kernel mode driver
- Next by Date: Re: DDRAW levels of resolution and picture quality
- Previous by thread: Mutual exclusion between the OAL and a kernel mode driver
- Index(es):