On Wed, Aug 23, 2023 at 10:27:09PM -0500, Nishanth Menon wrote: > On 21:01-20230823, Simon Glass wrote: > > Hi Nishanth, > > > > On Wed, 23 Aug 2023 at 18:18, Nishanth Menon <n...@ti.com> wrote: > > > > > > On 17:57-20230823, Simon Glass wrote: > > > [...] > > > > > This is how we have a common bit of rST for how to build N boards, > > > > > without having to do a literal copy and paste N times. > > > > > > > > How about using this? > > > > > > > > https://docutils.sourceforge.io/docs/ref/rst/restructuredtext.html#substitution-definitions > > > > > > I was not able to succeed with complex includes such as: > > > https://github.com/u-boot/u-boot/blob/master/doc/board/ti/am62x_sk.rst?plain=1#L89 > > > > > > am62x complete build procedure defined once and reused in other am62x > > > platforms.. But the am62x build procedure itself is reused from common > > > k3 build steps. > > > > I followed through these instructions. I find the env vars quite > > confusing, since I don't really know what it is doing. It feels like a > > script: > > > > do $a $b $c > > do $f $e > > > > it is pretty hard to follow. I think it would be better to write > > everything out in full for each board, like rockchip does. > > Unfortunately, this is a few major steps that is repeated for > (currently): > AM62x SK > Toradex Verdin > (pending: beagleplay - ) > (once all the dust clears up, hopefully phytec) > SK-LP > .... > > I have no reasonable way to offer to keep them all in sync. > https://libera.irclog.whitequark.org/u-boot/2023-07-26#34662854; > is kind of why I went down this path.S
And please note that I do not like the way we're doing this in other platforms. That we have almost verbatim instructions for building TF-A and OPTEE for nearly every aarch64 platform is not good. I was hoping for something more truly template-based and that we could expand out from the K3 case to cover other platforms as well, but we're not there yet. -- Tom
signature.asc
Description: PGP signature
