From: "H. Peter Anvin" <hpa@zytor.com>
To: Ley Foon Tan <lftan@altera.com>
Cc: linux-kernel@vger.kernel.org, arnd@arndb.de, linux-arch@vger.kernel.org
Subject: Re: Generic syscall ABI support
Date: Wed, 27 Mar 2013 22:35:20 -0700 [thread overview]
Message-ID: <5153D698.6010102@zytor.com> (raw)
In-Reply-To: <1364440182.2289.45.camel@leyfoon-vm>
On 03/27/2013 08:09 PM, Ley Foon Tan wrote:
> Need advise regarding the generic syscall ABI support.
>
> We are planning to upstream our Nios II kernel (arch/nios2) to mainline.
> But it doesn't support generic syscall ABI yet (It requires an updated
> Glibc port as well).
>
> The question is, is it a requirement for new arch to support generic
> syscall ABI when upstreaming? Can we upstream a non-generic syscall ABI
> first and migrate to generic syscall ABI in future?
> Thanks.
>
> Regards
> LFTAN
>
That would be extremely difficult.
In general, you should use the generic ABI for a new port unless you
have *very* strong and convincing reasons not to.
Given how long the Nios2 port has been in upstreaming (unfortunate, I
like to play with FPGAs ;) it seems worthwhile to adjust it before
pushing it.
-hpa
next prev parent reply other threads:[~2013-03-28 5:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-28 3:09 Generic syscall ABI support Ley Foon Tan
2013-03-28 5:35 ` H. Peter Anvin [this message]
2013-03-28 7:44 ` Arnd Bergmann
2013-03-28 8:32 ` Ley Foon Tan
2013-03-28 10:40 ` Arnd Bergmann
2013-03-28 11:30 ` Ley Foon Tan
2013-03-28 11:30 ` Ley Foon Tan
2013-03-28 11:42 ` Arnd Bergmann
2013-03-29 4:41 ` Rob Landley
2013-03-29 4:41 ` Rob Landley
2013-03-29 4:53 ` H. Peter Anvin
2013-03-29 9:49 ` Ley Foon Tan
2013-03-29 10:42 ` Arnd Bergmann
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=5153D698.6010102@zytor.com \
--to=hpa@zytor.com \
--cc=arnd@arndb.de \
--cc=lftan@altera.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).