Age | Commit message (Collapse) | Author | |
---|---|---|---|
2018-01-15 | or1k: Use new common syscall() implementation | Stafford Horne | |
Now that the common syscall implementation supports vararg calling conventions we can safely use it on OpenRISC. This saves a bit of code in the openrisc implementation. Signed-off-by: Stafford Horne <shorne@gmail.com> | |||
2017-12-10 | or1k: syscall: Pass arguments on the stack | Joel Stanley | |
Busybox internally calls syscall(2). - in unistd.h defined something like int syscall(nr, ....) - in syscall.c (common) implemented as int syscall(nr, arg1, arg3, arg3, arg4, arg5, arg6) This will not work, busybox thinks syscall should have varargs calling conventions. But it doesnt in the uclibc implementation so no args go through. Most architectures this will work. But on openrisc varargs are all sent on the stack. Regular args are passed in registers. Commit message and idea from Stafford Horne <shorne@gmail.com>. Signed-off-by: Joel Stanley <joel@jms.id.au> | |||
2017-05-14 | or1k: add clone() from old GNU libc implementation | Waldemar Brodkorb | |
2015-10-09 | add new architecture support for or1k | Waldemar Brodkorb | |
Information about Openrisc: http://opencores.org/or1k/Main_Page Integrated from: https://github.com/openrisc/uClibc-or1k |