Hang on a sec - turning these interrupt priorities into CDL options seems overkill. It would be simpler for the interrupt tests to contain something like:
#ifdef HAL_INTR_TEST_PRIO_A # define PRIO_A HAL_INTR_TEST_PRIO_A #else # define PRIO_A 1 #endif #ifdef HAL_INTR_TEST_PRIO_B # define PRIO_B HAL_INTR_TEST_PRIO_B #else # define PRIO_B 1 #endif cyg_interrupt_create(lvl1, PRIO_A, ...); cyg_interrupt_create(lvl1, PRIO_B, ...); and for the targets of interest arrange for HAL_INTR_TEST_PRIO_A and HAL_INTR_TEST_PRIO_B to be defined when #include'ing <cyg/hal/hal_intr.h>, e.g. via var_intr.h or proc_intr.h Allowing HALs to override defaults in testcases sometimes makes sense. However I cannot think of any circumstances where end users would want to mess about with these settings, so exposing them in the config tool would be inappropriate. Bart -- Bart Veer eCos Configuration Architect eCosCentric Limited The eCos experts http://www.ecoscentric.com/ Barnwell House, Barnwell Drive, Cambridge, UK. Tel: +44 1223 245571 Registered in England and Wales: Reg No 4422071.
