**** BEGIN LOGGING AT Sat Jun 28 02:59:58 2014
Jun 28 03:19:24 <karki> Good morning all ^_^
Jun 28 05:35:21 <Abhishek_> Morning
Jun 28 05:35:28 * Abhishek_ yawns
Jun 28 05:39:12 * karki tries to figure out how to use the universal cape stuff :/
Jun 28 07:53:42 <vvu> morning
Jun 28 08:37:35 <Abhishek_> Hey vvu
Jun 28 09:39:11 <vvu> hey Abhishek_ , what's up ?
Jun 28 12:38:28 * karki wants to go bare metal.........
Jun 28 12:56:26 <Abhishek_> karki: why? kernel isn't enough ;) ?
Jun 28 12:57:50 <Abhishek_> vvu: Long afternoon nap, that's all :)
Jun 28 13:11:08 <vvu> Abhishek_: good good
Jun 28 13:32:05 <Abhishek_> hey sidbh, how's it going with the PRU part of BeaglePilot?
Jun 28 13:33:25 <sidbh> Abhishek_, good, I'm still using older version of PRU compiler, are their any new development in that area?
Jun 28 13:33:57 <Abhishek_> sidbh: things are now cleared with the new PRU compiler.
Jun 28 13:34:30 <sidbh> great! can you provide me with info on that...
Jun 28 13:35:16 <anujdeshpande> Abhishek_: you working on PRU input atm ? or not yet ?
Jun 28 13:35:59 <Abhishek_> anujdeshpande: PRU part of my project is ready for beta
Jun 28 13:36:32 <anujdeshpande> Abhishek_: could you link me your blog ? would love to read more
Jun 28 13:38:03 <Abhishek_> anujdeshpande: some part of that stuff is on http://www.theembeddedkitchen.net/ [not related to the new firmware] and the rest on the BeagleLogic GitHub repo and its wiki
Jun 28 13:38:23 <Abhishek_> anujdeshpande: https://github.com/abhishek-kakkar/BeagleLogic/wiki
Jun 28 13:38:36 <anujdeshpande> Abhishek_: great, thanks
Jun 28 13:46:44 <Abhishek_> sidbh: my PRU firmware with the new PRU compiler) is at https://github.com/abhishek-kakkar/BeagleLogic/tree/master/beaglelogic-firmware
Jun 28 13:47:22 <sidbh> Abhishek_, thanks
Jun 28 15:48:36 <Abhishek_> praveendath92|pc: did you benchmark your driver yet?
Jun 28 15:49:07 <praveendath92|pc> Abhishek_: That's what I was doing this noon.
Jun 28 15:49:29 <praveendath92|pc> I see some abnormally high values and I think something is wrong.
Jun 28 15:49:40 <praveendath92|pc> I mean about the time for transfer.
Jun 28 15:49:58 <praveendath92|pc> How do you track the time for transfer?
Jun 28 15:50:23 <Abhishek_> I used "dd" 90% of the time, wrote my own app last week
Jun 28 15:52:04 <praveendath92|pc> dd for copying?
Jun 28 15:52:50 <Abhishek_> yep, from /dev/beaglelogic to /dev/null
Jun 28 15:54:31 <praveendath92|pc> A dd command on /dev/beaglelogic to /dev/null reads from device?
Jun 28 15:54:41 <Abhishek_> yeah
Jun 28 15:55:05 <praveendath92|pc> For write speeds?
Jun 28 15:55:19 <Abhishek_> no, more for raw read speeds
Jun 28 15:55:45 <Abhishek_> my device node is read-only
Jun 28 15:56:49 <praveendath92|pc> I want to do a write speed test.
Jun 28 15:57:03 <praveendath92|pc> That is more important for me.
Jun 28 15:57:30 <Abhishek_> does your driver wait for the transaction to complete before returning from a write() ?
Jun 28 15:57:37 <praveendath92|pc> I will try on these lines.
Jun 28 15:58:10 <praveendath92|pc> It's a blocking write.
Jun 28 15:58:49 <praveendath92|pc> But each write call can handle a max of 16384 bytes only.
Jun 28 15:59:34 <praveendath92|pc> May be I can try with buffersize in dd.
Jun 28 16:21:59 <praveendath92|pc> Abhishek_: I was using this, https://github.com/praveendath92/bard-linux/blob/master/frontend.c
**** ENDING LOGGING AT Sun Jun 29 02:59:59 2014