linux/poky.git/meta/recipes-bsp/formfactor, branch master

The poky repository master branch is no longer being updated.

2025-11-07T13:31:53+00:00

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

meta: set S from UNPACKDIR in recipes that use only local files

2025-06-20T11:07:26+00:00

There is no need to have two assignments; also setting S from UNPACKDIR (and not vice versa) is more logical as unpack task comes first, and tasks that come after unpack use S to access unpack results. Also adjust reference test data in selftest/recipeutils to reflect changes in test recipes. (From OE-Core rev: f64b7e5fb3181734c8dde87b27e872a026261a74) Signed-off-by: Alexander Kanavin Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

formfactor: add support for qemuriscv64 and qemuriscv32

2025-01-03T11:05:03+00:00

Add machine config files for qemuriscv64 and qemuriscv32. Fixes [YOCTO #15427]. (From OE-Core rev: ec01090759677f8b69352c56aa29940314ca73e7) Signed-off-by: Maxin John Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

recipes: Switch away from S = WORKDIR

2024-05-21T11:08:04+00:00

Where recipes use S = ${WORKDIR}, change them to set UNPACKDIR to a subdir of WORKDIR and make S point at this instead. I've chosen not to force S into any standard UNPACKDIR we may pick in future just so the S = UNPACKDIR case is clearly visible by the directory naming under WORKDIR as that should aid usability. (From OE-Core rev: d9328e3b0b062f0621de3d114584b44f384a1c02) Signed-off-by: Richard Purdie

recipes: Drop remaining PR values from recipes

2023-09-22T06:45:17+00:00

We've been removing PR values from recipes at upgrade time for a while. In general anyone maintaining a binary distro would end up having to curate these themselves so the values in OE-Core aren't really that useful anymore. In many ways it makes sense to clear out the remaining ones (which are mostly for 'config' recipes that are unlikely to increase in PV) and leave a clean slate for anyone implementing a binary distro config. References are left in meta-selftest since the tests there do involve them and their removal upon upgrade. (From OE-Core rev: d4c346e8ab8f3cae25d1b01c7331ed9f6d4f96ef) Signed-off-by: Richard Purdie

formfactor: Add machine config for qemuppc64

2021-03-11T14:00:36+00:00

(From OE-Core rev: 13bc8fa9d7ba8c2bf8c7167d0cf959273997f78f) Signed-off-by: Khem Raj Signed-off-by: Richard Purdie

meta: add missing descriptions and homepage in bsp

2019-09-16T22:02:45+00:00

(From OE-Core rev: ec4fdfcc7bcbc9bb92e2f33b37cc8c99bf1b6822) Signed-off-by: Maxime Roussin-Bélanger Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

Remove $COREBASE/LICENSE from LIC_FILES_CHKSUM

2016-10-28T15:15:18+00:00

Several recipes reference the LICENSE file in their LIC_FILES_CHKSUM variable as ${COREBASE}/LICENSE. This forces distribution providers to keep this file verbatim or to overload the affected recipes. The section "Moving to the Yocto Project 1.6 Release" in the Yocto manual suggests removing the LICENSE file where possible. Remove LICENSE in cases where COPYING.MIT is also given and replace LICENSE with COPYING.MIT if the former was the only entry. All modified recipes specify LICENSE = "MIT" and none of the in-tree files specify a different license either. As the packages do not change (the license files are not contained in them), do not increase PR. (From OE-Core rev: 0059e0661826c857a07c862bcb46162671e0e330) Signed-off-by: Olaf Mandel Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

formfactor: assume a keyboard is plugged in

2016-03-07T00:11:38+00:00

A sensible assumption is that BSPs have a USB keyboard and mouse connected unless told otherwise, so flip the logic in the formfactor config script that previously assumed that a keyboard was not connected by default. [ YOCTO #9174 ] (From OE-Core rev: a82ce3e477a475dccea3837eabacd9e93b873ee6) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

formfactor: add machconfig for qemumips64

2016-02-04T23:39:01+00:00

We need machconfig file to automatically choose between physical and virtual keyboards. [YOCTO #9027] (From OE-Core rev: cfe08b474ef46dccba4ed09a998c6f33426f1b3d) Signed-off-by: Maxin B. John Signed-off-by: Ross Burton Signed-off-by: Richard Purdie