[OpenWrt-Devel] [PATCH] mvebu, tegra: make CPU subtype default to vfp3-d16

Tomasz Maciej Nowak tomek_n at o2.pl
Wed Apr 1 12:07:58 EDT 2020

W dniu 01.04.2020 o 16:52, Klaus Kudielka pisze:
> Hi Petr & Tomasz,
>> In order to fix those issues Tomas in commit 2d61f8821c7c ("mvebu:
>> cortexa9: correct cpu subtype") and commit 43d1d8851062 ("tegra: correct
>> cpu subtype") changed the CPU subtype to explicit vfpv3-d16 which fixed
>> the above mentioned issue, but on the other end it has resulted in the
>> need of building packages for this new CPU subtype which is not wanted
>> due to the increased infrastructure costs, like disk space and
>> additional build time which is huge for packages feed.
> I certainly don't understand all aspects of the build system, but I
> checked over and over again.
> [0]$ find target -type f -exec grep -H CPU_SUBTYPE {} \; | grep vfpv3
> target/linux/mvebu/cortexa9/target.mk:CPU_SUBTYPE:=vfpv3-d16
> target/linux/omap/Makefile:CPU_SUBTYPE:=vfpv3
> target/linux/sunxi/cortexa8/target.mk:CPU_SUBTYPE:=vfpv3
> target/linux/tegra/Makefile:CPU_SUBTYPE := vfpv3-d16
> omap & sunxi/cortexa8 are both cortex-a8.
> So, tegra and mvebu/cortexa9 are the *only* targets with arm_cortex-a9_vfpv3
> (-d16) packages?
> If we switch both, like Tomasz did, arm_cortex-a9_vfpv3 would not be needed
> anymore, and be replaced by -d16. Why does that cost more resources?

Indeed, I always forget about omap and zynq being cortex-a8.

> (Okay, a few snapshot users would have to upgrade if they want to install
> packages, but this is the master branch anyway)

This commit also would make it un-portable to 19.07 branch, since package
directories structure wouldn't change. So if OpenWrt would announce 19.07.3
users of 19.07.2 or earlier would possibly end up with incompatible packages,
when installing something from packages repository.

> Nevermind, just a stupid idea, to avoid unneeded complexity.
> Please ignore it, if I'm wrong.

Nothing wrong with what You wrote, thanks for pointing all of it out.

> Klaus

Sorry for noise, added OpenWrt list.


openwrt-devel mailing list
openwrt-devel at lists.openwrt.org

More information about the openwrt-devel mailing list