summaryrefslogtreecommitdiffstats
path: root/scripts/tune/env.fake-arm1176jz-s.armv4tb
blob: c95cbf3eebfae742b407d8f95ec5fdb157be9288 (plain)
1
2
3
4
5
6
7
PACKAGE_ARCHS="all any noarch armeb armv4b armv4tb fake_arm1176jz_s"
TUNE_CCARGS=" -march=armv4t -marm"
TUNE_CCARGS_MFLOAT=""
TUNE_CCARGS_MFPU=""
TUNE_FEATURES="arm armv4 thumb bigendian"
TUNE_PKGARCH="armv4b"
export CC="armeb-oe-linux-gnueabi-gcc  -march=armv4t -marm --sysroot=SYSROOT"
l information on the specifics of hardware that Poky supports is available in README.hardware. Further hardware support can easily be added in the form of layers which extend the systems capabilities in a modular way. As an integration layer Poky consists of several upstream projects such as BitBake, OpenEmbedded-Core, Yocto documentation and various sources of information e.g. for the hardware support. Poky is in turn a component of the Yocto Project. The Yocto Project has extensive documentation about the system including a reference manual which can be found at: http://yoctoproject.org/documentation OpenEmbedded-Core is a layer containing the core metadata for current versions of OpenEmbedded. It is distro-less (can build a functional image with DISTRO = "nodistro") and contains only emulated machine support. For information about OpenEmbedded, see the OpenEmbedded website: http://www.openembedded.org/ Where to Send Patches ===================== As Poky is an integration repository, patches against the various components should be sent to their respective upstreams. bitbake: bitbake-devel@lists.openembedded.org meta-yocto: poky@yoctoproject.org Most everything else should be sent to the OpenEmbedded Core mailing list. If in doubt, check the oe-core git repository for the content you intend to modify. Before sending, be sure the patches apply cleanly to the current oe-core git repository. openembedded-core@lists.openembedded.org Note: The scripts directory should be treated with extra care as it is a mix of oe-core and poky-specific files.