From: n0ano@n0ano.com
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] 32bit syscall numbers
Date: Fri, 28 Mar 2003 20:39:01 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590723705360@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590723705359@msgid-missing>
Chandra-
Why do you care? The table in `arch/ia64/ia32/entry.S' is the only
place in the kernel where the syscall numbers are needed and that
information is embedded in the table, there's no need for a separate
list.
On Fri, Mar 28, 2003 at 12:21:19PM -0800, Chandra Kapate wrote:
> Hi,
>
> How do I find the 32 bit syscall numbers?
> I don't see any defines for, say __NR_ia32_chdir in
> any of the include files.
> One can look at the arch/ia64/ia32/entry.S file and
> deduce the numbers. But, is there any easy way?
> I see asm-x86_64/ia32_unistd.h file which contains
> the 32 bit syscall numbers. But, I don't see the
> corresponding file for ia64.
>
> I am running RedHat AS 2.1 on Itanium-2 box.
>
> Thanks,
>
> Chandra
>
> __________________________________________________
> Do you Yahoo!?
> Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop!
> http://platinum.yahoo.com
>
> _______________________________________________
> Linux-IA64 mailing list
> Linux-IA64@linuxia64.org
> http://lists.linuxia64.org/lists/listinfo/linux-ia64
--
Don Dugger
"Censeo Toto nos in Kansa esse decisse." - D. Gale
n0ano@n0ano.com
Ph: 303/447-2201
next prev parent reply other threads:[~2003-03-28 20:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-28 20:21 [Linux-ia64] 32bit syscall numbers Chandra Kapate
2003-03-28 20:39 ` n0ano [this message]
2003-03-31 4:33 ` Chandra Kapate
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=marc-linux-ia64-105590723705360@msgid-missing \
--to=n0ano@n0ano.com \
--cc=linux-ia64@vger.kernel.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