-
Couldn't load subscription status.
- Fork 71
Bugfix/clean uboot #493
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
base: master
Are you sure you want to change the base?
Bugfix/clean uboot #493
Conversation
| process for the next bootloader stage: U-Boot. | ||
|
|
||
| 3. U-Boot | ||
| ######### |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking in the old file, that was apparently never defined. @praneethbajjuri , what's the course of action here?
3caf6fe to
791adab
Compare
Remove duplicate and unreachable omap content from the k3 bootflow document. Remove unused labels and associated duplicate sections. Fixes: 6814540 ("refactor(U-Boot): Split K3 and OMAP Build Guide") Signed-off-by: Randolph Sapp <[email protected]>
The refactor seems to include all relevant information for the devices still using UG-General-Info. Purge this old file and move any remaining K3 devices over to the new structure. Fixes: 6814540 ("refactor(U-Boot): Split K3 and OMAP Build Guide") Signed-off-by: Randolph Sapp <[email protected]>
Standardize the tag name for component versions listings to: release-specific-build-information This involves deprecating the partially used tag: release-specific-sdk-components-versions Signed-off-by: Randolph Sapp <[email protected]>
Use the common release-specific-build-information tag instead of the component specific tags. This data was always somewhat tabular but was split over several sections with different formatting depending on the platform. We are now looking to merge this under a single table like what was done with AM62LX. This initial merge made some links inaccessible for some platforms. This attempts to go back and enforce a common tag name to make sure we are always linking the user to at least a close section while the transition occurs. Signed-off-by: Randolph Sapp <[email protected]>
Left in from the previous refactor, these are not needed when encapsulated by an inline-code wrapper. Fixes: 6814540 ("refactor(U-Boot): Split K3 and OMAP Build Guide") Signed-off-by: Randolph Sapp <[email protected]>
f1b7d3d to
606cb53
Compare
|
New unreachable files found with check_files.py: |
|
Those warnings are not new. I need to submit a separate pr to clean those up. Opened #503 |



fix(u-boot): remove old monolithic UG-General-Info
The refactor seems to include all relevant information for the devices still
using UG-General-Info. Purge this old file and move any remaining K3 devices
over to the new structure.
Fixes: 6814540 ("refactor(U-Boot): Split K3 and OMAP Build Guide")
Signed-off-by: Randolph Sapp [email protected]
fix(u-boot): remove duplicate section
Remove duplicate and unreachable omap content from the k3 bootflow document.
Remove unused labels and associated duplicate sections.
Fixes: 6814540 ("refactor(U-Boot): Split K3 and OMAP Build Guide")
Signed-off-by: Randolph Sapp [email protected]