Bruce Ashfield d616929413 linux-yocto/6.6: cfg: genericarm64 platform/peripheral support
Integrating the following commit(s) to linux-yocto/.:

1/12 [
    Author: Ross Burton
    Email: ross.burton@arm.com
    Subject: bsp/genericarm64: include .scc files instead of .cfg
    Date: Wed, 20 Mar 2024 19:42:09 +0000

    Some .cfg files were included accidentally, fix this.

    Signed-off-by: Ross Burton <ross.burton@arm.com>
    Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
]

2/12 [
    Author: Ross Burton
    Email: ross.burton@arm.com
    Subject: bsp/genericarm64: move CONFIG_PHYLINK under the right comment
    Date: Wed, 20 Mar 2024 19:42:10 +0000

    A bug in my annotation script meant this item ended up in the wrong place.

    Signed-off-by: Ross Burton <ross.burton@arm.com>
    Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
]

3/12 [
    Author: Bill Mills
    Email: bill.mills@linaro.org
    Subject: bsp/genericarm64: Automatically create /dev/i2c* devices
    Date: Wed, 20 Mar 2024 19:42:11 +0000

    With CONFIG_I2C_DEV=m you must modprobe that module in order to get the
    /dev nodes.  It is a small module (~8.5K) so just include it in.

    Signed-off-by: Bill Mills <bill.mills@linaro.org>
    Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
]

4/12 [
    Author: Ross Burton
    Email: ross.burton@arm.com
    Subject: bsp/genericarm64: enable hugetlbfs
    Date: Wed, 20 Mar 2024 19:42:12 +0000

    Signed-off-by: Ross Burton <ross.burton@arm.com>
    Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
]

5/12 [
    Author: Ross Burton
    Email: ross.burton@arm.com
    Subject: bsp/genericarm64: integrate the IMX clocks
    Date: Wed, 20 Mar 2024 19:42:13 +0000

    If these are kernel modules then there's a WARN_ON triggered when booted
    on IMX boards.

    Signed-off-by: Ross Burton <ross.burton@arm.com>
    Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
]

6/12 [
    Author: Ross Burton
    Email: ross.burton@arm.com
    Subject: bsp/genericarm64: enable more SPI controllers
    Date: Wed, 20 Mar 2024 19:42:14 +0000

    Signed-off-by: Ross Burton <ross.burton@arm.com>
    Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
]

7/12 [
    Author: Ross Burton
    Email: ross.burton@arm.com
    Subject: bsp/genericarm64: enable PHY subsystem
    Date: Wed, 20 Mar 2024 19:42:15 +0000

    Signed-off-by: Ross Burton <ross.burton@arm.com>
    Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
]

8/12 [
    Author: Ross Burton
    Email: ross.burton@arm.com
    Subject: bsp/genericarm64: enable USB On-The-Go and Gadget
    Date: Wed, 20 Mar 2024 19:42:16 +0000

    Signed-off-by: Ross Burton <ross.burton@arm.com>
    Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
]

9/12 [
    Author: Ross Burton
    Email: ross.burton@arm.com
    Subject: bsp/genericarm64: enable SATA
    Date: Wed, 20 Mar 2024 19:42:17 +0000

    SBCs don't tend to use SATA, but larger platforms will.

    Signed-off-by: Ross Burton <ross.burton@arm.com>
    Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
]

10/12 [
    Author: Ross Burton
    Email: ross.burton@arm.com
    Subject: bsp/genericarm64: support some i.MX8 boards
    Date: Wed, 20 Mar 2024 19:42:18 +0000

    Add more hardware enabling so that NXP i.MX8M boards boot successfully.

    Thanks to anton.antonov@arm.com for the options and testing.

    Signed-off-by: Ross Burton <ross.burton@arm.com>
    Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
]

11/12 [
    Author: Ross Burton
    Email: ross.burton@arm.com
    Subject: bsp/genericarm64: enable networking on Kontron KBox
    Date: Wed, 20 Mar 2024 19:42:19 +0000

    Thanks to anton.antonov@arm.com.

    Signed-off-by: Ross Burton <ross.burton@arm.com>
    Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
]

12/12 [
    Author: Ross Burton
    Email: ross.burton@arm.com
    Subject: bsp/genericarm64: enable Marvell ThunderX2 support
    Date: Wed, 20 Mar 2024 19:42:20 +0000

    Add the required options so that this BSP works on the Marvell ThunderX2.

    Thanks to anton.antonov@arm.com for the config and testing.

    Signed-off-by: Ross Burton <ross.burton@arm.com>
    Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
]

(From OE-Core rev: 18e696048cc3486c6cce600c5a2a27a887f558e1)

Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2024-03-23 10:18:20 +00:00
2024-02-19 11:34:33 +00:00
2021-07-19 18:07:21 +01:00
2023-10-19 11:31:13 +01:00

Poky

Poky is an integration of various components to form a pre-packaged build system and development environment which is used as a development and validation tool by the Yocto Project. It features support for building customised embedded style device images and custom containers. There are reference demo images ranging from X11/GTK+ to Weston, commandline and more. The system supports cross-architecture application development using QEMU emulation and a standalone toolchain and SDK suitable for IDE integration.

Additional 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 BSP layers which extend the systems capabilities in a modular way. Many layers are available and can be found through the layer index.

As an integration layer Poky consists of several upstream projects such as BitBake, OpenEmbedded-Core, Yocto documentation, the 'meta-yocto' layer which has configuration and hardware support components. These components are all part of the Yocto Project and OpenEmbedded ecosystems.

The Yocto Project has extensive documentation about the system including a reference manual which can be found at https://docs.yoctoproject.org/

OpenEmbedded is the build architecture used by Poky and the Yocto project. For information about OpenEmbedded, see the OpenEmbedded website.

Contribution Guidelines

Please refer to our contributor guide here: https://docs.yoctoproject.org/dev/contributor-guide/ for full details on how to submit changes.

Where to Send Patches

As Poky is an integration repository (built using a tool called combo-layer), patches against the various components should be sent to their respective upstreams:

OpenEmbedded-Core (files in meta/, meta-selftest/, meta-skeleton/, scripts/):

BitBake (files in bitbake/):

Documentation (files in documentation/):

meta-yocto (files in meta-poky/, meta-yocto-bsp/):

If in doubt, check the openembedded-core git repository for the content you intend to modify as most files are from there unless clearly one of the above categories. Before sending, be sure the patches apply cleanly to the current git repository branch in question.

CII Best Practices

Description
No description provided
Readme 251 MiB