This is the mail archive of the newlib@sourceware.org mailing list for the newlib project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

redboot syscalls for libgloss/arm


Who is the keeper of the syscalls defined in libgloss/arm/redboot-syscalls.c?

I would like to add dup, dup2, execve, and link. This list is
certainly not exhaustive, but it's the minimum needed for a useful
busybox shell running on a kernel implementing the redboot syscall
interface.

Rather than extending the redboot syscall interface, which seems to be
intentionally sparse by design, I suspect I'll move along to a more
fully featured syscall interface, likely that of Linux. This means
adding a new syscall interface, linux-syscalls.c, to libgloss/arm.
This addition brings up the question of the config name. The Linux
syscalls could be added to arm-elf, alongside RDI, RDP, and Redboot.
This approach seems to me to be the path of least resistance.
Alternatively, a new arm-linux-newlib (a.k.a.
arm-unknown-linux-newlib) target could be added.

I have already sent a patch to config-patches to add support for
i386-pc-linux-newlib, but I have received absolutely no response in a
month, even after pinging the list twice further. Is there a protocol
I'm not following?

Which syscall interface do the ARM RTEMS and ARM EABI targets use?

Cheers,
Shaun


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]