Issue 24: Migration: i2c http://code.google.com/p/jallib/issues/detail?id=24
Comment #3 by sebastien.lelong: > Did you ever take a look at the software layer on top of this? No, never. About the device list, I don't think these should remain in a lib, these are like default values, and mostly depend on users' projects (there's also hard-coded pin name...). > 1- Give the procedures in HW and SW the same name and include the one you need. > Pro: efficient code. > Con: SW and HW can't be used at the same time. For serial, it's worth having both at the same time. For i2c, it's not very necessary, as i2c is addressable by nature. > 2- Keep the above level of Stef IMHO not sure this is the best choice, mainly because of device list. > 3- Duplicate the above lib for both HW and SW. That is, having two i2c device list ? (not sure to understand...) About i2c slave, it's ok, we can do this later ! My implementation follows Microchip's App. Note AN734A + several bugfix (machine state impl.). And I'm not sure it's possible to put this in a lib with an efficient code... Seb -- 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 -~----------~----~----~----~------~----~------~--~---
