Observed for example running ffplay to decode H.264 video on Babbage 2.0
This needs to be worked around by a separate kernel image for the affected platforms, or the ability to enable or disable CONFIG_NEON at boot.
Note that the principal problem here is the reporting of neon in the auxv AT_HWCAP word and /proc/cpuinfo which may mislead userspace apps into using NEON.
The NEON context-switching code enabled by CONFIG_NEON should not itself cause problems.
Observed for example running ffplay to decode H.264 video on Babbage 2.0
This needs to be worked around by a separate kernel image for the affected platforms, or the ability to enable or disable CONFIG_NEON at boot.
Note that the principal problem here is the reporting of neon in the auxv AT_HWCAP word and /proc/cpuinfo which may mislead userspace apps into using NEON.
The NEON context-switching code enabled by CONFIG_NEON should not itself cause problems.