On 29.01.19 23:14, Richard Weinberger via Xenomai wrote:
Hi!
When running a ia32 application on x86_64 I get bad syscall errors.
This happens with ipipe-core-4.14.89-x86-2.patch and xenomai 3.0.8.
The problem seems to be that both ipipe_handle_syscall() and
handle_head_syscall()
check for
Hi!
When running a ia32 application on x86_64 I get bad syscall errors.
This happens with ipipe-core-4.14.89-x86-2.patch and xenomai 3.0.8.
The problem seems to be that both ipipe_handle_syscall() and
handle_head_syscall()
check for syscall-nr being >= NR_syscalls.
On ia32 the syscall table is
I was trying to update to 3.0.8, and looking at stat or acct in the
sched branch of the proc tree gives me an instant kernel crash, usually
with a null pointer access from a bogus code address, although the
locations aren't always the same. This is without even having my kernel
module or
On 29.01.19 10:57, Baur, Elias via Xenomai wrote:
Hello everyone,
I am new to lwIP and did a lot of research the last couple of days. My goal ist
to do real time networking between wire-connected Beagleboards. Therefore, we
have been setting up a Xenomai Co-Kernel on the boards. To actually
Hello everyone,
I am new to lwIP and did a lot of research the last couple of days. My goal ist
to do real time networking between wire-connected Beagleboards. Therefore, we
have been setting up a Xenomai Co-Kernel on the boards. To actually send and
receive UDP-packets, we want to use lwIP
