You don't protect or1k specific code with this. It is only supposed to be used
in generic code. I suspect the generic clock framework has a cast to cover this
up
On August 9, 2014 3:04:09 AM CDT, Hesham Moustafa
wrote:
>I can use this in my port from my assembly code part of _ISR_Handler
>jus
Hi all,
I am trying to optimize the _ISR_Handler code. OpenRISC folks
indicated that I can use shadow registers to hold interrupted task
context. There are 512 SPRs that can be used for mapping general
purpose registers to these SPRs (I guess we can use them for nesting
interrupts, given that inte
On 08/08/2014 10:10 PM, Joel Sherrill wrote:
Hi
This is a belated response to a comment from Sebastian where he
said you shouldn't call malloc() or rtems_workspace_allocate()
from a create extension.
[...]
It is fine to use malloc() or rtems_workspace_allocate() in the create
extension.
htt
I can use this in my port from my assembly code part of _ISR_Handler
just before calling the user C Handler. Something like putting
#if CPU_ISR_PASSES_FRAME_POINTER
l.add r4, sp, r0
#endif
where r3 and r4 are the first and second arguments respectively.
RTEMS Clock_isr() (which I use for tick ti
