On Jun 30, 2014, at 14:41 , Joel Sherrill wrote:
> Is your "struct handler_arguments" declared on the stack (e.g. an
> automatic variable)? If so, then the memory is likely clobbered by
> the time the ISR runs.
Not necessarily. A common method would be:
thread_to_process_something() {
Chris, I would like to ask where should I put rtems-boot hd image needed to
run pc386 on qemu. Should I create some directory under rtems-tools and put
image into it?
2014-06-27 3:34 GMT+02:00 Gedare Bloom :
> On Thu, Jun 26, 2014 at 5:26 PM, Chris Johns wrote:
> > On 27/06/2014 4:09 am, Joel S
On 2014-07-01 16:56, Sebastian Huber wrote:
gcc/ChangeLog
2014-07-01 Sebastian Huber
* config/arm/t-rtems-eabi: Add
mthumb/march=armv7-r/mfpu=vfpv3-d16/mfloat-abi=hard,
mbig-endian/mthumb/march=armv7-r, and
mbig-endian/mthumb/march=armv7-r/mfpu=vfpv3-d16/mfloat
gcc/ChangeLog
2014-07-01 Sebastian Huber
* config/arm/t-rtems-eabi: Add
mthumb/march=armv7-r/mfpu=vfpv3-d16/mfloat-abi=hard,
mbig-endian/mthumb/march=armv7-r, and
mbig-endian/mthumb/march=armv7-r/mfpu=vfpv3-d16/mfloat-abi=hard
multilibs.
---
gcc/config/a
Fix context switch on SMP for ARM, PowerPC and SPARC.
Atomically test and set the is executing indicator of the heir context
to ensure that at most one processor uses the heir context. Break the
busy wait loop also due to heir updates.
---
c/src/lib/libbsp/sparc/shared/irq_asm.S | 55
On 6/30/2014 6:51 PM, Hesham Moustafa wrote:
> Hi,
>
> I want to implement an API for OpenRISC IRQ. The hardware assumes that
> the handlers are installed at addresses 0x100 * N, meaning that every
> interrupt handler is starting at a multiple of 0x100, and each of each
> is of size 0xFF at maximu
I guess I should clarify further, set_vector usually just calls some
function that installs a "template" in the handler, which consists of
basically calling a function. You can see some examples in the
cpukit/score or the SPARC is at libbsp/sparc/shared/irq/
-Gedare
On Tue, Jul 1, 2014 at 8:59 AM,
For a "simple vectored architecture", the usual approach in RTEMS is
to implement some "set_vector()" function that will install a function
pointer in the IRQ table. This function pointer will either be called
in "rtems" mode via trampoline code (ISR_Handler) that sets up a safe
C environment, or w