Wip/bhahn/imx8mp pd26 update finalize#456
Conversation
BHahn42618
force-pushed
the
WIP/bhahn/imx8mp_PD26_update_finalize
branch
from
f7db4b2 to
f806b31
Compare
BHahn42618
force-pushed
the
WIP/bhahn/imx8mp_PD26_update_finalize
branch
2 times, most recently
from
a6e3fb1 to
b590f89
Compare
|
rebase to main & fix codespell check (collumn => column) |
BHahn42618
force-pushed
the
WIP/bhahn/imx8mp_PD26_update_finalize
branch
from
b590f89 to
318c87c
Compare
Update links and tags for PD26.1.0 release in head manual. Signed-off-by: Benjamin Hahn <B.Hahn@phytec.de>
Remove left-over overlaycallback from newer manuals where it is unused. Signed-off-by: Benjamin Hahn <B.Hahn@phytec.de>
Update links and tags for PD26.1.0 in head manual. Signed-off-by: Benjamin Hahn <B.Hahn@phytec.de>
Finalize release manuals for BSP-Yocto-i.MX8MP-PD26.1.0. Signed-off-by: Benjamin Hahn <B.Hahn@phytec.de>
Add releasenotes and more detailed overview about supported features. Signed-off-by: Benjamin Hahn <B.Hahn@phytec.de>
Add releasenotes and more detailed overview about supported features. Signed-off-by: Benjamin Hahn <B.Hahn@phytec.de>
BHahn42618
force-pushed
the
WIP/bhahn/imx8mp_PD26_update_finalize
branch
from
318c87c to
2176cb5
Compare
|
Added KPD BoMs for imx8mp Libra and then rebased to main |
|
Teresa is on vacation for 3 weeks |
| Release Notes | ||
| ============= | ||
|
|
There was a problem hiding this comment.
Apologies for missing this in the first review, can you move that to an include file since it appears that imx8mp and imx8mp-fpsc both share the same content?
There was a problem hiding this comment.
Since both boards are in one release, the release notes are the same, but I don't think we should use an include here. So far we only used includes for generic chapters that were included in the head manual and are generic for the board and not one release. The releasenotes are only for this one release and will not be included in other releases. For this case we usually put the chapters in the manuals themselves and not use includes. Using includes here would break the scheme we are using so far.
There was a problem hiding this comment.
Why can't you name the file pd26.1.0_release-notes ? It is clear then that it's only for a single release.
If you don't want to use an include file, then remove the respective non-relevant machine info from the releases notes. I.e. remove everything Libra specific from the Pollux file and vice versa.
3 participants
update links and tags for release
create nxp_pd26.1.0 manual from head manual
Add releasenotes
depends on #453