search

OE4T / tegra-demo-distro

Reference/demonstration distro for meta-tegra
MIT License
73 stars 74 forks source link

feat: prepare meta-mender-community refactoring #265

Closed TheYoctoJester closed 1 year ago

TheYoctoJester commented 1 year ago

This reflects 1862576ba943409857986072e19695b73d82ba7a on https://github.com/theyoctojester/meta-mender-community to prepare for the Jetpack4 and Jetpack5 support in meta-mender-community.

Changelog: Title Ticket: None

dwalkes commented 1 year ago

@TheYoctoJester thanks for getting this started. Is there a reason to merge this now as opposed to when it's already upstream in meta-mender-community? Typically we've pointed tegra-demo-distro at either the upstream meta-mender-community or our OE4T fork.

TheYoctoJester commented 1 year ago

@dwalkes no reason at all, just providing the template as proposed on the last call. I'm happy to keep the development in either my branch, or a separate one on meta-mender-community. What I just haven't figured out is how to make the git submodule based approach used by OE4T and the kas based one in meta-mender-community to play nice with each other.

angeloc commented 1 year ago

@TheYoctoJester Looking forward on how to solve this problem. I'm trying to use kas too, and the git submodule approach is really annoying to integrate. Thanks for looking at it!

TheYoctoJester commented 1 year ago

@dwalkes as we're currently sorting out https://github.com/OE4T/meta-mender-community/pull/18, I'll close that one here until the metadata is ready. @angeloc if you are interested in the kas implementations, please look at the above PR. It points to a branch which has configurations for all Mender-enabled boards on Jetpack4, as well as the current state of PoC on Jetpack5 for AGX Orin.