dsnejko wrote on Saturday, January 09, 2010:
Working on IAR ColdFire port I realized Code warrior port which I used as a start point doesn’t save EMAC registers in context switching macros. I think it should be fixed.
Regards, Dmitri.
dsnejko wrote on Saturday, January 09, 2010:
Working on IAR ColdFire port I realized Code warrior port which I used as a start point doesn’t save EMAC registers in context switching macros. I think it should be fixed.
Regards, Dmitri.
rtel wrote on Saturday, January 09, 2010:
I’m not sure it would make sense to save the EMAC registers. There is only one EMAC peripheral and that will be having a conversation that cannot be interrupted.
Regards.
dsnejko wrote on Sunday, January 10, 2010:
EMAC is not a peripheral but a core unit. As I understand (may be not right ) all emac commands are atomic and its state and registers should be stored with context. I will rise this question on freescale tech support to clarify.
Regards.
dsnejko wrote on Sunday, January 10, 2010:
I have checked FreeScale MQX dispatch source code. They save/restore EMAC.
Regards.
rtel wrote on Sunday, January 10, 2010:
In which case, apologies, I was thinking “media access controller” rather than “multiply accumulate”.
Regards.
dsnejko wrote on Sunday, January 10, 2010:
Yes, It is a confusing acronym they used.
Should I submit a bug to the tracker? I can make new portasm.s
Regards.