Hi Bin, On Tue, 2 Mar 2021 at 18:08, Bin Meng <bmeng...@gmail.com> wrote: > > Hi Tom, > > On Tue, Mar 2, 2021 at 11:35 PM Bin Meng <bmeng...@gmail.com> wrote: > > > > QEMU ppce500 machine can dynamically instantiate an eTSEC device > > if "-device eTSEC" is given to QEMU. > > > > This series updates the fixed-link ethernet PHY driver as well as > > the Freescale eTSEC driver to support the QEMU ppce500 board. > > > > Based-on: > > http://patchwork.ozlabs.org/project/uboot/list/?series=230985 > > > > This series is avaiable at u-boot-x86/eTSEC for testing. > > > > > > Azure results say there are several ARM boards fail to build due to > size overflow with this series. > https://dev.azure.com/bmeng/GitHub/_build/results?buildId=334&view=results > > How do we handle this?
The one I looked at, imx6dl_mamoj seems to be 0xbc5 over the limit. That's a very large growth, indicating that your series is doing something odd, perhaps? I suppose you know this, but you can use: buildman -b try imx6dl_mamoj buildman -b try -sS to see which commit creates the size growth, and -B to see which functions. Regards, Simon
