@Dave, Appreciate for this useful information.
If I understand correctly, I think our goal is to make one kernel for all the imx51 silicon. On the good silicon, we enable all the NEON and VFP. On the bad silicon, we disable the NEON and add some hack in unaligned access code. So we are going to do following things in kernel, 0, turn on CONFIG_NEON=y 1. dynamic detect the silicon rev 2. if rev < 3, we disable NEON by setting ASEDIS 3. if rev < 3, we add some hack in alignment_init() of arch/arm/mm/alignment.c. 4. my patch -- 'remove NEON flag of HWCAP dynamically' -- is still helpful for user space to run non-NEON version code. But, I just think if we add some hack in alignment_init to handle all the unaligned access for both NEON or none NEON, we don't need to disable NEON at all, since this is an unaligned access issue not a specific NEON one. -- 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 [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
