[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

set_vector

Hi,

While trying to build the bare bsp for sh-rtems, I noticed some issues
with regard to "set_vector":

AFAIS, set_vector most probably can be replaced by rtems_catch_interrupt
or _CPU_ISR_install_raw_handler on probably all targets (I didn't check
them all, however).

In contrary to rtems_catch_interrupt or _CPU_ISR_install_raw_handler,
set_vector is not an official API function of rtems nor an official API
function for BSPs. 

This prevents building the bare bsp for CPUs, which have drivers
applying set_vector in libcpu (hppa1.1, mips64orion, ppc403, sh7032).

To fix this problem I can imagine several solutions:
1. Completly remove set_vector from rtems anywhere (at minimum in
libcpu) and replace calls to it by official rtems' API functions.
2. Make set_vector an official rtems API function to be defined ether in
libcpu or in exec/score.

I'd prefer solution #1, but I can't judge if this approach is applicable
to all CPUs/BSPs.

Opinions? 

Ralf.

-- 
Ralf Corsepius 
Forschungsinstitut fuer Anwendungsorientierte Wissensverarbeitung (FAW)
Helmholtzstr. 16, 89081 Ulm, Germany     Tel: +49/731/501-8690
mailto:corsepiu at faw.uni-ulm.de           FAX: +49/731/501-999  
http://www.faw.uni-ulm.de