Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OE4T update and refactor #18

Merged
merged 12 commits into from Aug 10, 2023

Conversation

TheYoctoJester
Copy link

This PR brings the current state of the layers kirkstone branch, which also includes the kas based configurations. This specific branch contains the refactoring of the meta-mender-tegra directory from a layer into a directory containing layers for Jetpack 4 and Jetpack 5 based platforms, respectively.

The included state of the Jetpack 5 incarnation is directly based on #17 to serve as a base for the ongoing development.

@dwalkes dwalkes changed the base branch from kirkstone to kirkstone-r35.x July 21, 2023 18:33
@dwalkes dwalkes changed the base branch from kirkstone-r35.x to kirkstone July 21, 2023 18:41
@dwalkes
Copy link
Member

dwalkes commented Jul 21, 2023

@TheYoctoJester I thought I could update our kirkstone branch to match https://github.com/mendersoftware/meta-mender-community/commits/kirkstone but it looks like your branch isn't rebased on the upstream and has different commit history. Do you want to rebase on upstream?

I was originally thinking of targeting kirkstone-r35.x for work related to Jetpack 5 but I think given we can support both Jetpack 4 and 5 with your changes we may as well just use kirkstone.

@TheYoctoJester
Copy link
Author

@dwalkes the missing rebase was an oversight, sorry. Should be fixed now.

Copy link
Member

@dwalkes dwalkes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@TheYoctoJester I've added some comments here. I'm wondering about whether we should avoid adding files we know won't be useful with Jetpack 5 before this merge or delete after the merge. Will wait for @madisongh to weigh in before I approve.

@TheYoctoJester
Copy link
Author

@dwalkes thanks a lot! Will go through those one by one once I'm back the office, presumably Monday or Tuesday. I personally would like to remove as much of the old stuff as possible and not drag it along.
In most cases I just can't judge as I'm not super familiar with the Tegra stuff, hence need input like yours. Thanks!

TheYoctoJester added a commit to TheYoctoJester/meta-mender-community that referenced this pull request Jul 23, 2023
Remove all leftover u-boot references, as it is not
supported anymore on Jetpack 5. See comment:
OE4T#18 (comment)

Signed-off-by: Josef Holzmayr <jester@theyoctojester.info>
TheYoctoJester added a commit to TheYoctoJester/meta-mender-community that referenced this pull request Jul 23, 2023
Remove outdated init scripts, see comment:
OE4T#18 (comment)

Changelog: Title
Ticket: None

Signed-off-by: Josef Holzmayr <jester@theyoctojester.info>
TheYoctoJester added a commit to TheYoctoJester/meta-mender-community that referenced this pull request Jul 23, 2023
State scripts referring to TX2 and Nano can be removed.
See also comment: OE4T#18 (comment)

Signed-off-by: Josef Holzmayr <jester@theyoctojester.info>
@TheYoctoJester
Copy link
Author

@dwalkes addressed the comments. One thing I also noticed is the c-boot appends in recipes-bsp, which are actually masked out in layer.conf. Guess they should also be removed?

@dwalkes
Copy link
Member

dwalkes commented Jul 23, 2023

@TheYoctoJester good catch, yes everything cboot should be out of the Jetpack 5 branch.

Copy link
Member

@dwalkes dwalkes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Noticed a few more items which can be removed from the Jetpack 5 layer as well

TheYoctoJester and others added 3 commits July 24, 2023 11:38
This was an unintentional duplication from the mender-base.yml
kas include, and did set the revision floating on a release branch.

Changelog: Title
Ticket: None

Signed-off-by: Josef Holzmayr <jester@theyoctojester.info>
The Readme file and repo scripts for meta-mender-tegra still
referred to the dunfell and zeus releases. As we now provide
kas configurations for all supported boards in this layer,
note those in the Readme and remove the outdated information.

Changelog: Title
Ticket: None

Signed-off-by: Josef Holzmayr <jester@theyoctojester.info>
…ne-next

meta-mender-tegra: kas related fixes and updates
The current layer is compatible with Jetpack 4, which
correlates with the L4T 32.x release family. A number of
boards are supported on this, for example
- Jetson TX2
- Jetson Nano
- ...
The newer release family Jetpack 5 correlating with L4T 35.x
introduces a number of breaking changes which cannot be folded
into the existing structure.
To prepare for the support of both families, this moves the
existing layer into a dedicated subdirectory, allowing additional
Tegra-specific layers to be added to the meta-mender-tegra
top level directory.

Changelog: Title
Ticket: None

Signed-off-by: Josef Holzmayr <jester@theyoctojester.info>
This commit continues the refactoring of meta-mender-tegra
to support both Jetpack 4 and Jetpack 5 enabled boards.
The Jetpack 4 based board have been moved to the
tegrademo-mender distro as provided by the OE4T project.
The AGX Orin board is being added as a PoC-quality
board integration on Jetpack 5

Changelog: Title
Ticket: None

Signed-off-by: Josef Holzmayr <jester@theyoctojester.info>
This reflects efcbadb for the
Jetpack 5-based board integration layer.

Signed-off-by: Josef Holzmayr <jester@theyoctojester.info>
Changelog: Title
Ticket: None

Signed-off-by: Josef Holzmayr <jester@theyoctojester.info>
Remove all leftover u-boot references, as it is not
supported anymore on Jetpack 5. See comment:
OE4T#18 (comment)

Signed-off-by: Josef Holzmayr <jester@theyoctojester.info>
Remove outdated init scripts, see comment:
OE4T#18 (comment)

Changelog: Title
Ticket: None

Signed-off-by: Josef Holzmayr <jester@theyoctojester.info>
State scripts referring to TX2 and Nano can be removed.
See also comment: OE4T#18 (comment)

Signed-off-by: Josef Holzmayr <jester@theyoctojester.info>
In Jetpack5, cboot is not used anymore. Remove the
appends which placed an additional dependency on machine-id.

Changelog: Title
Ticket: None

Signed-off-by: Josef Holzmayr <jester@theyoctojester.info>
The TX2 and Nano platforms are not supported on Jetpack 5
anymore, so the respective flash layouts can be removed.

Changelog: Title
Ticket: None

Signed-off-by: Josef Holzmayr <jester@theyoctojester.info>
@TheYoctoJester
Copy link
Author

@dwalkes cleaned up and rebased :-)

FILESEXTRAPATHS:prepend := "${THISDIR}/files:"

SRC_URI += "file://0007-runtime-access-for-KernelCommandLine-efivar.patch;patchdir=.."
SRC_URI += "file://0008-enable-rootfs-redundancy.patch;patchdir=.."

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Instead of patch we should use overlays

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Instead of patch we should use overlays

Can you provide the change? This is directly based off the naroj/dev3 branch.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I know and I will. I marked this line quickly to not forget to do this. Sorry for confusion

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@maciej-narojczyk if this is working for you the same way it was on your previous branch let's merge and you can propose additional PRs for additional changes.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok

@dwalkes dwalkes self-requested a review July 25, 2023 18:35
Copy link
Member

@dwalkes dwalkes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me, and thanks @TheYoctoJester and @maciej-narojczyk for getting this started.

@maciej-narojczyk
Copy link

I see that kas build kas/jetson-agx-orin-devkit.yml is building core-image-minimal should we build demo-image-base instead ?

@TheYoctoJester
Copy link
Author

@maciej-narojczyk the default is core-image-minimal to reduce to build time for the automated testing. But I'm open to suggestions. If the general concensus is that demo-image-base is the image to promote for people taking a first look, then I'm happy to take that. Thoughts @dwalkes @madisongh?

@TheYoctoJester
Copy link
Author

@dwalkes as you approved, do you want to take this into the OE4T fork first and then PR back to the Mender one, or should I put that one directly in?

# these two classes only work as intended when being inherited in the
# OE4t setup-env.sh style environment, as they modify bblayers.conf
# and expect additional information on the host.
INHERIT:remove = "tegra-support-sanity distro_layer_buildinfo"
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we should add this line here
EXTRA_IMAGE_FEATURES ?= "debug-tweaks"

without it i couldnt login at all :)
what is login and password then ?

@maciej-narojczyk
Copy link

I got a working mender update with this PR and my local tweaks so it works.

@dwalkes
Copy link
Member

dwalkes commented Jul 26, 2023

@dwalkes as you approved, do you want to take this into the OE4T fork first and then PR back to the Mender one, or should I put that one directly in?

I was originally thinking we'd stage all the Jetpack 5 changes, including the refactor to move Jetpack 4 into a subdirectory, in this OE4T repository, and only merge upstream when we've got Jetpack 5 support complete. I'm open to other suggestions though. If we needed to make any changes to Jetpack 4 support this would be another reason to merge now. Perhaps the new kas changes might be a place where we'd want to make changes for Jetpack 4 which also go upstream.

the default is core-image-minimal to reduce to build time for the automated testing. But I'm open to suggestions. If the general concensus is that demo-image-base is the image to promote for people taking a first look, then I'm happy to take that. Thoughts @dwalkes @madisongh?

I think demo-image-base probably gets a bit more love and is more functional but there's no reason I know about which means core-image-minimal won't work.

@dwalkes dwalkes merged commit 22f8768 into OE4T:kirkstone Aug 10, 2023
dwalkes pushed a commit that referenced this pull request Aug 10, 2023
Remove all leftover u-boot references, as it is not
supported anymore on Jetpack 5. See comment:
#18 (comment)

Signed-off-by: Josef Holzmayr <jester@theyoctojester.info>
dwalkes pushed a commit that referenced this pull request Aug 10, 2023
Remove outdated init scripts, see comment:
#18 (comment)

Changelog: Title
Ticket: None

Signed-off-by: Josef Holzmayr <jester@theyoctojester.info>
dwalkes pushed a commit that referenced this pull request Aug 10, 2023
State scripts referring to TX2 and Nano can be removed.
See also comment: #18 (comment)

Signed-off-by: Josef Holzmayr <jester@theyoctojester.info>
@dwalkes
Copy link
Member

dwalkes commented Aug 10, 2023

Merging here for the time being

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.

None yet

3 participants