Skip to content

i.MX95: integrate FRDM display, Waydroid and partner BSP - #49

Open
ajlennon wants to merge 125 commits into
mainfrom
integration/imx95-frdm-screen-current
Open

i.MX95: integrate FRDM display, Waydroid and partner BSP#49
ajlennon wants to merge 125 commits into
mainfrom
integration/imx95-frdm-screen-current

Conversation

@ajlennon

@ajlennon ajlennon commented Sep 11, 2026

Copy link
Copy Markdown
Member

Summary

  • add the FRDM-i.MX95 HDMI/display and standard splash handoff integration
  • add the FRDM Waydroid service, Android 16 compatibility, image provisioning, and graphics policy
  • consume the independently maintained Active ESL NXP i.MX partner layer with exact revisions
  • keep NXP OTBR as explicit product policy while isolating mfgtool/recovery payloads
  • add a mandatory baseline-versus-candidate layer-adoption gate over every pre-existing image and mfgtool tuple

Layer-adoption safety

The stable Layer Adoption Gate check treats every KAS, .gitmodules, or layer.conf change as material. It requires an updated review contract, completes baseline and candidate builds for fourteen legacy tuples, and compares layer policy, all bbappends, resolved recipes/providers, package and task graphs, warnings, deploy layout, signing/recovery outcomes, and artifact sizes. Any unexplained delta fails.

Evidence

  • exact-pinned FRDM mfgtool build completed on ai-tools: 3032/3032 tasks, 17,762,666-byte compressed recovery initramfs, forbidden payload count zero
  • Foundries target 2908 mfgtools run passed; its normal run exposed a stale libglibutil licence checksum
  • the exact libglibutil source checksum was corrected and a forced do_populate_lic passed locally
  • Foundries target 2909 mfgtools run passed; its normal run exposed the same clean-builder class in pinned libgbinder
  • libgbinder commit e906afcf retains BSD-3-Clause and its exact LICENSE hashes to 6b4103b77e6fa766a75a1c2c3ba715c8
  • exact-manifest forced bitbake libgbinder -c populate_lic -f passed all 105 tasks on ai-tools at product commit e7c5619
  • replacement Foundries target 2910 is running manifest commit ae714e5
  • product policy check confirms OTBR is retained while direct Boost payload does not leak into the image
  • Python compilation, JSON validation, bash -n, shellcheck, git diff --check, and actionlint pass
  • Node 24-compatible action majors are used and Yocto jobs are restricted to the dedicated runner label

Review note

Do not merge until Foundries CI 2910 and the new layer-adoption regression check are green.

AI disclosure: implementation and verification were assisted by OpenAI Codex under maintainer direction.

Assisted-by: OpenAI Codex

…mx95-frdm-screen-current

# Conflicts:
#	.github/workflows/layer-adoption-gate.yml
#	ci/layer-adoption-contract.json
#	ci/layer-adoption-tuples.json
#	scripts/kas-build-mfgtools.sh
#	scripts/validation/capture-layer-state.sh
#	scripts/validation/compare-layer-state.py
#	scripts/validation/run-layer-adoption-regression.py
#	scripts/validation/tests/test_capture_layer_state.py
#	scripts/validation/tests/test_compare_layer_state.py
#	scripts/validation/tests/test_run_layer_adoption_regression.py
Preserve the explicit INST and Phasora retirements, but require paired factory-image and mfgtool coverage for every still-active DT510, Handheld, Screen, Sentai and i.MX93 product. Reject incomplete matrices before builds start.

Signed-off-by: Alex Lennon <ajlennon@dynamicdevices.co.uk>

Assisted-by: Codex
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