[dunfell/master,V2,00/12] recipes-core: Add a bootstrap Linux image

Board bringups are typically painful. however, over the years, folks
know of minimal debug tools that are pretty effective in helping debug
basic peripherals. Lets create a reusable packagegroup balancing the
tools from wisdom from various folks vs the size of the resultant
package.

We would like to base such a system on more simplistic sysvinit (no
offence systemd, you are still our fav), as it has a much smaller
footprint.

The board startup is best done with a minimal u-boot and kernel device
tree configurations.

Dependency (for patch #12, depends on https://lore.kernel.org/all/20220314202840.18904-1-reatmon@ti.com/ )

Changes since V1:
* Additional documentation patches
* Cleanups for review comments

V1: https://lore.kernel.org/all/20220309021316.28370-1-nm@ti.com/

Nishanth Menon (12):
  Revert "tisdk-tiny-image: remove packagedata task breaking initramfs
    packaging"
  tisdk-tiny-image: Split common components into include file
  tisdk-tiny-image: Add some usability notes
  tisdk-base-image: Reformat documentation and clarify usage
  tisdk-default-image: Reformat documentation and clarify usage
  tisdk-thinlinux-image: Reformat documentation
  packagegroups: Add a new bootstrap package group
  recipes-core: images: Add a basic bootstrap base image
  recipes-bsp: Create a bootstrap-initrd package
  recipes-core: images: Introduce tisdk-bootstrap-image
  tisdk-core-bundle: Add documentation to clarify usage
  images: Build tisdk-bootstrap-image with tisdk-core-bundle

 .../bootstrap-initrd/bootstrap-initrd_1.0.bb  | 22 ++++++++
 .../recipes-core/images/arago-tiny-image.inc  |  9 ++++
 .../recipes-core/images/tisdk-base-image.bb   |  4 +-
 .../images/tisdk-bootstrap-base-image.bb      | 21 ++++++++
 .../images/tisdk-bootstrap-image.bb           | 20 +++++++
 .../recipes-core/images/tisdk-core-bundle.bb  |  6 +++
 .../recipes-core/images/tisdk-core-bundle.inc |  2 +-
 .../images/tisdk-default-image.bb             |  3 ++
 .../images/tisdk-thinlinux-image.bb           |  1 +
 .../recipes-core/images/tisdk-tiny-image.bb   | 20 +++----
 .../packagegroup-arago-bootstrap.bb           | 53 +++++++++++++++++++
 11 files changed, 150 insertions(+), 11 deletions(-)
 create mode 100644 meta-arago-distro/recipes-bsp/bootstrap-initrd/bootstrap-initrd_1.0.bb
 create mode 100644 meta-arago-distro/recipes-core/images/arago-tiny-image.inc
 create mode 100644 meta-arago-distro/recipes-core/images/tisdk-bootstrap-base-image.bb
 create mode 100644 meta-arago-distro/recipes-core/images/tisdk-bootstrap-image.bb
 create mode 100644 meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-bootstrap.bb

On 09:37-20220318, Nishanth Menon via lists.yoctoproject.org wrote:
> Lets clarify the usage of tiny image as something meant as a building
> block and not something that folks can directly use.
> 
> Signed-off-by: Nishanth Menon <nm@ti.com>
> ---
> Changes since v1:
> * Review comments incorporated
> 
> V1: https://lore.kernel.org/all/20220309021316.28370-3-nm@ti.com/
>  .../recipes-core/images/tisdk-tiny-image.bb              | 9 +++++++++
>  1 file changed, 9 insertions(+)
> 
> diff --git a/meta-arago-distro/recipes-core/images/tisdk-tiny-image.bb b/meta-arago-distro/recipes-core/images/tisdk-tiny-image.bb
> index 85ae3728e86e..352cc2d1aa44 100644
> --- a/meta-arago-distro/recipes-core/images/tisdk-tiny-image.bb
> +++ b/meta-arago-distro/recipes-core/images/tisdk-tiny-image.bb
> @@ -1,3 +1,12 @@
> +# Arago TI SDK super minimal base image for initramfs
> +#
> +# Image meant for basic boot of linux kernel. Intended as
> +# bare system, this image does not package the kernel in the
> +# standard /boot folder in rootfs. Instead, it provides a base
> +# rootfs allowing kernel to be deployed elsewhere
> +# (tftp/separate boot partition/jtag log etc..) and boot
> +# the image.


This and elsewhere, should we use instead:

SUMMARY = "Arago TI SDK super minimal base image for initramfs"

DESCRIPTION = "Image meant for basic boot of linux kernel. Intended as \
bare system, this image does not package the kernel in the \
standard /boot folder in rootfs. Instead, it provides a base \
rootfs allowing kernel to be deployed elsewhere \
(tftp/separate boot partition/jtag log etc..) and boot \
the image.\
"

and should we also create a HOMEPAGE = "wiki link?"