diff -r 55fbab1b4f94 -r 9fb0f81b4416 docs/overview.txt --- a/docs/overview.txt Fri Oct 03 20:00:36 2008 +0000 +++ b/docs/overview.txt Sun Oct 05 15:32:00 2008 +0000 @@ -541,20 +541,14 @@ - a human-readable name, in lower case letters, with numbers as appropriate. The underscore is allowed; space and special characters are not. Eg.: arm, x86_64 - - a directory in "config/arch/" named after the architecture, with the same - letters as above. Eg.: arch/arm, arch/x86_64 - This directory contains the following files, and only those files: - - a configuration file in kconfig syntax, named "config.in", which shall - follow the API defined below. - Eg.: config/arch/arm/config.in - - a function script in bash-3.0 syntax, named "functions", which shall - follow the API defined below. - Eg.: config/arch/arm/functions - - an optional file, named "experimental" (in lower case!), which, if it - is present, means that support for this architecture is EXPERIMENTAL. - Eg.: config/arch/arm/experimental + - a file in "config/arch/", named after the architecture's name, and suffixed + with ".in". + Eg.: config/arch/arm.in + - a file in "scripts/build/arch/", named after the architecture's name, and + suffixed with ".sh". + Eg.: scripts/build/arch/arm.sh -The "config.in" file API: +The architecture's ".in" file API: > the config option "ARCH_%arch%" (where %arch% is to be replaced with the actual architecture name). That config option must have *neither* a type, *nor* a prompt! Also, it can @@ -584,7 +578,7 @@ this, as the architecture name was written all upper case. However, the prefix is unique among architectures, and does not cause harm). -The "functions" file API: +The architecture's ".sh" file API: > the function "CT_DoArchValues" + parameters: none + environment: @@ -656,8 +650,8 @@ - default to: - all empty -You can have a look at "config/arch/arm/" for an quite complete example of -what an actual architecture description looks like. +You can have a look at "config/arch/arm.in" and "scripts/build/arch/arm.sh" for +a quite complete example of what an actual architecture description looks like. Kernel specific | ----------------+ @@ -760,7 +754,7 @@ any name-clashing. You can have a look at "config/kernel/linux.in" and "scripts/build/kernel/linux.sh" -as an example of what a complex kernel description looks like, +as an example of what a complex kernel description looks like. Adding a new version of a component | ------------------------------------+