view www/index.html @ 414:42faea138734

Save the expanded .config files for uClibc and linux in each build/temp-$ARCH dir after the build.
author Rob Landley <rob@landley.net>
date Sun, 19 Oct 2008 02:47:44 -0500
parents 3eeb77934265
children 4a140cf3cfb2
line wrap: on
line source

<!--#include file="header.html" -->


<b><h1><a href=about.html>What is Firmware Linux?</a></h1></b>

<blockquote>
<p>Firmware Linux is an embedded Linux build system, designed to eliminate
the need for cross compiling.</p>

<p>The build system is a series of bash scripts which create a small native
Linux development environment for each target, runnable on real hardware or
under emulators such as <a href=http://qemu.org>QEMU</a>.</p>

<p>Currently supported targets include arm, mips, powerpc, and x86, x86-64.
Partial support is available for sparc, sh4, and m68k.</p>

<p>For more information, see <a href=about.html>the about page</a>.</p>
</blockquote>

<b><h1><a href=downloads>Downloading Firmware Linux</a></h1></b>

<blockquote>
<b><h2><a href=downloads>Source Code</a></h2></b>
<p>The current source tarball is
<a href=downloads/firmware-0.9.0.tar.bz2>Firmware Linux version 0.9.0</a>.
This is the series of shell scripts you run to create the various binary
images.  See the <a href=downloads/README>README</a> for usage instructions,
and the <a href=news.html>release notes</a>.</p>

<p>Several <a href=downloads/binaries>prebuilt binary images</a>
are available, based on the current Firmware Linux release.</p>

<b><h2><a href=downloads/binaries/system-image>System Images</a></h2></b>

<p>System images provide a complete native development environment, based
on the following packages:</p>

<ul>
<li>Linux 2.6.26.2</li>
<li>uClibc 0.9.29</li>
<li>BusyBox 1.11.1</li>
<li>binutils 2.18</li>
<li>gcc 4.1.2</li>
<li>make 3.8.1</li>
<li>bash 2.05b</li>
</ul>

<p>(The build also uses the toybox 0.0.6 and distcc 2.18.3 packages, but does
not depend on them.)</p>

<p>System image tarballs contain an ext2 root filesystem image and a kernel
configured to boot under the emulator QEMU.  Use the "./run-emulator.sh"
script to use qemu to emulate the appropriate target system, giving you a
shell prompt within the native development environment.  (Type "exit" when
finished.)</p>

<b><h2><a href=downloads/binaries/mini-native>Root filesystem tarballs</a></h2></b>

<p>If you prefer to package your own filesystem images, or use QEMU's
application emulation mode, you can download each target's root filesystem
packaged in a tarball.</p>

<b><h2><a href=downloads/binaries/cross-compiler>Cross compilers</h2></a></b>

<p>Prebuilt binary cross compilers for use on <a href=downloads/binaries/cross-compiler/host-i686>i686</a> or <a href=downloads/binaries/cross-compiler/host-x86_64>x86-64</a> hosts.</p>
</blockquote>

<b><h1><a href=/hg/firmware>Development</a></h1></b>

<p>The project maintains a <a href=/hg/firmware>development repository</a>
using the Mercurial source control system.  This includes RSS feeds for
<a href=http://127.0.0.1/hg/hgwebdir.cgi/firmware/rss-log>each checkin</a>
and for <a href=http://127.0.0.1/hg/hgwebdir.cgi/firmware/rss-tags>new releases</a>.</p>

<p>Questions about Firmware Linux should be addressed to the project's
<a href=http://www2.them.com:8080/cgi-bin/mailman/listinfo/firmware>mailing
list</a>, the IRC channel #firmware on irc.freenode.org.  The project
maintainer's <a href=/notes.html>blog</a> often includes notes about
ongoing Firmware Linux development.</p>

<!--#include file="footer.html" -->