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 maximum. Once an interrupt occurs, the processors jumps to the
Is h_args on the stack or in global space when passed into
rtems_interrupt_handler_install?
--jennifer
> -Original Message-
> From: devel [mailto:devel-boun...@rtems.org] On Behalf Of Andre
> Marques
> Sent: Monday, June 30, 2014 1:09 PM
> To: Gedare Bloom; Wendell Silva
> Cc: devel@rte
On 6/30/2014 1:08 PM, Andre Marques wrote:
On 06/30/14 18:07, Gedare Bloom wrote:
On Mon, Jun 30, 2014 at 12:52 PM, Wendell Silva wrote:
André,
Technically, you should be able to call functions (directly or indirectly)
in any point of your program. AFAIK, there are only a subset of RTEMS
dire
Hello Joel,
On Monday 30 of June 2014 19:20:23 Joel Sherrill wrote:
> Did you write this patch? Do you have paperwork with the FSF on file
> for GCC submissions?
As I have already stated, I have no papers signed with FSF but some of my
H8S enhancements has been used by GCC maintainers long time a
On 06/30/14 18:07, Gedare Bloom wrote:
On Mon, Jun 30, 2014 at 12:52 PM, Wendell Silva wrote:
André,
Technically, you should be able to call functions (directly or indirectly)
in any point of your program. AFAIK, there are only a subset of RTEMS
directives you shouldn't call from an ISR.
If t
On 6/30/2014 12:20 PM, Pavel Pisa wrote:
Next big-endian targets added are added to GCC RTEMS setup
(the first libraries search subdirecory name and the second GCC
options to select appropriate build mode)
Nice work! A few odd questions.
Did you write this patch? Do you have paperwork with t
Next big-endian targets added are added to GCC RTEMS setup
(the first libraries search subdirecory name and the second GCC
options to select appropriate build mode)
eb
- mbig-endian
- for standard ARMv4
thumb/eb
- mthumb mbig-endian
- for THUMB ARMv4+
thumb/armv7-r/eb
- mthumb ma
Hello everybody,
we have advanced with preparation RTEMS multilib toolchain which
targets Cortex-R in big-endian thumb mode. The required RTEMS ARM
target fragments are included in followup patch.
I have used next configure script options
CFLAGS="-O2 -pipe" LDFLAGS=-s \
../../../src/gcc-4.9/conf
On Mon, Jun 30, 2014 at 12:52 PM, Wendell Silva wrote:
> André,
>
> Technically, you should be able to call functions (directly or indirectly)
> in any point of your program. AFAIK, there are only a subset of RTEMS
> directives you shouldn't call from an ISR.
If the function does not 'sleep' it sh
André,
Technically, you should be able to call functions (directly or indirectly)
in any point of your program. AFAIK, there are only a subset of RTEMS
directives you shouldn't call from an ISR.
What kind of error have you got? BSP?
--Wendell.
2014-06-30 13:47 GMT-03:00 Andre Marques :
> Hell
Hello,
I am trying to call a function through a function pointer from an
interrupt handler, but I am not sure if this is even possible as the
system hangs at that point. If not, is there any way in RTEMS to have
that function executed outside the isr?
Thanks,
André Marques.
___
On 2014-06-30 13:34, Sebastian Huber wrote:
@@ -83,8 +84,8 @@ static void leon3_console_isr(void *arg)
}
if (
-(status & LEON_REG_UART_STATUS_THE)
- && (uart->regs->ctrl & LEON_REG_UART_CTRL_TI) != 0
+(status & APBUART_STATUS_THE)
+ && (uart->regs->ctrl & APBUART_CTRL_T
On 2014-06-30 13:23, Daniel Hellstrom wrote:
hardware. The GRLIB APBUART is compatible on most or if not all aspects with
the LEON2 AT697 UART, however the APBUART have more features that are currently
not in use. I think it would be better to call the LEON3 BSP UART "APBUART" and
the LEON2 UART
---
c/src/lib/libbsp/sparc/leon3/console/console.c | 31 +-
.../libbsp/sparc/leon3/console/printk_support.c| 13 ---
c/src/lib/libbsp/sparc/leon3/include/leon.h| 33
c/src/lib/libbsp/sparc/shared/include/apbuart.h|1 +
c/src/li
Hello,
I like this initiative of having common code, however I'm not sure that all of it is good. The LEON2 UART and the LEON3 APBUART is not the same hardware. The GRLIB APBUART is compatible on most or if
not all aspects with the LEON2 AT697 UART, however the APBUART have more features that ar
On 2014-06-26 12:50, Sebastian Huber wrote:
Hello,
for SMP support we need atomic operations. We use the ones provided by the C11
and C++11 standards. For this it is necessary to use -std=gnu++11 as a GCC
option since otherwise an include of yields to compile time errors.
Does anyone know how
---
c/src/lib/libbsp/sparc/leon2/console/console.c | 35 ++-
c/src/lib/libbsp/sparc/leon2/console/debugputs.c | 17 +
c/src/lib/libbsp/sparc/leon2/include/leon.h| 35
c/src/lib/libbsp/sparc/leon2/include/rasta.h | 31
17 matches
Mail list logo
