diff options
| author | Tomasz Maciej Nowak <tomek_n@o2.pl> | 2020-03-18 19:04:13 +0100 |
|---|---|---|
| committer | Petr Štetiar <ynezz@true.cz> | 2020-03-28 22:58:36 +0100 |
| commit | 43d1d88510621801d66a0a7f46f4c4f44d89633a (patch) | |
| tree | 83a713523f5141d28d98df6ac9fcd2d1e7513979 /target/linux/tegra/config-5.4 | |
| parent | 258f070d1a4fe1808b654f58f50779fd0afafa1a (diff) | |
| download | upstream-43d1d88510621801d66a0a7f46f4c4f44d89633a.tar.gz upstream-43d1d88510621801d66a0a7f46f4c4f44d89633a.tar.bz2 upstream-43d1d88510621801d66a0a7f46f4c4f44d89633a.zip | |
tegra: correct cpu subtype
Tegra 2 processors have only 16 double-precision registers. The change
introduced by 8dcc1087602e ("toolchain: ARM: Fix toolchain compilation
for gcc 8.x") switched accidentally the toolchain for tegra target to cpu
type with 32 double-precision registers. This stems from gcc defaults
which assume "vfpv3-d32" if only "vfpv3" as mfpu is specified. That
change resulted in unusable image, in which kernel will kill userspace as
soon as it causing "Illegal instruction".
Ref: https://forum.openwrt.org/t/gcc-was-broken-on-mvebu-armada-370-device-after-commit-on-2019-03-25/43272
Fixes: 8dcc1087602e ("toolchain: ARM: Fix toolchain compilation for
gcc 8.x")
Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
Diffstat (limited to 'target/linux/tegra/config-5.4')
0 files changed, 0 insertions, 0 deletions