summaryrefslogtreecommitdiffstats
path: root/meta/conf/machine
diff options
context:
space:
mode:
Diffstat (limited to 'meta/conf/machine')
-rw-r--r--meta/conf/machine/include/README88
1 files changed, 44 insertions, 44 deletions
diff --git a/meta/conf/machine/include/README b/meta/conf/machine/include/README
index e4b59c9566..65d09428a8 100644
--- a/meta/conf/machine/include/README
+++ b/meta/conf/machine/include/README
@@ -1,27 +1,27 @@
12012/03/30 - Mark Hatle <mark.hatle@windriver.com> 12012/03/30 - Mark Hatle <mark.hatle@windriver.com>
2 - Initial Revision 2 - Initial Revision
3 3
4The individual CPU, and ABI tunings are contained in this directory. A 4The individual CPU, and ABI tunings are contained in this directory. A
5number of local and global variables are used to control the way the 5number of local and global variables are used to control the way the
6tunings are setup and how they work together to specify an optimized 6tunings are setup and how they work together to specify an optimized
7configuration. 7configuration.
8 8
9The following is brief summary of the generic components that are used 9The following is brief summary of the generic components that are used
10in these tunings. 10in these tunings.
11 11
12AVAILTUNES - This is a list of all of the tuning definitions currently 12AVAILTUNES - This is a list of all of the tuning definitions currently
13available in the system. Not all tunes in this list may be compatible 13available in the system. Not all tunes in this list may be compatible
14with the machine configuration, or each other in a multilib 14with the machine configuration, or each other in a multilib
15configuration. Each tuning file can add to this list using "+=", but 15configuration. Each tuning file can add to this list using "+=", but
16should never replace the list using "=". 16should never replace the list using "=".
17 17
18DEFAULTTUNE - This specifies the tune to use for a particular build. 18DEFAULTTUNE - This specifies the tune to use for a particular build.
19Each tune should specify a reasonable default, which can be overriden by 19Each tune should specify a reasonable default, which can be overriden by
20a machine or multilib configuration. The specified tune must be listed 20a machine or multilib configuration. The specified tune must be listed
21in the AVAILTUNES. 21in the AVAILTUNES.
22 22
23TUNEVALID[feature] - The <feature> is defined with a human readable 23TUNEVALID[feature] - The <feature> is defined with a human readable
24explanation for what it does. All architectural, cpu, abi, etc tuning 24explanation for what it does. All architectural, cpu, abi, etc tuning
25features must be defined using TUNEVALID. 25features must be defined using TUNEVALID.
26 26
27TUNECONFLICTS[feature] - A list of features which conflict with <feature>. 27TUNECONFLICTS[feature] - A list of features which conflict with <feature>.
@@ -31,51 +31,51 @@ tuning ends up with features which conflict with each other.
31TUNE_FEATURES - This is automatically defined as TUNE_FEATURES_tune-<tune>. 31TUNE_FEATURES - This is automatically defined as TUNE_FEATURES_tune-<tune>.
32See TUNE_FEATURES_tune-<tune> for more information. 32See TUNE_FEATURES_tune-<tune> for more information.
33 33
34TUNE_FEATURES_tune-<tune> - Specify the features used to describe a 34TUNE_FEATURES_tune-<tune> - Specify the features used to describe a
35specific tune. This is a list of features that a tune support, each 35specific tune. This is a list of features that a tune support, each
36feature must be in the TUNEVALID list. Note: the tune and a given 36feature must be in the TUNEVALID list. Note: the tune and a given
37feature name may be the same, but they have different purposes. Only 37feature name may be the same, but they have different purposes. Only
38features may be used to change behavior, while tunes are used to 38features may be used to change behavior, while tunes are used to
39describe an overall set of features. 39describe an overall set of features.
40 40
41ABIEXTENSION - An ABI extension may be specified by a specific feature 41ABIEXTENSION - An ABI extension may be specified by a specific feature
42or other tuning setting, such as TARGET_FPU. Any ABI extensions either 42or other tuning setting, such as TARGET_FPU. Any ABI extensions either
43need to be defined in the architectures base arch file, i.e. 43need to be defined in the architectures base arch file, i.e.
44ABIEXTENSION = "eabi" in the arm case, or appended to in specific tune 44ABIEXTENSION = "eabi" in the arm case, or appended to in specific tune
45files with a ".=". Spaces are not allowed in this variable. 45files with a ".=". Spaces are not allowed in this variable.
46 46
47TUNE_CCARGS - Setup the cflags based on the TUNE_FEATURES settings. 47TUNE_CCARGS - Setup the cflags based on the TUNE_FEATURES settings.
48These should be additive when defined using "+=". All items in this 48These should be additive when defined using "+=". All items in this
49list should be dynamic! i.e. 49list should be dynamic! i.e.
50${@bb.utils.contains("TUNE_FEATURES", "feature", "cflag", "!cflag", d)} 50${@bb.utils.contains("TUNE_FEATURES", "feature", "cflag", "!cflag", d)}
51 51
52TUNE_ARCH - The GNU canonical arch for a specific architecture. i.e. 52TUNE_ARCH - The GNU canonical arch for a specific architecture. i.e.
53arm, armeb, mips, mips64, etc. This value is by bitbake to setup 53arm, armeb, mips, mips64, etc. This value is by bitbake to setup
54configure. TUNE_ARCH definitions are specific to a given architecture. 54configure. TUNE_ARCH definitions are specific to a given architecture.
55They may be a single static definitions, or may be dynamically adjusted. 55They may be a single static definitions, or may be dynamically adjusted.
56See each architectures README for details for that CPU family. 56See each architectures README for details for that CPU family.
57 57
58TUNE_PKGARCH - The package architecture used by the packaging systems to 58TUNE_PKGARCH - The package architecture used by the packaging systems to
59define the architecture, abi and tuning of a particular package. 59define the architecture, abi and tuning of a particular package.
60Similarly to TUNE_ARCH, the definition of TUNE_PKGARCH is specific to 60Similarly to TUNE_ARCH, the definition of TUNE_PKGARCH is specific to
61each architecture. See each architectures README for details for that 61each architecture. See each architectures README for details for that
62CPU family. 62CPU family.
63 63
64PACKAGE_EXTRA_ARCHS - Lists all runtime compatible package 64PACKAGE_EXTRA_ARCHS - Lists all runtime compatible package
65architectures. By default this is equal to 65architectures. By default this is equal to
66PACKAGE_EXTRA_ARCHS_tune-<tune>. If an architecture deviates from the 66PACKAGE_EXTRA_ARCHS_tune-<tune>. If an architecture deviates from the
67default it will be listed in the architecture README. 67default it will be listed in the architecture README.
68 68
69PACKAGE_EXTRA_ARCHS_tune-<tune> - List all of the package architectures 69PACKAGE_EXTRA_ARCHS_tune-<tune> - List all of the package architectures
70that are compatible with this specific tune. The package arch of this 70that are compatible with this specific tune. The package arch of this
71tune must be in the list. 71tune must be in the list.
72 72
73TARGET_FPU - The FPU setting for a given tune, hard (generate floating 73TARGET_FPU - The FPU setting for a given tune, hard (generate floating
74point instructions), soft (generate internal gcc calls), "other" 74point instructions), soft (generate internal gcc calls), "other"
75architecture specific floating point. This is synchronized with the 75architecture specific floating point. This is synchronized with the
76compiler and other toolchain items. This should be dynamically 76compiler and other toolchain items. This should be dynamically
77configured in the same way that TUNE_CCARGS is. 77configured in the same way that TUNE_CCARGS is.
78 78
79BASE_LIB_tune-<tune> - The "/lib" location for a specific ABI. This is 79BASE_LIB_tune-<tune> - The "/lib" location for a specific ABI. This is
80used in a multilib configuration to place the libraries in the correct, 80used in a multilib configuration to place the libraries in the correct,
81non-conflicting locations. 81non-conflicting locations.