Bruce Ashfield 42c37a2228 linux-yocto/5.15: riscv64: drop MAXPHYSMEM_128GB
Integrating the following commit(s) to linux-yocto:

    commit e1b976ee4fb5af517cf01a9f2dd4a32f560ca894
    Author: Bruce Ashfield <bruce.ashfield@gmail.com>
    Date:   Tue Feb 15 23:27:31 2022 -0500

        riscv64: drop MAXPHYSMEM_128GB

        The MAXPHYSMEM config options have been removed upstream via the
        following commit, so we drop our setting.

           commit 6250ecf5ba42292b652cd01c9fcb2239010c5c44
           Author: Alexandre Ghiti <alexandre.ghiti@canonical.com>
           Date:   Mon Jan 17 10:57:16 2022 +0100

               riscv: Get rid of MAXPHYSMEM configs

               commit db1503d355a79d1d4255a9996f20e72848b74a56 upstream.

               CONFIG_MAXPHYSMEM_* are actually never used, even the nommu defconfigs
               selecting the MAXPHYSMEM_2GB had no effects on PAGE_OFFSET since it was
               preempted by !MMU case right before.

               In addition, the move of the kernel mapping at the end of the address
               space broke the use of MAXPHYSMEM_2G with MMU since it defines PAGE_OFFSET
               at the same address as the kernel mapping.

               Reported-by: Geert Uytterhoeven <geert@linux-m68k.org>
               Fixes: 2bfc6cd81bd1 ("riscv: Move kernel mapping outside of linear mapping")
               Signed-off-by: Alexandre Ghiti <alexandre.ghiti@canonical.com>
               Tested-by: Geert Uytterhoeven <geert@linux-m68k.org>
               Tested-by: Conor Dooley <Conor.Dooley@microchip.com>
               Cc: stable@vger.kernel.org
               Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>
               Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

(From OE-Core rev: da19366b44af8521b0f311581793fc89d554cd40)

Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2022-03-05 22:58:48 +00:00
2022-03-01 23:51:21 +00:00
2021-07-19 18:07:21 +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

The project works using a mailing list patch submission process. Patches should be sent to the mailing list for the repository the components originate from (see below). Throughout the Yocto Project, the README files in the component in question should detail where to send patches, who the maintainers are and where bugs should be reported.

A guide to submitting patches to OpenEmbedded is available at:

https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded

There is good documentation on how to write/format patches at:

https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines

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