Bruce Ashfield 812dbc2769 linux-yocto/6.6: arm: jitter entropy backport
Integrating the following commit(s) to linux-yocto/6.6:

1/1 [
    Author: Stephan Müller
    Email: smueller@chronox.de
    Subject: crypto: jitter - add RCT/APT support for different OSRs
    Date: Thu, 21 Sep 2023 13:48:11 +0200

    The oversampling rate (OSR) value specifies the heuristically implied
    entropy in the recorded data - H_submitter = 1/osr. A different entropy
    estimate implies a different APT/RCT cutoff value. This change adds
    support for OSRs 1 through 15. This OSR can be selected by the caller
    of the Jitter RNG.

    For this patch, the caller still uses one hard-coded OSR. A subsequent
    patch allows this value to be configured.

    In addition, the power-up self test is adjusted as follows:

    * It allows the caller to provide an oversampling rate that should be
    tested with - commonly it should be the same as used for the actual
    runtime operation. This makes the power-up testing therefore consistent
    with the runtime operation.

    * It calls now jent_measure_jitter (i.e. collects the full entropy
    that can possibly be harvested by the Jitter RNG) instead of only
    jent_condition_data (which only returns the entropy harvested from
    the conditioning component). This should now alleviate reports where
    the Jitter RNG initialization thinks there is too little entropy.

    * The power-up test now solely relies on the (enhanced) APT and RCT
    test that is used as a health test at runtime.

    The code allowing the different OSRs as well as the power-up test
    changes are present in the user space version of the Jitter RNG 3.4.1
    and thus was already in production use for some time.

    Reported-by "Ospan, Abylay" <aospan@amazon.com>
    Signed-off-by: Stephan Mueller <smueller@chronox.de>
    Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
]

(From OE-Core rev: 1349b759e9b8f363ab9a9feec531f3a877f97dec)

Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2024-01-04 23:47:51 +00:00
2023-11-21 21:34:04 +00:00
2023-11-21 21:34:04 +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 249 MiB