Hi All, Good to see some life back on this project! Today I adapted i2c_hw_slave to work with jallib and created a timer-0 lib (for fixed interval ISR). Not yet ready to add to jallib but it is in the process!
As for ETP: my idea is to forget about testing the library suite. Test what you are working on as far as it is possible. Ask someone else if you concider testing on a certain configuration is mandatory. Then release and respond to user feed back. No feedback means it's good enough. And on specific files: Only in unvalidated/include/jal: now.jal Seems to be a special file. It defines the setting for a specific application and I don't know if it should be included as a lib. I think there should be a way to put this in the application program itself. And if it is only a default, it could be in the lib itself... Only in unvalidated/include/peripheral/i2c: i2c_level1.jal Should be added. It is better to use this level1 routine then the level0 routines it calls. How can we notify users of this? Maybe we should not add the level0-based examples. How about generating samples from test/board files? Is this still concidered a real option? I seem the only one working with this setup... 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 -~----------~----~----~----~------~----~------~--~---
