2009/2/28 Sebastien Lelong <[email protected]>: > So, does this mean it doesn't go to "project" anymore ?... Isn't this a > project ? Ah... Sure it is. The board file just gave me a flying start (dutch expression, also english or french?).
> > I'm sorry but I can't figure out why you need to _lcd_flush(). What does > flush mean in this case ? I may have miss something... Yes, you missed the part I did not share yet (the technical design). Basicly the master will send chars to the slave (either serial or i2c) and each byte is processed by the slave. So it is a stream and serial is very convenient for this. For i2c however, bytes are bundled in messages. The question is how to know when there is a next byte expected (so we get longer messages, less overhead). And when the expected byte is delayed, so is part of the display update. > Whatever it is, I'd say "make it flexible" :) Sure. But that will be not that efficient. So I am thinking about default fast (and less efficient) and optionally more efficient. Flush is required to trigger tranfer so no pending data is left. 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 -~----------~----~----~----~------~----~------~--~---
