> 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.
Babbage 2.0 still gives the strange value 51020 in /proc/cpuinfo (using redboot 200930-0ubuntu1 I think). > 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. This won't match 51020 or 51120, so I guess it should work. -- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. -- 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
