Hi Joshua, On 12/28/2011 09:17 PM, Joshua Juran wrote:
On Dec 27, 2011, at 9:53 PM, Greg Ungerer wrote:if (CPU_IS_COLDFIRE) { __asm__ volatile ("fsave %0" : : "m" (*sc->sc_fpstate) : "memory"); } else { __asm__ volatile (".chip 68k/68881\n\t" "fsave %0\n\t" ".chip 68k" : : "m" (*sc->sc_fpstate) : "memory"); } I am still concerned about the use of ".chip 68k" in general though. Just not sure how we can avoid it. I guess there is no way to jus t revert to the original CPU choice?#define CPU "68040" _asm__ volatile (".chip 68k/68881\n\t" "fsave %0\n\t" ".chip " CPU : : "m" (*sc->sc_fpstate) : "memory");
Possibly. Regards Greg ------------------------------------------------------------------------ Greg Ungerer -- Principal Engineer EMAIL: gerg@xxxxxxxxxxxx SnapGear Group, McAfee PHONE: +61 7 3435 2888 8 Gardner Close, FAX: +61 7 3891 3630 Milton, QLD, 4064, Australia WEB: http://www.SnapGear.com -- To unsubscribe from this list: send the line "unsubscribe linux-m68k" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
