Stelian Pop wrote:
 > Hi,
 > The attached patch adds an option to make Xenomai userspace issue EABI
 > syscalls. This is needed to make Xenomai work with kernels compiled with
 > Note that due to a change in syscall handling when the EABI layer was
 > added in the kernel, this patch is needed for all EABI enabled kernels,
 > even if the CONFIG_OABI_COMPAT compatibility layer has been enabled.
 > All sensible combinations should be supported: old ABI userspace with
 > old ABI kernel, old ABI userspace with CONFIG_OABI_COMPAT kernels, EABI
 > userspace with EABI kernels. The other combinations will fail with a
 > SIGILL signal.
 > Don't forget to run 'scripts/bootstrap' after applying this patch...
 > Signed-off-by: Stelian Pop <[EMAIL PROTECTED]>

I get a problem with this patch: I am in the no EABI case in user-space
and kernel-space, and when starting latency, I get an "Illegal
instruction" message. If I revert this patch, latency starts
correctly. Any idea ?


                                            Gilles Chanteperdrix.

Xenomai-core mailing list

Reply via email to