Thanks a lot, Jamie. That is the right thing. After some email with Rob from Freescale, for TO2 rev is 51120 and TO3 rev should be 51130. Oliver's revision might be a bug in U-Boot or something.
So I think using 'cpu_is_mx51_rev(CHIP_REV_3_0)' to do dynamic testing is a safe way to workaround this NEON issue on old silicon. How do you guys think of this? -- CONFIG_NEON=y causes platform lockups with certain application/platform combinations https://bugs.launchpad.net/bugs/507416 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
