ticker task wakeup order

[Allan Hessenflow]

Is the order that the ticker tasks wake up in significant?  While it
looks fine comparing the output I'm getting to what I'd expect from the
code, I notice the ticker.scn file shows them waking in a different
order than I'm seeing.  So I'm wondering if that could indicate some
problem in my port.  Here's my output:

*** CLOCK TICK TEST ***
TA1  - rtems_clock_get - 09:00:00   12/31/1988
TA2  - rtems_clock_get - 09:00:00   12/31/1988
TA3  - rtems_clock_get - 09:00:00   12/31/1988
TA1  - rtems_clock_get - 09:00:05   12/31/1988
TA2  - rtems_clock_get - 09:00:10   12/31/1988
TA1  - rtems_clock_get - 09:00:10   12/31/1988
TA3  - rtems_clock_get - 09:00:15   12/31/1988
TA1  - rtems_clock_get - 09:00:15   12/31/1988
TA2  - rtems_clock_get - 09:00:20   12/31/1988
TA1  - rtems_clock_get - 09:00:20   12/31/1988
TA1  - rtems_clock_get - 09:00:25   12/31/1988
TA2  - rtems_clock_get - 09:00:30   12/31/1988
TA3  - rtems_clock_get - 09:00:30   12/31/1988
TA1  - rtems_clock_get - 09:00:30   12/31/1988
*** END OF CLOCK TICK TEST ***

allan

-- 
Allan N. Hessenflow      allanh at kallisti.com