On 12/02/18 15:47, Tom Rini wrote:
> On Mon, Feb 12, 2018 at 01:25:21AM +0000, Andre Przywara wrote:
>> The current master fails to build some Allwinner H5 boards, due to
>> exceeding the U-Boot proper size limit we currently have still in place.
>> This affects:
>> - nanopi_neo2_defconfig
>> - nanopi_neo_plus2_defconfig
>> - orangepi_pc2_defconfig
>> - orangepi_prime_defconfig
>> - orangepi_zero_plus2_defconfig
>> To workaround this issue, a left-over low hanging fruit is to disable
>> the MII *command*, which is probably only useful for debugging and not
>> needed for a normal boot flow, even when booting via network (PXE/TFTP).
>> Allow to de-select CMD_MII, even when the distro default enables it.
>> Then disable it explicitly in the affected board's defconfigs.
>> This makes all Allwinner ARMv8 boards build again.
>> Signed-off-by: Andre Przywara <andre.przyw...@arm.com>
>> ---
>> Hi,
>> my sincere apologies for this ugly hack (and I welcome any nicer solution!),
>> but we are running out of silver bullets for this particular problem and this
>> command seems both easy to give up and worthwhile in terms of code size
>> savings (~11KB).
>> The "default n if ..." doesn't seem to work with "imply", so I needed to
>> disable it in each of the affected defconfigs. Please let me know if there
>> is a better solution.
> Can we not move the env location now?  Thanks!

Not yet, unfortunately. As of v2018.01 we store the environment in raw
MMC still and need to obey the limit. The just merged multi-env support
allows us to *transition* all users over to a FAT environment (because
it will pickup the env from MMC, but save it in FAT by default). But we
need at least one release to be nice to our users: v2018.03. In this
time we still need to obey the limit, to not destroy the existing legacy
env in MMC.
With v2018.05-rc1 we can then disable ENV_IS_IN_MMC and remove the limit.

So the end is nigh ;-), but not there yet.


U-Boot mailing list

Reply via email to