From: matthias.bgg@googlemail.com (Matthias Brugger)
To: kernelnewbies@lists.kernelnewbies.org
Subject: system call numbers
Date: Thu, 22 Nov 2012 09:44:37 +0100 [thread overview]
Message-ID: <50ADE5F5.8020904@gmail.com> (raw)
Hi all,
I'm looking into the avr32 architecture implementation, as compiling the
kernel gives you several warnings about system calls which are missing.
I had a look in the unistd.h file I realized that system call numbers
differ widely from other architectures (I had a look at arm and x86).
Are the system call numbers platform specific. As far as I understand,
the system calls are "wrapped" in libc. So I wonder if [g,e,uC]libc uses
a different system call number each architecture.
A look in the source of uClibc didn't helped me to clear my doubts.
If not all system calls are implemented for avr32:
- is there a problem at all, or does libc implementation take care of
not implemented system calls?
- if I want to add a system call, what are the steps needed?
Best regards,
Matthias
next reply other threads:[~2012-11-22 8:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-22 8:44 Matthias Brugger [this message]
2012-11-22 9:19 ` system call numbers Matthias Kaehlcke
2012-11-22 9:44 ` Adrian Perez de Castro
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50ADE5F5.8020904@gmail.com \
--to=matthias.bgg@googlemail.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).