| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
and maximal alignment.
There is need for unambiguous named and defined cache function
which should be called when code is updated, loaded
or is self-modifying.
There should be function to obtain maximal cache line length
as well. This function can and should be used for allocations
which can be used for data and or code and ensures that
there are no partial cache lines overlaps on start and
end of allocated region.
Updates #2782
|
|
|
|
|
|
|
|
|
|
|
| |
base access.
The main reason for inclusion of minimum hypervisor related defines
is that current ARM boards firmware and loaders (U-boot for example)
start loaded operating system kernel in HYP mode to allow it take
control of virtualization (Linux/KVM for example).
Updates #2783
|
|
|
|
|
| |
Updates #2782
Updates #2783
|
|
|
|
|
|
|
| |
Properly pass the stack aligned context to _CPU_Context_switch_altivec()
since _CPU_altivec_ctxt_off defined via ppc_context.
Update #2761.
|
|
|
|
|
|
|
|
|
|
|
|
| |
The window underflow trap handler used %i5 which destroyed the %o5 of
the calling context. Bug introduced by
0d3b5d47429effb350448d9e9123a67db722109f.
Go back to the pre 0d3b5d47429effb350448d9e9123a67db722109f behaviour
and use the two unused instructions in the trap vector to optimize a
bit.
Close #2651.
|
|
|
|
| |
Close #2502.
|
|
|
|
| |
Close #2470.
|
|
|
|
| |
Close #2373.
|
| |
|
|
|
|
|
| |
Drop the <rtems/score/percpu.h> include since this file exposes a lot of
implementation details.
|
|
|
|
|
|
|
|
| |
Store the floating-point unit property in the thread control block
regardless of the CPU_HARDWARE_FP and CPU_SOFTWARE_FP settings. Make
sure the floating-point unit is only enabled for the corresponding
multilibs. This helps targets which have a volatile only floating point
context like SPARC for example.
|
|
|
|
| |
Update #2356.
|
| |
|
| |
|
| |
|
|
|
|
| |
Update #2271.
|
| |
|
| |
|
|
|
|
|
| |
Get rid of _CPU_cache_invalidate_instruction_range declaration
as it doesn't make sense here.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
fix warning
|
|
|
|
|
| |
The sparc64 port had some incorrect copyright notices affixed to
source code files.
|
|
|
|
|
|
|
| |
PowerPC Book E: Account for an extra tick period if a tick increment's
pending.
Close #2230.
|
|
|
|
| |
Close #2237.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Add AltiVec and FPU support to the Context_Control in case we use the
e6500 multilib.
Add PPC_MULTILIB_ALTIVEC and PPC_MULTILIB_FPU multilib defines. Add
non-volatile AltiVec and FPU context to Context_Control. Add save/restore of
non-volatile AltiVec and FPU to _CPU_Context_switch(). Add save/restore
of volatile AltiVec and FPU context to the exception code. Adjust data
cache optimizations for the new context and cache line size.
|
|
|
|
| |
This is not correct, but works for now.
|
|
|
|
| |
Provide floating point context support only if PPC_HAS_FPU == 1.
|
| |
|
|
|
|
|
| |
Use it for the default PPC_CACHE_ALIGNMENT. Use it for
PPC_STRUCTURE_ALIGNMENT.
|
| |
|
| |
|
| |
|
|
|
|
| |
Do not warn about not implemented cache functions.
|
|
|
|
| |
Give the BSP the ability to define PPC_CACHE_ALIGNMENT.
|
| |
|
| |
|
|
|
|
|
|
| |
Also use the const qualifier on the address pointer's target in in_*()
Closes #2128
|
|
|
|
| |
close #2211
|
|
|
|
| |
close #2211
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
On recent u-boots, the watchdog is turned on / left enabled. The
Beaglebone Black rev. C ships with such a u-boot internally so any
application booting from it must disable the watchdog.
Therefore this change is needed to boot an RTEMS app out-of-the-box
on a BBB Rev C - otherwise the user button must be held during boot
(to bypass the stock uboot) or the internal uboot must be updated. To
allow for a better out-of-the-box experience, we just turn off the
watchdog.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Coding style cleanups.
* Use OS reserved trap 0x89 for IRQ Disable
* Use OS reserved trap 0x8A for IRQ Enable
* Add to SPARC CPU supplement documentation
This will result in faster Disable/Enable code since the
system trap handler does not need to decode which function
the user wants. Besides the IRQ disable/enabled can now
be inline which avoids the caller to take into account that
o0-o7+g1-g4 registers are destroyed by trap handler.
It was also possible to reduce the interrupt trap handler by
five instructions due to this.
|
|
|
|
|
|
|
|
|
|
|
| |
Save five instructions on underflow handling.
By using an optimized trap entry we can move instructions from
the window underflow function into the trap entry vector. By
setting WIM=0 and using RESTORE it is possible to move the
new WIM register content from the trapped window into the
to-be-restored register window. It is then possible to avoid
the WIM write delay.
|