separated working in a container from the build page - #25
Merged
Conversation
Contributor
|
I think that second page should actually be moved to the FPGA repo, linked from the meta-panda doc. It should say that to build an FPGA image you need to follow the docs in that repo, then use the bitstream to make the firmware |
adedamola-sode
force-pushed
the
separate-container-from-build
branch
from
June 19, 2026 13:50
3741786 to
94d0385
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Currently, the development, working in a container section is in the build page. This is confusing, as it has nothing to do with the build artifacts, but comes directly before the build artifacts, I think it's better in its own page.