U-Boot: refactor general info for the AM62Lx boot flow#204
U-Boot: refactor general info for the AM62Lx boot flow#204praneethbajjuri merged 3 commits intoTexasInstruments:masterfrom
Conversation
9244a6f to
d3a691c
Compare
source/linux/Foundational_Components/U-Boot/UG-General-Info.rst
Outdated
Show resolved
Hide resolved
source/linux/Foundational_Components/U-Boot/UG-General-Info.rst
Outdated
Show resolved
Hide resolved
source/linux/Foundational_Components/U-Boot/UG-General-Info.rst
Outdated
Show resolved
Hide resolved
d3a691c to
3e559df
Compare
There was a problem hiding this comment.
The indentation for all your newly added table got messed up in v2
Checkout RST preview - https://github.com/TexasInstruments/processor-sdk-doc/blob/3e559df08028e91d1fa0947828279fe416fe3688/source/linux/Foundational_Components/U-Boot/UG-General-Info.rst
There was a problem hiding this comment.
ah a plugin was trying to be helpful :/ I fixed it now.
There was a problem hiding this comment.
@bryanbrattlof The indentation for all your newly added table still seems to be incorrect
There was a problem hiding this comment.
Hmm. I'm don't think I see the issue you're seeing. I'm assuming your talking about the boot flow diagrams which I had a little trouble myself so I just disabled the bootflow section on line 1324 if we're rendering for the AM62L and made a complete new section below that section.
There was a problem hiding this comment.
@cshilwant , Bryan's indentation is fine, it is 3 space indentation everywhere. The only place it is 4 space indentation is for Image formats tables and that is because everyone else in that section is also using 4 space indentation. This PR should be merged as is and then someone can go fix the indentation for that section IMO
There was a problem hiding this comment.
@jmenti @bryanbrattlof @jeevantelukula
It ended up looking like - https://texasinstruments.github.io/processor-sdk-doc/processor-sdk-linux-AM62LX/esd/docs/11_00_05_02/linux/Foundational_Components/U-Boot/UG-General-Info.html#image-formats
as compared to AM62x where things are fine - https://texasinstruments.github.io/processor-sdk-doc/processor-sdk-linux-AM62X/esd/docs/10_01_10_04/linux/Foundational_Components/U-Boot/UG-General-Info.html#image-formats
source/linux/Foundational_Components/U-Boot/UG-General-Info.rst
Outdated
Show resolved
Hide resolved
source/linux/Foundational_Components/U-Boot/UG-General-Info.rst
Outdated
Show resolved
Hide resolved
source/linux/Foundational_Components/U-Boot/UG-General-Info.rst
Outdated
Show resolved
Hide resolved
source/linux/Foundational_Components/U-Boot/UG-General-Info.rst
Outdated
Show resolved
Hide resolved
source/linux/Foundational_Components/U-Boot/UG-General-Info.rst
Outdated
Show resolved
Hide resolved
source/linux/Foundational_Components/U-Boot/UG-General-Info.rst
Outdated
Show resolved
Hide resolved
816dfdd to
5a75128
Compare
There was a problem hiding this comment.
@bryanbrattlof The indentation for all your newly added table still seems to be incorrect
|
@bryanbrattlof why are we explaining the bootflow under both "Image Formats" and under "Boot Flow"? Just leave the section under "Image Formats with no description and give a full description of the boorflow under the bootflow section, pretty please (: |
5a75128 to
3c4caf9
Compare
|
no worries. I've removed the paragraphs |
several updates after the last review
StaticRocket
left a comment
There was a problem hiding this comment.
Close enough for now. There's still some indentation issues but I know this file is about to be reworked.
|
Looks like 57f78ae was an accidental merge commit? |
|
Well this was correct until @praneethbajjuri modified it. @bryanbrattlof you'll have to rebase and push now. |
cshilwant
left a comment
There was a problem hiding this comment.
Need to fix - #204 (comment)
Yes, my bad .. the rebase messed it up. @bryanbrattlof will send a update in a day removing the merge delta. |
57f78ae to
8d2d38f
Compare
jmenti
left a comment
There was a problem hiding this comment.
I see no major issues but I did nitpick a few details @bryanbrattlof
There was a problem hiding this comment.
@cshilwant , Bryan's indentation is fine, it is 3 space indentation everywhere. The only place it is 4 space indentation is for Image formats tables and that is because everyone else in that section is also using 4 space indentation. This PR should be merged as is and then someone can go fix the indentation for that section IMO
source/linux/Foundational_Components/U-Boot/UG-General-Info.rst
Outdated
Show resolved
Hide resolved
source/linux/Foundational_Components/U-Boot/UG-General-Info.rst
Outdated
Show resolved
Hide resolved
source/linux/Foundational_Components/U-Boot/UG-General-Info.rst
Outdated
Show resolved
Hide resolved
source/linux/Foundational_Components/U-Boot/UG-General-Info.rst
Outdated
Show resolved
Hide resolved
b6193a3
8d2d38f to
b6193a3
Compare
There are some weird whitespace inconsistencies. Fix them Signed-off-by: Bryan Brattlof <bb@ti.com>
Quite a lot has changed for the AM62Lx boot flow when compared to more traditional AM62 devices. After hiding un-necessary sections document via ASCII charts the bootflow between the SMS and A53 cores along with the memory layout of the 2 SRAM spaces during the boot sequence Signed-off-by: Bryan Brattlof <bb@ti.com>
ARM's Trusted firmware Boot Loader (BL) stage 1, 2 and 3 provides a reference software design for the different phases a CPU can be during boot. To make things a little more uniform, standardize on using BL-1 for AP Trusted ROM code or BL-31 for EL3 Runtime Firmware Signed-off-by: Bryan Brattlof <bb@ti.com>
b6193a3 to
ec6ec8f
Compare
Quite a lot has changed for the AM62Lx boot flow when compared to more traditional AM62 devices. After hiding un-necessary sections document via ASCII charts the bootflow between the SMS and A53 cores along with the memory layout of the 2 SRAM spaces during the boot sequence
Unfortunately this will create a lot of warnings about undefined references to optee. Other than creating an entirely new U-Boot file for 62L I don't think we can get rid of them now. One idea is to add optee back in with a simple landing page saying something along the lines of
raise NotImplementedError()or something