| Age | Commit message (Collapse) | Author |
|---|
|
|
|
The boot loader must set the MEM SWAP field of the Bus Matrix Module
Control Register 1 (BMMCR1).
|
|
It is necessary that the environment variable XTRATUM_PATH is set to the
XtratuM installation path, e.g.
XTRATUM_PATH="/opt/xtratum/xm"
By default the example_xm_cf.xml will be used for building the tests.
It can be overwritten with setting the XTRATUM_CONFIG environment
variable to another XML file, e.g.
XTRATUM_CONFIG="/some/path/to/rtems_xm_cf.xml"
|
|
|
|
|
|
|
|
Update #3093.
|
|
Update #3093.
|
|
Update #3090.
|
|
Update #3090.
|
|
Update #3090.
|
|
Update #3090.
|
|
Make Clock_driver_support_shutdown_hardware() optional. This avoids
the atexit() support on memory constrained targets.
|
|
Use a specific define for the interrupt exception frame size.
Update #3082.
|
|
Rename ppc_exc_wrap_async_normal to ppc_exc_interrupt to avoid a bit of
obfuscation.
Update #3082.
|
|
There is no need to explicitly set the output format and architecture in
the linker script. This enables the usage of this linker script with
the ELFv2 ABI (64-bit).
Update #3082.
|
|
Avoid use of small-data area, since it is not supported in the ELFv2 ABI
by GCC.
Update #3082.
|
|
Update #3082.
Update #3085.
|
|
|
|
This fixes some "variably modified" warnings and a clang compile error.
|
|
|
|
Intel has obsoleted this hardware and the BSP was never completed.
closes #3086.
|
|
|
|
|
|
|
|
Update #3082.
Update #3085.
|
|
|
|
|
|
Update #2859.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Due to the FDT support we can now reduce the BSP variants. Use the
processor core to define the BSP variants.
Update #3082.
Update #3085.
|
|
Do not flush/invalidate the caches. Instead enable the cache during the
low-level initialization and perform an explicit cache flush for the
read-only and fast-text sections.
Update #3082.
Update #3085.
|
|
|
|
|
|
The SPARC ABI is a bit special with respect to the floating point context.
The complete floating point context is volatile. Thus, from an ABI point
of view nothing needs to be saved and restored during a context switch.
Instead the floating point context must be saved and restored during
interrupt processing. Historically, the deferred floating point switch was
used for SPARC and the complete floating point context is saved and
restored during a context switch to the new floating point unit owner.
This is a bit dangerous since post-switch actions (e.g. signal handlers)
and context switch extensions may silently corrupt the floating point
context.
The floating point unit is disabled for interrupt handlers. Thus, in case
an interrupt handler uses the floating point unit then this will result in a
trap (INTERNAL_ERROR_ILLEGAL_USE_OF_FLOATING_POINT_UNIT).
In uniprocessor configurations, a lazy floating point context switch is
used. In case an active floating point thread is interrupted (PSR[EF] == 1)
and a thread dispatch is carried out, then this thread is registered as the
floating point owner. When a floating point owner is present during a
context switch, the floating point unit is disabled for the heir thread
(PSR[EF] == 0). The floating point disabled trap checks that the use of the
floating point unit is allowed and saves/restores the floating point context
on demand.
Update #3077.
|
|
Add new fatal error INTERNAL_ERROR_ILLEGAL_USE_OF_FLOATING_POINT_UNIT.
Update #3077.
|
|
Rename SPARC_USE_SAFE_FP_SUPPORT in SPARC_USE_SYNCHRONOUS_FP_SWITCH.
Update comment.
Update #3077.
|
|
Update #3077.
|
|
|
|
|
|
Avoid void pointer arithmetic.
Updates #2859.
|
|
Use the libio mutex lock instead of the mmap mappings lock.
Updates #2859.
|
