[Bug 1000638] New: kernel tests intr0, kintr0 fails with someconditions

[bugzilla-daemon at ecoscentric dot com]

http://bugs.ecos.sourceware.org/show_bug.cgi?id=1000638

           Summary: kernel tests intr0, kintr0 fails with some conditions
           Product: eCos
           Version: CVS
          Platform: Other (please specify)
        OS/Version: Other
            Status: UNCONFIRMED
          Severity: normal
          Priority: normal
         Component: Test farm
        AssignedTo: jld@ecoscentric.com
        ReportedBy: sergei.gavrikov@gmail.com
         QAContact: ecos-bugs@ecos.sourceware.org
             Class: ---


Created an attachment (id=612)
 --> (http://bugs.ecos.sourceware.org/attachment.cgi?id=612)
fix? issue with an interrupt configure call in intr0.cxx, kintr0.cxx tests

Kernel tests: intr0.cxx, kintr0.cxx try to configure interrupt &v1, which
number assigns itself with a random? value:

v1 = CYGNUM_HAL_ISR_MIN + (6 % CYGNUM_HAL_ISR_COUNT)

Unfortunately, not all targets have same interrupts (configurable). The
external interrupts are configurable only, e.g., only numbers 14, 15, 16, 17
are external (=configurable) on lpc2xxx targets. More that v1 number is 6 for
it and for this platform that is CYGNUM_HAL_INTERRUPT_UART0. So, every time I
got ASSERT_FAIL on interrupt configure calls in intr0/kintr0 tests.

Can we call C++ Cyg_Interrupt::configure_interrupt, cyg_interrupt_configure in
C in test by a condition only?

For example, to call these configure if something like HAL_INTR_TEST_CONFIGURE
is defined. If this dumb switch is okay, I attach 2 kopeika patch.

Regards,

Sergei


-- 
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.