LEON3 Clock and Timer Driver

[Sebastian Huber]

Hello,

the LEON3 clock and timer driver use both LEON3_Timer_Regs (usually GPTIMER 0).

In separate source files we have

http://git.rtems.org/rtems/tree/c/src/lib/libbsp/sparc/leon3/clock/ckinit.c#n33

#if defined(RTEMS_MULTIPROCESSING)
   #define LEON3_CLOCK_INDEX \
     (rtems_configuration_get_user_multiprocessing_table() ? LEON3_Cpu_Index : 0)
#else
   #define LEON3_CLOCK_INDEX 0
#endif

and

http://git.rtems.org/rtems/tree/c/src/lib/libbsp/sparc/leon3/timer/timer.c#n24

#if defined(RTEMS_MULTIPROCESSING)
   #define LEON3_TIMER_INDEX \
       ((rtems_configuration_get_user_multiprocessing_table()) ? \
         (rtems_configuration_get_user_multiprocessing_table()->node) - 1 : 1)
#else
   #define LEON3_TIMER_INDEX 0
#endif

So we cannot use a clock and timer driver at the same time.  Is this intentional?

Why are there different methods used to select the index in the 
RTEMS_MULTIPROCESSING case?

-- 
Sebastian Huber, embedded brains GmbH

Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone   : +49 89 189 47 41-16
Fax     : +49 89 189 47 41-09
E-Mail  : sebastian.huber at embedded-brains.de
PGP     : Public key available on request.

Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.