Mercurial > hg > aboriginal
changeset 1371:6d0b8eacd14e
Merge description files into settings files as $DESCRIPTION entry.
author | Rob Landley <rob@landley.net> |
---|---|
date | Sat, 11 Jun 2011 22:43:24 -0500 |
parents | 3bd113bd3722 |
children | 6f9d21d978b4 |
files | sources/targets/armv4eb/description sources/targets/armv4eb/settings sources/targets/armv4l/description sources/targets/armv4l/settings sources/targets/armv4tl/description sources/targets/armv4tl/settings sources/targets/armv5l/description sources/targets/armv5l/settings sources/targets/armv6l/description sources/targets/armv6l/settings sources/targets/hw-tct-hammer/description sources/targets/hw-tct-hammer/settings sources/targets/hw-uml/description sources/targets/hw-wrt610n/description sources/targets/hw-wrt610n/settings sources/targets/i486/description sources/targets/i486/settings sources/targets/i586/description sources/targets/i586/settings sources/targets/i686/description sources/targets/i686/settings sources/targets/m68k/description sources/targets/m68k/settings sources/targets/mips/description sources/targets/mips/settings sources/targets/mips64/description sources/targets/mips64/settings sources/targets/mipsel/description sources/targets/mipsel/settings sources/targets/powerpc-440fp/description sources/targets/powerpc-440fp/settings sources/targets/powerpc/description sources/targets/powerpc/settings sources/targets/sh4/description sources/targets/sh4/settings sources/targets/sparc/description sources/targets/sparc/settings sources/targets/x86_64/description sources/targets/x86_64/settings |
diffstat | 39 files changed, 149 insertions(+), 109 deletions(-) [+] |
line wrap: on
line diff
--- a/sources/targets/armv4eb/description Fri Jun 10 21:10:37 2011 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,6 +0,0 @@ -ARM v4, big endian, soft float, OABI. - -Although arm processors can work with either endianness, most ARM boards are -wired little endian, so building big endian arm is fairly uncommon. The -ixp4xx, ixp2000, and ixp23xx are the only current Linux targets to support -big endian operation.
--- a/sources/targets/armv4eb/settings Fri Jun 10 21:10:37 2011 -0500 +++ b/sources/targets/armv4eb/settings Sat Jun 11 22:43:24 2011 -0500 @@ -1,3 +1,11 @@ +DESCRIPTION=" +ARM v4, big endian, soft float, OABI. + +Although arm processors can work with either endianness, most ARM boards are +wired little endian, so building big endian arm is fairly uncommon. The +ixp4xx, ixp2000, and ixp23xx Linux targets support big endian operation. +" + KARCH=arm KERNEL_PATH=arch/${KARCH}/boot/zImage GCC_FLAGS="--with-float=soft"
--- a/sources/targets/armv4l/description Fri Jun 10 21:10:37 2011 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,7 +0,0 @@ -ARM v4, little endian, soft float, OABI. - -This is an extremely generic arm image that should run on any arm hardware -still in use today (except ARMv7M, which is arm in name only). - -The downside is it uses the Old Application Binary Interface, described here: -http://www.linuxfordevices.com/c/a/Linux-For-Devices-Articles/Why-ARMs-EABI-matters/
--- a/sources/targets/armv4l/settings Fri Jun 10 21:10:37 2011 -0500 +++ b/sources/targets/armv4l/settings Sat Jun 11 22:43:24 2011 -0500 @@ -1,3 +1,16 @@ +DESCRIPTION=" +ARM v4, little endian, soft float, OABI. + +This is a generic low-end arm image that should run on any arm hardware +still in use today (except ARMv7M, which is arm in name only). + +The downside is it uses the Old Application Binary Interface, described here: +http://www.linuxfordevices.com/c/a/Linux-For-Devices-Articles/Why-ARMs-EABI-matters/ + +This instruction set cannot support EABI, which requies the Thumb extensions. +It's sort of the 80286 of the ARM world. +" + KARCH=arm KERNEL_PATH=arch/${KARCH}/boot/zImage GCC_FLAGS="--with-float=soft"
--- a/sources/targets/armv4tl/description Fri Jun 10 21:10:37 2011 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,5 +0,0 @@ -ARM v4, with thumb support, little endian, EABI, soft float. - -This is the lowest-end arm instruction set that can support EABI, the current -binary ABI documented by ARM. It's used used in 920t processors (such as the -OpenMoko Freerunner).
--- a/sources/targets/armv4tl/settings Fri Jun 10 21:10:37 2011 -0500 +++ b/sources/targets/armv4tl/settings Sat Jun 11 22:43:24 2011 -0500 @@ -1,3 +1,15 @@ +DESCRIPTION=" +ARM v4, with thumb support, little endian, EABI, soft float. + +This is the lowest-end arm instruction set that can support EABI, the current +binary ABI documented by ARM. It's used used in 920t processors (such as the +OpenMoko Freerunner). + +This is \"the i386 of ARM\", an extremely generic low-end arm image that +should run on any arm hardware still in use today (except ARMv7M, which +is arm in name only). +" + KARCH=arm KERNEL_PATH=arch/${KARCH}/boot/zImage GCC_FLAGS="--with-march=armv4t --with-float=soft"
--- a/sources/targets/armv5l/description Fri Jun 10 21:10:37 2011 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,5 +0,0 @@ -ARM v5, little endian, EABI with vector floating point (vfp). - -ARMv5 is to ARMv4 as pentium is to i486. Most modern arm hardware should be -able to run this, and hardware that supports the v5 instruction set should run -this about 25% faster than code compiled for v4.
--- a/sources/targets/armv5l/settings Fri Jun 10 21:10:37 2011 -0500 +++ b/sources/targets/armv5l/settings Sat Jun 11 22:43:24 2011 -0500 @@ -1,3 +1,11 @@ +DESCRIPTION=" +ARM v5, little endian, EABI with vector floating point (vfp). + +ARMv5 is the Pentium of the ARM world. Most modern arm hardware should be +able to run this, and hardware that supports the v5 instruction set should run +this about 25% faster than code compiled for v4. +" + KARCH=arm KERNEL_PATH=arch/${KARCH}/boot/zImage GCC_FLAGS="--with-march=armv5 --with-mfloat-abi=soft --with-mfp=vfp"
--- a/sources/targets/armv6l/description Fri Jun 10 21:10:37 2011 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,6 +0,0 @@ -ARM v6, little endian, EABI with vector floating point (vfp). - -This is a fairly recent ARM architecture (introduced 2001, actually shipped -silicon around 2003). This hardware can still run v4 and v5 instruction sets, -but v6 is targeted to the newer stuff and should run more efficiently (faster -prformance/better battery life).
--- a/sources/targets/armv6l/settings Fri Jun 10 21:10:37 2011 -0500 +++ b/sources/targets/armv6l/settings Sat Jun 11 22:43:24 2011 -0500 @@ -1,4 +1,11 @@ -# ARMv6 with vector floating point (vfp). +DESCRIPTION=" +ARM v6, little endian, EABI with vector floating point (vfp). + +The Pentium II of the ARM world: this architecture was introduced in 2001 +and actually shipped silicon around 2003. This hardware can still run v4 +and v5 instruction sets, but recompiling for armv6 should provide a +slight performance boost (and thus better battery life). +" KARCH=arm KERNEL_PATH=arch/${KARCH}/boot/zImage
--- a/sources/targets/hw-tct-hammer/description Fri Jun 10 21:10:37 2011 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,8 +0,0 @@ -# The Tin Can Tools hammer board - -An ARM920T system on a chip, with 32 megs DRAM and 16 megs flash, and several -integrated peripherals. - -See http://www.tincantools.com/product.php?productid=16133 for the hammer board -and http://www.tincantools.com/product.php?productid=16143 for the "nail -board" (a USB-powered mounting kit for the hammer).
--- a/sources/targets/hw-tct-hammer/settings Fri Jun 10 21:10:37 2011 -0500 +++ b/sources/targets/hw-tct-hammer/settings Sat Jun 11 22:43:24 2011 -0500 @@ -1,4 +1,11 @@ -# The Tin Can Tools Hammer board is an armv4l with a different kernel. - ARCH=armv4tl source "$CONFIG_DIR/$ARCH/settings" + +DESCRIPTION=" +The Tin Can Tools hammer board is an ARM920T system on a chip, with 32 megs +DRAM and 16 megs flash, and several integrated peripherals. + +See http://www.tincantools.com/product.php?productid=16133 for the hammer +board and http://www.tincantools.com/product.php?productid=16143 for the +\"nail board\" (a USB-powered mounting kit for the hammer). +"
--- a/sources/targets/hw-uml/description Fri Jun 10 21:10:37 2011 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,5 +0,0 @@ -User Mode Linux (based on i686) - -This is a Linux kernel built to run as a normal userspace process. It lets -you run vmlinux as an executable, with Linux acting as its own emulator -instead of using qemu.
--- a/sources/targets/hw-wrt610n/description Fri Jun 10 21:10:37 2011 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,11 +0,0 @@ -Linksys WRT610n. - -A small blue mips-based router. - -This doesn't actually work yet, because the kernel doesn't fully support this -hardware without more patches, and trx image packaging needs an additional -32 byte header before the router's installer and bootloader will accept it. - -TODO - -See http://www.linksysbycisco.com/US/en/products/WRT610N
--- a/sources/targets/hw-wrt610n/settings Fri Jun 10 21:10:37 2011 -0500 +++ b/sources/targets/hw-wrt610n/settings Sat Jun 11 22:43:24 2011 -0500 @@ -1,4 +1,16 @@ -# Include base architecture +DESCRIPTION=" +Linksys WRT610n. + +A small blue mips-based router. + +This doesn't actually work yet, because the kernel doesn't fully support this +hardware without more patches, and trx image packaging needs an additional +32 byte header before the router's installer and bootloader will accept it. + +TODO + +See http://www.linksysbycisco.com/US/en/products/WRT610N +" ARCH=mipsel source "$CONFIG_DIR/$ARCH/settings"
--- a/sources/targets/i486/description Fri Jun 10 21:10:37 2011 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,8 +0,0 @@ -An i486 based computer. - -Yes it's obsolete, but there are embedded processors that use it. The -existance of an FPU is assumed, even though some i486s don't have one. -This is simply coz i486s with no FPU are not of interest to me. Someone -else can fix that if they care. - -Produced and tested by David Seikel.
--- a/sources/targets/i486/settings Fri Jun 10 21:10:37 2011 -0500 +++ b/sources/targets/i486/settings Sat Jun 11 22:43:24 2011 -0500 @@ -1,3 +1,14 @@ +DESCRIPTION=" +An i486 based computer. + +Yes it's obsolete, but there are embedded processors that use it. The +existance of an FPU is assumed, even though some i486s don't have one. +This is simply coz i486s with no FPU are not of interest to me. Someone +else can fix that if they care. + +Produced and tested by David Seikel. +" + KARCH=i386 KERNEL_PATH=arch/${KARCH}/boot/bzImage BINUTILS_FLAGS=
--- a/sources/targets/i586/description Fri Jun 10 21:10:37 2011 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,5 +0,0 @@ -An i586 board, such as the original Pentium/Pentium Pro/Pentium II/Via Samuel - -This demonstrates how creating code which runs on the host can still be cross -compiling, because the target may only support a subset of the host's -instruction set.
--- a/sources/targets/i586/settings Fri Jun 10 21:10:37 2011 -0500 +++ b/sources/targets/i586/settings Sat Jun 11 22:43:24 2011 -0500 @@ -1,3 +1,12 @@ +DESCRIPTION=" +An i586 board, such as the original Pentium/Pentium Pro/Pentium II/Via Samuel + +This demonstrates how creating code which runs on the host can still be cross +compiling, because the target may only support a subset of the host's +instruction set. Thus target code runs on the host, but host code won't +run on the target, so you still can't afford to leak context. +" + KARCH=i386 KERNEL_PATH=arch/${KARCH}/boot/bzImage BINUTILS_FLAGS=
--- a/sources/targets/i686/description Fri Jun 10 21:10:37 2011 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,1 +0,0 @@ -Standard 32-bit x86 target, Pentium 3 or later.
--- a/sources/targets/i686/settings Fri Jun 10 21:10:37 2011 -0500 +++ b/sources/targets/i686/settings Sat Jun 11 22:43:24 2011 -0500 @@ -1,3 +1,5 @@ +DESCRIPTION="Standard 32-bit x86 target, Pentium 3 or later." + KARCH=i386 KERNEL_PATH=arch/${KARCH}/boot/bzImage BINUTILS_FLAGS=
--- a/sources/targets/m68k/description Fri Jun 10 21:10:37 2011 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,9 +0,0 @@ -Motorola 68000. - -This builds, but qemu can't run it yet. (The qemu m68k support is actually -only coldfire, an mmu-less subset of the m68k instruction set.) - -The aranym emulator might be able to run this (with a different kernel -configuration) but that emulator doesn't support serial consoles. - -TODO
--- a/sources/targets/m68k/settings Fri Jun 10 21:10:37 2011 -0500 +++ b/sources/targets/m68k/settings Sat Jun 11 22:43:24 2011 -0500 @@ -1,3 +1,13 @@ +DESCRIPTION=" +Motorola 68000. + +This builds, but qemu can't run it yet. (The qemu m68k support is actually +only coldfire, an mmu-less subset of the m68k instruction set.) + +The aranym emulator might be able to run this (with a different kernel +configuration) but that emulator doesn't support serial consoles. +" + KARCH=m68k KERNEL_PATH=vmlinux GCC_FLAGS= # "--with-float=soft"
--- a/sources/targets/mips/description Fri Jun 10 21:10:37 2011 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,1 +0,0 @@ -Mips r4k big endian.
--- a/sources/targets/mips/settings Fri Jun 10 21:10:37 2011 -0500 +++ b/sources/targets/mips/settings Sat Jun 11 22:43:24 2011 -0500 @@ -1,3 +1,5 @@ +DESCRIPTION="Mips r4k big endian." + KARCH=mips KERNEL_PATH=vmlinux BINUTILS_FLAGS=
--- a/sources/targets/mips64/description Fri Jun 10 21:10:37 2011 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,1 +0,0 @@ -64 bit big endian mips.
--- a/sources/targets/mips64/settings Fri Jun 10 21:10:37 2011 -0500 +++ b/sources/targets/mips64/settings Sat Jun 11 22:43:24 2011 -0500 @@ -1,3 +1,5 @@ +DESCRIPTION="64 bit big endian mips" + KARCH=mips KERNEL_PATH=vmlinux BINUTILS_FLAGS="--enable-64-bit-bfd"
--- a/sources/targets/mipsel/description Fri Jun 10 21:10:37 2011 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,1 +0,0 @@ -Mips r4k little endian
--- a/sources/targets/mipsel/settings Fri Jun 10 21:10:37 2011 -0500 +++ b/sources/targets/mipsel/settings Sat Jun 11 22:43:24 2011 -0500 @@ -1,3 +1,5 @@ +DESCRIPTION="Mips r4k little endian" + KARCH=mips KERNEL_PATH=vmlinux BINUTILS_FLAGS=
--- a/sources/targets/powerpc-440fp/description Fri Jun 10 21:10:37 2011 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,1 +0,0 @@ -Power PC 440, with hardware floating point.
--- a/sources/targets/powerpc-440fp/settings Fri Jun 10 21:10:37 2011 -0500 +++ b/sources/targets/powerpc-440fp/settings Sat Jun 11 22:43:24 2011 -0500 @@ -1,5 +1,7 @@ source "$CONFIG_DIR/powerpc/settings" +DESCRIPTION="Power PC 440, with hardware floating point." + CROSS_TARGET=powerpc-unknown-linux GCC_FLAGS="--with-cpu=440fp --with-tune=440fp ${GCC_FLAGS}" BINUTILS_FLAGS="--with-cpu=440fp --with-tune=440fp"
--- a/sources/targets/powerpc/description Fri Jun 10 21:10:37 2011 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,11 +0,0 @@ -Power PC, 32 bit - -Generic Power PC system, a basic unoptimized instruction set which -just about any powerpc should be able to run. - -The main exceptions are the 440 and 880 lines, which were stripped down -versions of the powerpc (created by IBM and Motorola, respectively) targetted -at battery powered devices such as cell phones. They do not support the entire -powerpc instruction set. (Alas, the two chose _different_ subsets, so they -don't run each other's code either. The 880 is mostly dead today, but the -440 is alive and well.)
--- a/sources/targets/powerpc/settings Fri Jun 10 21:10:37 2011 -0500 +++ b/sources/targets/powerpc/settings Sat Jun 11 22:43:24 2011 -0500 @@ -1,3 +1,17 @@ +DESCRIPTION=" +Power PC, 32 bit + +Generic Power PC system, a basic unoptimized instruction set which +just about any powerpc should be able to run. + +The main exceptions are the 440 and 880 lines, which were stripped down +versions of the powerpc (created by IBM and Motorola, respectively) targetted +at battery powered devices such as cell phones. They do not support the +entire powerpc instruction set. (Alas, the two chose _different_ subsets, so +they don't run each other's code either. These days the 880 is known as +PowerQuic.) +" + KARCH=powerpc KERNEL_PATH=vmlinux GCC_FLAGS=
--- a/sources/targets/sh4/description Fri Jun 10 21:10:37 2011 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,4 +0,0 @@ -The Super Hitachi processor is fairly popular in Japan, and winds up in things -like the Sega Dreamcast and automobile onboard computers. - -There's a wiki about it at http://linux-sh.org
--- a/sources/targets/sh4/settings Fri Jun 10 21:10:37 2011 -0500 +++ b/sources/targets/sh4/settings Sat Jun 11 22:43:24 2011 -0500 @@ -1,3 +1,11 @@ +DESCRIPTION=" +The SuperH processor was created by Hitachi and is mostly local to Japan. +It's been used in things like the Sega Dreamcast and automobile onboard +computers. + +There's a wiki about it at http://linux-sh.org. +" + KARCH=sh KERNEL_PATH=arch/${KARCH}/boot/zImage GCC_FLAGS= #"--with-cpu=m4-nofpu"
--- a/sources/targets/sparc/description Fri Jun 10 21:10:37 2011 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,7 +0,0 @@ -32-bit sparc - -Sparc was a risc processor design Sun Microsystems came up with to replace -m68k in their Unix workstations. With the advent of OpenSolaris and -x86-64, Fujitsu mainframes may now use more of it than they do. - -This has been broken for a couple years, and nobody's bothered to fix it.
--- a/sources/targets/sparc/settings Fri Jun 10 21:10:37 2011 -0500 +++ b/sources/targets/sparc/settings Sat Jun 11 22:43:24 2011 -0500 @@ -1,3 +1,13 @@ +DESCRIPTION=" +32-bit sparc + +Sparc was a risc processor design Sun Microsystems came up with to replace +m68k in their Unix workstations. With the advent of OpenSolaris and +x86-64, Fujitsu mainframes may now use more of it than they do. + +This has been broken for a couple years, and nobody's bothered to fix it. +" + # Originally contributed by Bertl. KARCH=sparc
--- a/sources/targets/x86_64/description Fri Jun 10 21:10:37 2011 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,3 +0,0 @@ -64-bit x86. - -Modern standard PC architecture. Runs i686 code as well.
--- a/sources/targets/x86_64/settings Fri Jun 10 21:10:37 2011 -0500 +++ b/sources/targets/x86_64/settings Sat Jun 11 22:43:24 2011 -0500 @@ -1,3 +1,9 @@ +DESCRIPTION=" +64-bit x86. + +Modern standard PC architecture. Runs i686 code as well. +" + KARCH=x86_64 KERNEL_PATH=arch/${KARCH}/boot/bzImage GCC_FLAGS=