Hi, I changed my mind: the app will be based on a board file - your board file, Seb ;)
My first step in this will be the serial support and this looks straight forward. And when this is done, i2c slave could be added. There is already one issue: straight forward implementation will generate one i2c message for each byte written to the display. This could be made smarter (read: more efficient) but that requires a command like _lcd_flush(). And the use of this flush could be integrated into h44780_common, making it a bit more efficient. I think this is not worth the effort. We could also let the user call flush and that would make it much more efficient. But when the user does not call flush (but did configure he would) then there will be delayed updates... What do you think? Joep --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
