**** BEGIN LOGGING AT Tue Jun 24 02:59:59 2014 Jun 24 03:51:55 Abhishek_: btw got your code to work :) Jun 24 08:13:04 mranostay: sigrok bindings by this weekend :) Jun 24 08:59:07 av500: vvu: It worked :D Jun 24 08:59:33 good Jun 24 08:59:36 so what can you do now? Jun 24 08:59:41 The data transfer from PC - Android from kernel space. Jun 24 08:59:49 Need to clean up first. Jun 24 08:59:57 good Jun 24 09:00:00 A lot of mess while testing. Jun 24 09:00:03 sure Jun 24 09:00:09 messting Jun 24 09:00:13 Currently just 3 bytes for testing. Jun 24 09:00:25 So, I will try and increase that limit. Jun 24 09:01:08 Laptop running out of charge and power cut. Jun 24 09:09:44 #hacked Jun 24 09:10:37 praveendath92: clean up and make the exquisite push to git Jun 24 09:11:19 vvu: Surprisingly no changes in kernel module. Jun 24 09:11:34 Just a new runnable in Java. Jun 24 09:11:52 yep, do not block UI thread while reading/writing Jun 24 09:12:09 A new thread is being used. Jun 24 09:12:39 it complains a lot when u hack on UI thread Jun 24 09:13:03 Hmm. Actually it force closes. Jun 24 09:13:19 yep cuz it runs out of mem i think so Jun 24 09:13:30 if you look at logcat then u will see a lot of freeing and alloc Jun 24 09:13:32 No long processes on UI thread. Yep. Jun 24 09:13:58 you have something workOnUIThread method predefined i think so Jun 24 09:14:43 runOnUiThread(Runnable action); Jun 24 09:15:03 Yeah. Now that I also have the new Google APIs, I will shift things to bard-droid repo Jun 24 09:16:03 There aren't many runnables in the code actually. Just 2. One for writing to BB and other for readinf from board. Jun 24 09:16:17 Which code are you looking at vvu ? Jun 24 09:16:54 that is just a paste from google.com Jun 24 09:17:03 if you wanna run smth on UI thread use that Jun 24 09:17:08 but do not abuse it Jun 24 09:18:46 Oh. Sure. I won't :) Jun 24 09:19:28 Not so new to Android dev'ing. Jun 24 10:57:59 karki: ping Jun 24 11:11:11 * Abhishek_ is thinking that his small rproc hook can be backported to the botspeak driver Jun 24 18:06:14 panto: can you see anything in the mmap method that could trigger a segfault? https://github.com/abhishek-kakkar/BeagleLogic/blob/master/beaglelogic-kernel-driver/beaglelogic.c#L594 Jun 24 18:12:55 Abhishek_: what do you have left to implement ? Jun 24 18:13:26 vvu: The kernel driver is feature complete (with some odd bugfixes to make as I go) Jun 24 18:13:35 I whipped up a test app today Jun 24 18:14:08 so now u need to interface sigrok with it ? Jun 24 18:14:08 I am building a userspace bridge for the BeagleLogic stuff Jun 24 18:14:16 and beginning work on the sigrok bindings Jun 24 18:14:49 vvu: but you can still use it with sigrok using its raw binary input format Jun 24 18:14:56 I grabbed some stuff using it Jun 24 18:15:00 nice nice Jun 24 18:15:21 that's what I showed in my last week's update and the meeting Jun 24 18:15:45 i really hope i`ll have some time to test some of the projects Jun 24 18:15:59 work was painful these days Jun 24 18:30:53 Abhishek_, I'll have to find some time Jun 24 18:31:00 k Jun 24 18:36:49 when I tried to access the mapped region in userspace, I got a segfault, thought you might be able to point out something in that particular line. Jun 24 19:59:48 just an update on the channel: I just got a reply from rcn-ee that the BeagleLogic driver is staged in the BeagleBoard 3.8 tree Jun 24 22:07:07 rcn-ee: can i be cool like you and have a kernel tree named after me? :P **** ENDING LOGGING AT Wed Jun 25 02:59:58 2014