aboutsummaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorGravatar Eric Andersen <andersen@codepoet.org>2004-09-02 23:03:25 +0000
committerGravatar Eric Andersen <andersen@codepoet.org>2004-09-02 23:03:25 +0000
commit45a0513a64f10b4d437e5b261f6b53f8e75e064b (patch)
treeb5a8bdcf732f90833c700d128fa4ed3133d84ffc /README
parent192c35f6eb2bb85e28c697a45c7d80a43ec6e743 (diff)
downloadbusybox-45a0513a64f10b4d437e5b261f6b53f8e75e064b.tar.gz
busybox-45a0513a64f10b4d437e5b261f6b53f8e75e064b.tar.bz2
Based on patches from Mike Frysinger, add insmod support for
sparc and ia64 (itanium). Also, reorganize the insmod architecture support code to be alphasorted and less messy. Update the readme to list current insmod arch support.
Diffstat (limited to 'README')
-rw-r--r--README17
1 files changed, 9 insertions, 8 deletions
diff --git a/README b/README
index aa58cd1b9..72a560c38 100644
--- a/README
+++ b/README
@@ -33,23 +33,24 @@ Supported architectures:
BusyBox in general will build on any architecture supported by gcc. It has
a few specialized features added for __sparc__ and __alpha__. insmod
- functionality is currently limited to x86, ARM, SH3/4, powerpc, m68k,
- MIPS, cris, and v850e.
+ functionality is currently limited to ARM, CRIS, H8/300, x86, ia64,
+ x86_64, m68k, MIPS, PowerPC, S390, SH3/4/5, Sparc, v850e, and x86_64
+ for 2.4.x kernels. For 2.6.x kernels
Supported C Libraries:
- glibc-2.0.x, glibc-2.1.x, glibc-2.2.x, glibc-2.3.x, uClibc. People
- are looking at newlib and diet-libc, but consider them unsupported,
- untested, or worse. Linux-libc5 is no longer supported -- you
- should probably use uClibc instead if you want a small C library.
+ uClibc and glibc are supported. People have been looking at newlib and
+ diet-libc, but they are currently considered unsupported, untested, or
+ worse. Linux-libc5 is no longer supported -- you should probably use uClibc
+ instead if you want a small C library.
Supported kernels:
Full functionality requires Linux 2.2.x or better. A large fraction of the
code should run on just about anything. While the current code is fairly
Linux specific, it should be fairly easy to port the majority of the code
- to, say, FreeBSD or Solaris, or Mac OS X, or even Windows (if you are into
- that sort of thing).
+ to support, say, FreeBSD or Solaris, or Mac OS X, or even Windows (if you
+ are into that sort of thing).
----------------