diff options
| author | Richard Purdie <richard.purdie@linuxfoundation.org> | 2025-11-07 13:31:53 +0000 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2025-11-07 13:31:53 +0000 |
| commit | 8c22ff0d8b70d9b12f0487ef696a7e915b9e3173 (patch) | |
| tree | efdc32587159d0050a69009bdf2330a531727d95 /meta/conf/machine/include/arm/README | |
| parent | d412d2747595c1cc4a5e3ca975e3adc31b2f7891 (diff) | |
| download | poky-8c22ff0d8b70d9b12f0487ef696a7e915b9e3173.tar.gz | |
The poky repository master branch is no longer being updated.
You can either:
a) switch to individual clones of bitbake, openembedded-core, meta-yocto and yocto-docs
b) use the new bitbake-setup
You can find information about either approach in our documentation:
https://docs.yoctoproject.org/
Note that "poky" the distro setting is still available in meta-yocto as
before and we continue to use and maintain that.
Long live Poky!
Some further information on the background of this change can be found
in: https://lists.openembedded.org/g/openembedded-architecture/message/2179
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/conf/machine/include/arm/README')
| -rw-r--r-- | meta/conf/machine/include/arm/README | 40 |
1 files changed, 0 insertions, 40 deletions
diff --git a/meta/conf/machine/include/arm/README b/meta/conf/machine/include/arm/README deleted file mode 100644 index c5637798e6..0000000000 --- a/meta/conf/machine/include/arm/README +++ /dev/null | |||
| @@ -1,40 +0,0 @@ | |||
| 1 | 2012/03/30 - Mark Hatle <mark.hatle@windriver.com> | ||
| 2 | - Initial Revision | ||
| 3 | |||
| 4 | The ARM architecture definitions are split among a number of files. | ||
| 5 | The primary definitions for the variables are handled by the core | ||
| 6 | arch-arm.inc file. | ||
| 7 | |||
| 8 | TUNE_ARCH is set to either "arm" or "armeb" depending on the value | ||
| 9 | of the existence of the "bigendian" feature in a given tune. | ||
| 10 | |||
| 11 | A small set of ARM specific variables have been defined to allow | ||
| 12 | TUNE_PKGARCH to be automatically defined. Optimized tunings must NOT | ||
| 13 | change the definiton of TUNE_PKGARCH. TUNE_PKGACH:tune-<tune> will be | ||
| 14 | ignored. The format of the package arch is enforced by the TUNE_PKGARCH | ||
| 15 | default. The format must be of the form: | ||
| 16 | <armversion>[t][e][hf][b][-vfp][-neon] | ||
| 17 | |||
| 18 | TUNE_PKGARCH is defined as: | ||
| 19 | ${ARMPKGARCH}${ARMPKGSFX_THUMB}${ARMPKGSFX_DSP}${ARMPKGSFX_EABI}${ARMPKGSFX_ENDIAN}${ARMPKGSFX_FPU} | ||
| 20 | |||
| 21 | ARMPKGARCH - This is the core package arch component specified by each | ||
| 22 | tuning. This is the primary identifier of a tuning. Usual values are: | ||
| 23 | arm, armv4, armv5, armv6, armv7a, etc. | ||
| 24 | |||
| 25 | ARMPKGSFX_THUMB - This is the thumb specific suffix. Curently it is | ||
| 26 | defined in feature-arm-thumb.inc. | ||
| 27 | |||
| 28 | ARMPKGSFX_DSP - This is the DSP specific suffix. Currently this is set | ||
| 29 | to 'e' when on armv5 and the dsp feature is enabled. | ||
| 30 | |||
| 31 | ARMPKGSFX_EABI - This is the eabi specific suffix. There are currently | ||
| 32 | two defined ABIs specificed, standard EABI and Hard Float (VFP) EABI. | ||
| 33 | When the callconvention-hard is enabled, "hf" is specified, otherwise it | ||
| 34 | is blank. | ||
| 35 | |||
| 36 | ARMPKGSFX_ENDIAN - This is the endian specific suffix. It is defined in | ||
| 37 | the core arch-arm.inc file. | ||
| 38 | |||
| 39 | ARMPKGSFX_FPU - This is the FPU specific suffix. The suffix indicates | ||
| 40 | specific FPU optimizations. 'vfp' and 'neon' are both defined. | ||
