On Sat, 16 May 2020 at 15:46, Heinrich Schuchardt xypron.glpk@gmx.de wrote:
On 5/15/20 7:10 AM, François Ozog wrote:
<snip> > Would the topic of dynamic parts of device trees deserve two slides on > our next meeting? > > This is a key topic that probably deserves more than two slides. Please > prepare a presentation as you deem fit . >
You can find my ideas about why device trees are not static here:
https://github.com/xypron/dte/blob/master/Device%20Trees%20Are%20Not%20Stati...
Great presentation! looking forward you talk to it.
If we were to define a UML sequence diagram with regards to firmware, what would be the actors and the classes?
From all past discussions, I am trying to find a name for the function
that U-Boot does. I would like to avoid "boot loader" because it may mean too many things. Thinking about areas of responsibility, I distinguish "firmware" and "operating system" (loosely defined). U-Boot becomes the pivot function between "firmware" and "OS".
I thus see two domains for DT manipulations (fixups, overlay merge or list-add): - what happens between firmware components (SMM, Trusted OS, Secure partitions...) -- what happens in the hand off between firmware and OS (and conversely)
Do you think you could add some slides to present your ideas around the above topics?
Best regards
Heinrich