From: "H. Peter Anvin" <hpa@zytor.com>
To: Al Viro <viro@ftp.linux.org.uk>
Cc: akpm@osdl.org, torvalds@osdl.org, klibc@zytor.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [klibc] Re: Merge strategy for klibc
Date: Mon, 20 Mar 2006 13:17:13 -0800 [thread overview]
Message-ID: <441F1BD9.9010008@zytor.com> (raw)
In-Reply-To: <20060320202224.GE27946@ftp.linux.org.uk>
Al Viro wrote:
> On Mon, Mar 20, 2006 at 11:54:01AM -0800, H. Peter Anvin wrote:
>
>>Okay, as of this point, I think klibc is in quite good shape; my
>>testing so far is showing that it can be used as a drop-in replacement
>>for the kernel root-mounting code.
>>
>>That being said, there is guaranteed to be breakage, for two reasons:
>>
>>a. There are several architectures which don't have klibc ports yet.
>> Since I don't have access to them, I can't really do them, either.
>> It's usually a matter of an afternoon or less to port klibc to a
>> new architecture, though, if you have a working development
>> environment for it.
>
> Which ones?
>
This is the status of architectures in klibc, at least as far as I know.
Note that 64-bit architectures which have 32-bit fallback modes (e.g.
MIPS) can use the 32-bit klibc if applicable.
alpha: Working
arm-thumb: Untested
arm: Working
arm26: Not yet ported
cris: Working
h8300: Not yet ported
i386: Working
ia64: Working
m32r: Untested
m68k: Not yet ported
mips: Working
mips64: Not yet ported
parisc: Working
parisc64: Not yet ported
ppc: Working
ppc64: Working
s390: Working static, shared untested
s390x: Working
sh: Untested
sh64: Not yet ported
sparc: Working
sparc64: Untested
v850: Not yet ported
x86-64: Working
xtensa: Not yet ported
-hpa
next prev parent reply other threads:[~2006-03-20 21:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-20 19:54 Merge strategy for klibc H. Peter Anvin
2006-03-20 20:19 ` Jan-Benedict Glaw
2006-03-20 21:24 ` H. Peter Anvin
2006-03-20 20:22 ` Al Viro
2006-03-20 21:17 ` H. Peter Anvin [this message]
2006-03-20 20:54 ` Ingo Oeser
2006-03-20 22:09 ` Roman Zippel
2006-03-22 0:27 ` H. Peter Anvin
2006-03-22 14:47 ` Antonio Vargas
2006-03-22 16:11 ` H. Peter Anvin
2006-03-21 12:39 ` Michael Tokarev
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=441F1BD9.9010008@zytor.com \
--to=hpa@zytor.com \
--cc=akpm@osdl.org \
--cc=klibc@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=viro@ftp.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.