# HG changeset patch # User Rob Landley # Date 1237408344 18000 # Node ID c796d3ebf1794ab78e209ef558ab8340243e5562 # Parent 02e2c17f035cd0f9e15b7dca99bb50f4a6f9d2e2 Fluff out docs a bit (miniconfig: what hardware does qemu need?) diff -r 02e2c17f035c -r c796d3ebf179 www/documentation.html --- a/www/documentation.html Wed Mar 18 13:01:55 2009 -0500 +++ b/www/documentation.html Wed Mar 18 15:32:24 2009 -0500 @@ -1828,6 +1828,21 @@ to come up with your own configuration for actual target hardware, feel free.

+

The starting point for kernel configs is generally one of the defconfig +files from the Linux kernel source code, usually at +"arch/$ARCH/configs/*_defconfig". Copy that to .config at the top of the +kernel source, run menuconfig to edit it, then shrink it into a miniconfig.

+ +

Kernels to run system images under qemu generally require the following +hardware: serial port (for /dev/console), hard drive (for hda and hdb images), +network card (for distcc), and a persistent realtime clock (make gets unhappy +if source files are newer than the current time). The ability to address +at least 512 megs of memory is also nice, although some targets (such as mips) +are limited to less than that by the hardware. The "qemu-system-$ARCH -M ?" +and "qemu-system-$ARCH -cpu ?" options may be informative here, also +the QEMU System +emulator for non PC targets documentation.

+

$ARCH/miniconfig-uClibc

Just like the Linux kernel, uClibc needs a .config file to build, and @@ -1838,7 +1853,9 @@ contents.

Most of each miniconfig-uClibc is identical from platform to platform. -At some point in the future this boilerplate might be factored out into +Usually only the "Target Architecture" changes (and occasionally an entry +or two out of Target Architecture Features and Options). At some point +in the future the rest of the uClibc configuration might be factored out into a common file, but so far removing the duplication hasn't been worth the extra complexity.