On Thu, Oct 19, 2017 at 01:39:28PM +0200, Mark Kettenis wrote: > > From: Maxime Ripard <maxime.rip...@free-electrons.com> > > Date: Thu, 19 Oct 2017 10:26:49 +0200 > > > > The EFI loader support takes around 31kB on an ARMv7 board, which makes us > > trip across the size limit we've had on the U-Boot binary. > > > > Since it's not an essential feature, disable it by default for ARCH_SUNXI > > so that we get back some extra room for user customisations. > > This is an essential feature for booting OpenBSD. And I believe it is > a requirement for several Linux distros as well. I don't think > disabling this by default is a good idea.
I get it, every one wants its old features. We can't have that. Can we move forward in the discussion? > How much of that 31kB is due to recent improvements of the EFI loader > support? I understand the desire to have a more complete EFI > implementation, but if the consequence of that is that the EFI loader > gets disabled by default on many boards I think we're throwing out the > baby with the bathwater... Bisection led to a meaningless (as in not relevant to the current discussion) commit that was just adding a bit of code, and probably was just tripping over the limit. So it's basically only a symptom, and it shouldn't prevent any development from happening. What I'd like to happen though is a real discussion on why on Earth we should have all the usecases in the worlds supported in our defconfigs, especially for distros that will package and build U-Boot themselves. Everyone has a custom defconfig for the kernel. What's so different? Maxime -- Maxime Ripard, Free Electrons Embedded Linux and Kernel engineering http://free-electrons.com
signature.asc
Description: PGP signature
_______________________________________________ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot
