Initialization order problem in io/wallclock/

[Rutger Hofman]

Good afternoon,

the io/wallclock/ static initializer currently runs after 
CYG_INIT_CLOCK. However, the I2C device that may control the clock, or 
the clock itself, may use mutexes. Therefore the initializer order must 
be _AFTER( CYG_INIT_THREADS).

I ran into this when I enabled assertions in eCos: the mutex in my I2C 
was used before the thread package was initialized, and this caused an 
assertion failure.

Patch attached. Is this format OK? I merged eCos into our SVN 
repository, so the diff format will be slightly different from cvs diff 
output.

Rutger Hofman
VU Amsterdam
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: wallclock.patch
URL: <http://sourceware.org/pipermail/ecos-patches/attachments/20080111/86e58f96/attachment.ksh>