Comment #1 on issue 53 by jsuijs: i2c hardware slave routine http://code.google.com/p/jallib/issues/detail?id=53
I like a buffer as an interface. It only requires one routine by the user, which is simple since the user gets the full message to handle (no state to track, info to store etc). Downside: - It can't cope with real large messages (beyond buffer size). - I have no way yet to trigger processing when the master sends a number of bytes, followed by a stop. The master must read at least one byte back to trigger processing -- 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 -~----------~----~----~----~------~----~------~--~---
