Hi Alexandar, El jue, 26 ago 2021 a las 14:25, Alexander Dahl (<[email protected]>) escribió:
> Hello Guillermo, > > Am Thu, Aug 26, 2021 at 01:43:25PM +0200 schrieb Guillermo Rodriguez > Garcia: > > Hi Alexander, > > > > El jueves, 26 de agosto de 2021, Alexander Dahl <[email protected]> > escribió: > > > > > Hei hei, > > > > > > I crafted this in the last weeks for a DistroKit based generic BSP, > > > which uses U-Boot for half a dozen boards. Maybe someone else finds it > > > useful? > > > > > > What does this do exactly, and how does it work? > > This adds a new package type 'u-boot' to the `ptxdist newpackage` > command. That newpackage command uses templates to create the > necessary rule files for a new package. You can write your own > templates and add it to your BSP, too. > > So why a package type 'u-boot' if there's already an u-boot package? > I had the idea when working with DistroKit [1] as a base layer for > another generic BSP. You can build a BSP with a rootfs common to > different SoCs of the armv7 family and use a common kernel as well. > However bootloaders for different SoC families differ, so for such a > generic BSP you need to build different bootloaders, and what you do > then is duplicate those bootloaders packages in ptxdist with slighty > changed names/variables making them unique. DistroKit for example has > multiple barebox packages. > > Creating such packages by copy and paste and search and replace is > cumbersome and error prone, so I thought why not doing the same thing > pengutronix did with barebox for u-boot as well?! > This looks great. I am sure I have a use for this in my BSPs. Is it possible to add these templates to my BSP without modifying ptxdist itself? Where should the files be installed? Thanks, Guillermo
_______________________________________________ ptxdist mailing list [email protected] To unsubscribe, send a mail with subject "unsubscribe" to [email protected]
