Skip to content

Wip/bhahn/imx95 alpha2 uuu#419

Open
BHahn42618 wants to merge 3 commits intomainfrom
WIP/bhahn/imx95_alpha2_uuu
Open

Wip/bhahn/imx95 alpha2 uuu#419
BHahn42618 wants to merge 3 commits intomainfrom
WIP/bhahn/imx95_alpha2_uuu

Conversation

@BHahn42618
Copy link
Contributor

  • fix uuu.rsti include path for imx8mp-fpsc manuals
  • fix emmc bootparts link in uuu chapter
  • include uuu flash emmc part for imx95 ALPHA2 release

Copy link
Contributor

@ymoog ymoog left a comment

Choose a reason for hiding this comment

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

In your second commit message:

bsp: uuu: fix emmc bootparts link

you also modify rauc in addition to bsp, please drop bsp:

This link here goes to another include file. This is unstable and will

Please add reference to what "This link here" refers to.

lead to link to other (wrong) manuals. Fix this by linking to the

Please also add another sentence why it linked to other manuals.

bootloader offsets section of the RAUC manual.

And here to which it links now and why/how that fixes the problem.

Changes themselves lgtm.

Comment on lines +64 to +69
:end-before: .. bootloader-offsets-marker

.. _walnascar-bootloader-offsets:

.. include:: common/reference.rsti
:start-after: .. bootloader-offsets-marker
Copy link
Collaborator

Choose a reason for hiding this comment

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

I really don't like these kind of inserts, where the included text should be modified in the first place instead. I'd suggest using a link in source/rauc/common/reference.rsti at the desired place directly. The outcome is the same, and it's simpler.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Currently yes, the outcome would be the same, as the reference.rsti is only included in one manual, but if this changes in the future and it is included in multiple manuals, it will lead to the same issue that we had before, where the link will link to one of the manuals, but you can not control which one. And this might go undetected when creating a new rauc manual.

.. |u-boot-tag| replace:: v2021.04_2.2.0-phy17

.. RAUC
.. |ref-bootloader-offsets-marker| replace:: :ref:`Disable booting from e.MMC boot partitions <kirkstone-bootloader-offsets>`
Copy link
Collaborator

Choose a reason for hiding this comment

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

Shouldn't this reference substitution reside in the .. Ref Substitutions section below?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I guess this would also be a good place. Should I change this for all manuals?

Remove one of the slashes to get the correct format for the include
path.

Signed-off-by: Benjamin Hahn <B.Hahn@phytec.de>
The emmc-disable-boot-part link goes to another include file which is
included in multiple manuals. This will lead to linking to other (wrong)
manuals, as sphinx will see the same link destination across different
manuals and will take one destination for all links. Fix this by
linking to the bootloader offsets section of the RAUC manual.

Signed-off-by: Benjamin Hahn <B.Hahn@phytec.de>
Include uuu flash emmc part for ALPHA2 release.

Signed-off-by: Benjamin Hahn <B.Hahn@phytec.de>
@BHahn42618 BHahn42618 force-pushed the WIP/bhahn/imx95_alpha2_uuu branch from f2c5935 to 8006cb7 Compare March 4, 2026 15:11
Copy link
Contributor

@ymoog ymoog left a comment

Choose a reason for hiding this comment

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

Your first commit description still claims/implies that something was wrong/incorrect before. You said this was not the case, it was already correct. Do not claim that you fix something when it was simply a style issue.

Also, you did not add how you resolve the linking problem. Please add that.

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.

3 participants