Skip to content

FIT kernel and initramfs support#2

Open
sarnold wants to merge 10 commits intooe-mickledorefrom
fit-support
Open

FIT kernel and initramfs support#2
sarnold wants to merge 10 commits intooe-mickledorefrom
fit-support

Conversation

@sarnold
Copy link
Member

@sarnold sarnold commented Jan 24, 2026

  • add qemu-native patch and site.yaml, remove machine overrides
  • add basic fitImage support to enclustra config
  • coerce fitimage bbclass to find the dtbs, update u-boot cfg
  • split out enclustra BSP changes as fit and address configs
  • apply enclustra machine patch for baseline fitImage support
  • support fitImage as default kernel in sd-aa1 boot script
  • add initramfs recipe for fitImage usage (consumable include file for custom recipes)
  • rename oe-core patches and cleanup some whitespace

* turns out enclustra-module layer is extremely brittle compared to
  most vendor bsp/sdk layers
* long-term answer is to fully consume the necessary machine bits
  into user layer => convert me-aa1-blah-blah into my-machine

Signed-off-by: Stephen L Arnold <sarnold@vctlabs.com>
* keep fit cfg in kas until enclustra machine bits are fully migrated

Signed-off-by: Stephen L Arnold <sarnold@vctlabs.com>
Signed-off-by: Stephen L Arnold <sarnold@vctlabs.com>
Signed-off-by: Stephen L Arnold <sarnold@vctlabs.com>
* add patch and kas fit.yaml to enable fitImage build artifact and
  image.ub deployed fit kernel in deployed boot partition
* note that fitimage bbclass includes all overlays BUT does not
  create multiple configurations, so the default boot payload is
  kernel plus devicetree.dtb only
* as yet, there is no default boot support in boot.scr

Signed-off-by: Stephen L Arnold <sarnold@vctlabs.com>
* add vboot.yaml to generate dev keys and demonstrate signing

Signed-off-by: Stephen L Arnold <sarnold@vctlabs.com>
* add more wic removal and cleanup some leftover machine cruft

Signed-off-by: Stephen L Arnold <sarnold@vctlabs.com>
Signed-off-by: Stephen L Arnold <sarnold@vctlabs.com>
* as documented in the consuming tox workflow, the "meta-user" repo
  must be cloned locally first in order for kas to pull in the other
  layers BUT the kas parent repo should not have path or url keys

Signed-off-by: Stephen L Arnold <sarnold@vctlabs.com>
…suming

* this allows consumers to use their own image class and pkg install
  while still using the include file as-is
* add devel-initramfs to deployed boot files for testing

Signed-off-by: Stephen L Arnold <sarnold@vctlabs.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant