You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is Issue 340 moved from a Google Code project.
Added by 2010-08-29T17:32:33.000Z by [email protected].
Please review that bug for more context and additional comments, but update this bug.
Closed (Fixed).
Original labels: Type-Enhancement, Priority-Medium, Milestone-0022, Component-Core
Original description
What change would like to see?
Modification of WInterrupts.c to use register #ifdefs instead of cpu #ifdefs
Why?
To support more cpus without having to keep adding more and more ifdefs
Would this cause any incompatibilities with previous versions? If so, how can these be mitigated?
This is Issue 340 moved from a Google Code project.
Added by 2010-08-29T17:32:33.000Z by [email protected].
Please review that bug for more context and additional comments, but update this bug.
Closed (Fixed).
Original labels: Type-Enhancement, Priority-Medium, Milestone-0022, Component-Core
Original description
What change would like to see?
Modification of WInterrupts.c to use register #ifdefs instead of cpu #ifdefs
Why?
To support more cpus without having to keep adding more and more ifdefs
Would this cause any incompatibilities with previous versions? If so, how
can these be mitigated?
No, it has been tested on the following cpus
atmega8
atmega168
atmega169
atmega328p
atmega128
atmega644
atmega644p
atmega645
atmega324p
atmega32
atmega1281
atmega1280
atmega2560
atmega2561
If anyone knows of a board that uses some other cpu, please let me know.
The text was updated successfully, but these errors were encountered: