On Thu, Jan 10, 2019 at 09:00:13AM +0100, Stefano Babic wrote: > Hi Tom, Soeren, > > On 09/01/19 23:39, Tom Rini wrote: [snip] > > Why default? Well, "everyone" > > agrees that defaulting to EFI application support means the widest > > choice of out of the box software support. > > I am unsure about this - just my two cents. > > I agree with you if we are talking about evaluation boards and / or > boards supposed to run different distros (or in any case, more flavour > of software). > > But there are a lot of "custom" boards (maintained in U-Boot) that runs > for a specific project and won't run any other kind of software. If a > device is a navigation system, a network controller, or whatever, it > will just do this job until its EOL. > > Specially for older boards, a new feature should not be activated as > default. At the beginning, police in U-Boot was to set just what should > be required in the bootloader, without setting what is not needed as > default. So default was off instead of on.
So, part of what I'm taking away from all of this is that I really do need to see how many people I can bcc at once before gmail gets really mad at me, Yes, there's a number of end-user devices we have support for in mainline that are intended to be re-used as the manufacturer intended. Part of the Kconfig migration means that they can more easily remove stuff they don't want/need than before. But there's also the repurposed boards, and lots of not really clear cut cases, such as the tbs2910 where while it's not my call, does fall into the "enable EFI loader support for your end users maybe?" category. And in the end, I should have emailed off everyone with a gentle reminder to inspect and trim their configs. -- Tom
signature.asc
Description: PGP signature
_______________________________________________ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot
