**** BEGIN LOGGING AT Sun Aug 16 02:59:59 2015
**** BEGIN LOGGING AT Sun Aug 16 07:03:17 2015
Aug 16 10:48:06 <_av500_> back
Aug 16 13:28:09 <apaar_> alexanderhiam, ds2:ping
Aug 16 15:16:19 <alexanderhiam> apaar_: pong
Aug 16 16:34:05 <ebadawy> jkridner|desktop: Please check the current change in the home page and let me know your feedback.
Aug 16 16:34:47 <ebadawy> ehab93.github.io/bone101
Aug 16 16:44:43 <nerdboy> moin
Aug 16 16:44:56 <nerdboy> time to wake up...  https://www.youtube.com/watch?v=xxcLNHasPx4
Aug 16 16:46:08 <apaar_> alexanderhiam :sorry was away i will soon be done with the pruspeak port(that took quite a while).Am right now updating readme and cleaning up the code.What would be considered a good peformance/no. of cycles per byte for pru_bridge on the firmware side?
Aug 16 16:47:58 <alexanderhiam> apaar_: I can't remember what karki had measured for timing, but I'd think you'd want to meet or exceed that
Aug 16 16:50:28 <apaar_> oh ok so i compare it with what the original pruspeak code too for the same data? but that is only one off data tranfer for few bytes at a time and also he is accessing global memory while prubridge stays in the local mem map
Aug 16 16:52:40 <nerdboy> then skew the benchmark so it's optimal for your implementation
Aug 16 16:52:50 <nerdboy> just don't tell anyone...
Aug 16 16:53:04 <apaar_> :)
**** ENDING LOGGING AT Mon Aug 17 02:59:58 2015