On Mon, 2 Mar 2020 at 18:40, Andrei Warkentin <[email protected]> wrote: > > Hi Ard, > > > Do we really need this patch? For development, you can put anything > > you want here. For doing releases, I'd expect edk2-platforms to be in > > sync with edk2-non-osi, given that there are more blobs there than > > TF-A, right? > > This is a developer productivity improvement that I've found to be useful and > it has no impact on others for the default case of building code for release. > > Sure, you can copy things around and stage/unstage files, but I like > automating my work and I tend to track the upstream TF-A (for regressions, > rpi4-uefi.dev work), > so being able to quickly generate builds both with internal and external TF-A > and without extra hoopla has been key. The time I avoid dealing with dirty > trees is time I can spend elsewhere else making Pi 4 implementation better. > > There aren't really any other blobs that matter for Pi 4...The embedded DTB > is going to go away as part of fixing the regression seen with > https://github.com/pftf/RPi4/issues/17 (on the Pi 4 you can't really boot > anyway without passing a DTB in config.txt). >
Fair enough. I still don't quite see the point, but I don't really mind either. Reviewed-by: Ard Biesheuvel <[email protected]> Pushed as 30324eefb3a4..07cc442f7212 -=-=-=-=-=-=-=-=-=-=-=- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#55228): https://edk2.groups.io/g/devel/message/55228 Mute This Topic: https://groups.io/mt/71676028/21656 Group Owner: [email protected] Unsubscribe: https://edk2.groups.io/g/devel/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
