Comment #10 on issue 94 by robhamerling: Legacy aliasing enhanced modules in device files http://code.google.com/p/jallib/issues/detail?id=94
Inventarisation of naming conflicts for ECCPxCON registers like: 'alias CCPxCON is ECCPxCON' (x in range 1 to 10). There are 8 PICs which will give a naming conflict: 18F448, 4480, 458, 4580, 4584, 4680, 4682, and 4685. All these PICs have 1 legacy CCP module and 1 enhanced CCP module, and the control registers are called CCP1CON and an ECCP1CON (these PIC have no other [E]CCPxCON registers). There are no other PICs or other CCPxCON registers which would give a similar naming conflict with a alias declaration as above. Proposed solution for this naming conflict for these PICs is to declare the aliases for the enhanced CCP module as: 'alias CCP2CON is ECCP1CON' Herewith the enhanced module becomes available as second legacy CCP module, and for example the PWM library would now support 2 PWM ports. Sidenote: The current PWM libraries do not support the enhanced CCP modules of the PICs mentioned above. I see this as an experiment for further developments in this area. An alternative naming convention could be implemented with relatively little work. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jallib?hl=en -~----------~----~----~----~------~----~------~--~---
