**** BEGIN LOGGING AT Wed Apr 06 02:59:58 2016
Apr 06 12:52:59 <ZeekHuge> This is interesting, but somehow I broke some part of the kernel I think. Actually the output to lsmod is an empty list, though it was absolutely fine before the last reboot. Is there a way to fix it or I will have to reinstall linux onto it ?
Apr 06 13:53:12 <alexhiam> ZeekHuge: have you checked dmesg?
Apr 06 13:55:20 <alexhiam> ah, nvm, I see you're getting some help in #beagle
Apr 06 13:57:06 <ZeekHuge> alexhiam: ahh yep .. I have started to reinstall the kernel
Apr 06 13:57:36 <ZeekHuge> btw can you please help me with pru_rproc
Apr 06 13:57:55 <alexhiam> not sure...
Apr 06 13:58:40 <ZeekHuge> actually .. the pru_rproc at here https://github.com/beagleboard/linux/blob/4.1/drivers/remoteproc/ have the same desc as pruss_remoteproc
Apr 06 13:59:00 <alexhiam> isn't TI rewriting the pru rproc stuff in their latest kernel?
Apr 06 13:59:02 <ZeekHuge> pruss_remoteproc = https://github.com/shubhi1407/PRU-framework/tree/master/drivers/remoteproc
Apr 06 13:59:08 <alexhiam> what kernel are you using?
Apr 06 13:59:26 <ZeekHuge> wasn't aware of this .. ohk.
Apr 06 14:00:10 <alexhiam> we looked at it here a couple weeks ago and it looked like they weren't done, so we may just have to stick with what's in 4.1 for the time being
Apr 06 14:00:27 <alexhiam> though I may be totally wrong about that...
Apr 06 14:01:48 <ZeekHuge> whom can I ask about that ?
Apr 06 14:02:54 <alexhiam> idk... why not just use 4.1?
Apr 06 14:03:56 <alexhiam> you could try to get in touch with whoever maintains pru_rproc at TI
Apr 06 14:06:53 <ZeekHuge> I had 4.1.17 and there pruss_remoteproc was working. But all from 4.1.17 down to 4.1.13 all are 'realtime versions. I have 4.1.18 now with the pru_rproc in it and absence of pruss_remoteproc
Apr 06 14:09:22 <ZeekHuge> I think its Suman Anna.
Apr 06 14:13:31 <alexhiam> ZeekHuge: do you need an rt kernel?
Apr 06 14:36:56 <chanakya_vc> Hey alexhiam ,mr_science,I tried the method that you suggested for the makefile.I am not able to understand how to include custom header files that I have written
Apr 06 14:38:12 <chanakya_vc> The basic problem is that it is not compiling the header file that I wrote,which is common to the driver and the user app.Could you please help?
Apr 06 14:38:26 <alexhiam> chanakya_vc: is it on github?
Apr 06 14:39:24 <chanakya_vc> https://github.com/chanakya-vc/BBB-Gsoctry/tree/master/ioctlsdriver
Apr 06 14:39:41 <alexhiam> capital 'M'!
Apr 06 14:39:56 <chanakya_vc> I have not debugged it completly.So might contain some syntax errors
Apr 06 14:40:10 <chanakya_vc> Ohh I corrected that on my local copy
Apr 06 14:40:18 <chanakya_vc> did not update there.
Apr 06 14:45:06 <alexhiam> what's the error that you're getting?
Apr 06 14:52:02 <Abhishek_> morning
Apr 06 14:52:17 <chanakya_vc>  alexhiam, error: expected ‘)’ before ‘;’  #define query_getvar  _IOR('q',1,query_for_ioctls *);
Apr 06 14:52:28 <chanakya_vc> And the same for all the macros.
Apr 06 14:53:11 <chanakya_vc> defined in query_ioctls.h
Apr 06 14:53:37 <alexhiam> chanakya_vc: with this makefile? are you sure you don't have changes you haven't pushed?
Apr 06 14:54:09 <alexhiam> for one you have `default: module App_to_perform_ioctls`, which I think should be `default: module query_ioctldriver`
Apr 06 14:54:41 <chanakya_vc> It starts with App_to_perform_ioctls only.
Apr 06 14:55:02 <alexhiam> isn't that a userspace program to test the driver?
Apr 06 14:55:05 <chanakya_vc> These errors in making the above file only.
Apr 06 14:55:09 <chanakya_vc> Yes
Apr 06 14:55:22 <alexhiam> then why are you trying to build it as a kernel module?
Apr 06 14:57:26 <chanakya_vc> I guess that is a mistake.
Apr 06 14:57:48 <chanakya_vc> I thought we could build both of these in a single makefile?
Apr 06 14:58:25 <alexhiam> sure, but not both as modules
Apr 06 14:59:48 <chanakya_vc> I just changed it .Got the error as: linux/module.h: No such file or directory : #include <linux/module.h>
Apr 06 15:00:03 <chanakya_vc> I guess I have to add targets?
Apr 06 15:00:33 <chanakya_vc> Or I am doing some other mistake
Apr 06 15:00:34 <alexhiam> well you haven't defined the KERNEL_SOURCE variable
Apr 06 15:00:50 <chanakya_vc> Okay will do that.
Apr 06 15:01:28 <alexhiam> oh sorry, forget what I said about the default line, I was not thinking straight :P
Apr 06 15:02:29 <alexhiam> but better to define directives for everything instead of trusting that gcc will guess right
Apr 06 15:04:28 <chanakya_vc> Okay.I am a bit confused about makefiles.Can you recommend any source for it?
Apr 06 15:04:43 <chanakya_vc> I need to study it a bit.
Apr 06 15:04:54 <alexhiam> https://www.gnu.org/software/make/manual/html_node/index.html#SEC_Contents
Apr 06 15:05:31 <alexhiam> something like this should get you to where you can start fixing your syntax errors: http://pastebin.com/kFBSgePR
Apr 06 15:05:52 <chanakya_vc> I will go through it.Thanks.
Apr 06 15:06:10 <alexhiam> the first thing you'll want to fix is the semicolons in your defines in query_ioctls.h!
Apr 06 15:06:34 <alexhiam> https://github.com/chanakya-vc/BBB-Gsoctry/blob/master/ioctlsdriver/query_ioctldriver.c#L36
Apr 06 15:07:01 <alexhiam> when that define is expanded you end up with `case _IOR('q',1,query_for_ioctls *);:`
Apr 06 15:07:25 <chanakya_vc> Yes that is the error I was getting with App
Apr 06 15:07:25 <alexhiam> semicolons should never be at the end of a define
Apr 06 15:07:42 <chanakya_vc> Careless of me :(
Apr 06 15:07:58 <alexhiam> I also see some missing commas and semicolons here and there
Apr 06 15:08:05 <alexhiam> it's debugging time ;)
Apr 06 15:08:38 <chanakya_vc> Yup I guess so.It is one of the most difficult tasks :)
Apr 06 15:10:05 <chanakya_vc> Apart from the syntax errors,what do you think about the code?I put comments explaining all functions that I have defined.
Apr 06 15:14:06 <chanakya_vc> alexhiam, What would you want me to work on, after I am done with this?
Apr 06 15:20:45 <alexhiam> chanakya_vc: you want default cases in your switch statements
Apr 06 15:21:16 <alexhiam> and check your formatting, there's some inconsistent whitespace
Apr 06 15:21:55 * alexhiam heads to lunch
Apr 06 15:22:12 <Abhishek_> meeting in ~40 minutes now?
Apr 06 15:22:47 <chanakya_vc> alexhiam, Okay I will do that.
Apr 06 15:23:59 <chanakya_vc> alexhiam, Will look into the formatting bit.I nearly spent all my time researching all the structures and functions that are required :)
Apr 06 15:42:02 * hpfmn is ready for the meeting :)
Apr 06 15:51:15 <alexhiam_> Meeting in 10min?
Apr 06 16:01:39 <hpfmn> hmm
Apr 06 16:01:41 <hpfmn> nobody there?
Apr 06 16:02:31 <Abhishek_> everyone's here
Apr 06 16:02:44 <Abhishek_> well, not exactly everyone but still
Apr 06 16:02:50 <hpfmn> ;)
Apr 06 16:08:54 <hpfmn> hi rma_
Apr 06 16:10:39 <rma_> hi there how r u?
Apr 06 16:12:37 <hpfmn> rma_: I'm fine ;) - was everything good at superbooth?
Apr 06 16:15:02 <rma_> great meeting, we had lots of fun and great that we could meet in person!
Apr 06 16:15:13 <rma_> we are just discussing the projects in the mentors channel
Apr 06 16:47:07 <jkridner> any students lurking?
Apr 06 16:47:16 <ZeekHuge> yep I am here :)
Apr 06 16:47:35 <jkridner> hi ZeekHuge!
Apr 06 16:47:45 <ZeekHuge> Hey jkridner !
Apr 06 16:47:47 <jkridner> Just seeing who responds. :-)
Apr 06 16:48:13 <jkridner> ZeekHuge: have you meet any other potential students?
Apr 06 16:48:17 <jkridner> er, met
Apr 06 16:49:14 <ZeekHuge> met ?, well I had a casual chat with chanakya_vc sometime back .
Apr 06 16:50:11 <ZeekHuge> Is there something to inform them or him ?
Apr 06 16:50:19 * hpfmn is there
Apr 06 16:50:54 <hpfmn> jkridner: how is it going?
Apr 06 16:51:35 <_av500_> hpfmn: working on it :)
Apr 06 16:51:51 <jkridner> tough picking and finding enough mentorship to handle all the great proposals.
Apr 06 16:52:10 <hpfmn> sound good :)
Apr 06 16:52:23 <jkridner> ZeekHuge: no, just trying to foster more discussion among #beagle-gsoc'rs
Apr 06 16:52:33 <ZeekHuge> should I try to call chanakya_vc. We are connected on fb .
Apr 06 16:52:36 <ZeekHuge> ?
Apr 06 16:52:37 <jkridner> ZeekHuge: and find if people are actually chatting much.
Apr 06 16:53:03 <jkridner> nope... more interested in who lurks in #beagle-gsoc around this time of day and who people run into here.
Apr 06 16:53:38 <ZeekHuge> ohk ..:)
Apr 06 17:01:04 <ZeekHuge> alexhiam: I have been advic
Apr 06 17:01:21 <ZeekHuge> alexhiam: I have been advised to use non-rt kernel unless required.
Apr 06 17:03:57 * ZeekHuge broke his BBB, the USB port just .. ahh .. got detached .... :(
Apr 06 17:04:49 <hpfmn> poor thing
Apr 06 17:05:49 <ZeekHuge> jkridner: Can you something tell about the changes that ti-people are making in the remoteproc system for PRUs ? like how much time will it take to get completed or .. what they are ultimately trying to do ?
Apr 06 17:08:27 <Abhishek_> ZeekHuge: that's sad :(
Apr 06 17:09:16 <jkridner> ZeekHuge: can you put that in the form of an e-mail? I will forward to the folks working on remoteproc within TI.
Apr 06 17:09:28 <jkridner> send to me @beagleboard.org
Apr 06 17:09:56 * Abhishek_ would like to be CC'd as well
Apr 06 17:11:03 <udayansinha> jkridner: me too...I'm a student too :)
Apr 06 17:11:07 <ZeekHuge> Ohk. sure Abhishek_, Will do. If that gets completed before coding period, it would be a good starting point then ..
Apr 06 17:13:42 <Abhishek_> The kernel stuff is constantly changing, so I do not have high expectations about it being "completed", but then having something stable enough to work with, that's something
Apr 06 17:15:31 * ZeekHuge agrees ..
Apr 06 17:15:46 <ZeekHuge> this is cool https://github.com/dinuxbg/gnupru, though unofficial.
Apr 06 17:16:51 <Abhishek_> as in, I'd prefer TI ppl not to surprise us with a new driver API midway, assuming the project gets shortlisted.
Apr 06 17:21:16 <rma_> still depating projects but priorization is moving forward
Apr 06 17:21:36 <ZeekHuge> yes .. even the presence of pruss.ko and pru_rproc.ko in 4.1.18 surprised me ! 4.1.17-rt had pruss_remoteproc only. And more, prus_rproc and pruss_remoteproc have a part of code same. while their description is exactly same. But pru_rproc exports some symbols to be used.
Apr 06 17:22:28 <Abhishek_> you see
Apr 06 17:22:45 <hpfmn> rma_: do you have an idea when there might be some more information? or is it even allowed to say something before april 22nd?
Apr 06 17:23:27 <ZeekHuge> also I wasn't able to get PRU-framework working on 4.1.18. It was working on 4.1.17-rt ..
Apr 06 17:23:29 <Abhishek_> No. The results are gonna be announced by Google.
Apr 06 17:23:34 <Abhishek_> not us
Apr 06 17:23:48 * ZeekHuge - Change is the only constant !
Apr 06 17:24:44 <hpfmn> thx Abhishek_
Apr 06 17:32:04 <ZeekHuge> maybe this commit explains (or provide some extra info ) <https://git.ti.com/pru-software-support-package/pru-software-support-package/commit/9107429410e43305372fdb66e434658e9b0f9947> what TI-folks doing . pru_vring.h is required for pruss_remoteproc to work.
Apr 06 17:35:38 <Abhishek_> hmm, makes sense
Apr 06 17:36:00 <m_w> Hello from ELC
Apr 06 17:36:49 <m_w> I am without laptop so this is painful.
Apr 06 17:38:42 <Abhishek_> Hey m_w
Apr 06 17:38:56 <Abhishek_> m_w: Can you get on #beagle-mentors?
Apr 06 17:40:19 <m_w> Sure
Apr 06 17:42:00 <ZeekHuge> ar
Apr 06 17:42:21 * ZeekHuge is sorry for that ..
Apr 06 19:26:47 <ZeekHuge> Abhishek_: can I get your email id please ?
Apr 06 19:27:32 <ZeekHuge> to CC you in the mail ..
Apr 06 20:00:20 <ZeekHuge> is this the mailing id of jkridner ? @beagleboard ? - jasonkridner@beagleboard.org ?
Apr 06 20:04:50 <alexhiam> ZeekHuge: jkridner@beagleboard.org
Apr 06 20:05:42 <ZeekHuge> ohk thankyou .. and Abhishek_'s ? if you could tell ? is it abhishek@theembeddedkitchen.net
Apr 06 20:05:44 <ZeekHuge> ?
Apr 06 20:07:17 <alexhiam> that'll work
Apr 06 20:12:29 <ZeekHuge> jkridner: will this be okay ? https://docs.google.com/document/d/1Dtrl51Tp9tblBD5I3JDWjsTvAciJeI5xwZKP70iApKw/edit?usp=sharing
Apr 06 20:12:50 * ZeekHuge dont know it is OK to ask it ..
Apr 06 20:38:16 <ZeekHuge> jkridner: is there anything to add/change ?
Apr 06 20:41:45 <jkridner> doh.... was replying in the wrong room.
Apr 06 20:41:54 <jkridner> the TI team is focused on mainline, not the Beagle tree. Have you compared what rcn-ee merged with what is upstream?
Apr 06 20:41:57 <jkridner> questions like #1 are a bit difficult for them to answer, since it depends quite a bit on the community. A better question would be something like "are you planning to push any additional changes?"
Apr 06 20:42:00 <jkridner> #2 is not in the form of a question.
Apr 06 20:42:03 <jkridner> #3 is really closer to the question you should ask for #1, but I don't think putting a bounds on the GSoC timeframe is necessary.
Apr 06 20:46:04 <jkridner> ZeekHuge: ^^^
Apr 06 20:46:29 <jkridner> ZeekHuge: do you know how to look at the deltas from mainline and where to find mainline?
Apr 06 20:46:35 <jkridner> mainline == upstream
Apr 06 20:47:20 <ZeekHuge> ahh .. not exactly.
Apr 06 20:47:45 <ZeekHuge> I was looking at the beaglebone tree...
Apr 06 20:47:52 <pmezydlo> bradfa: I also would like to know if I should add or change something (in my application)?
Apr 06 20:50:15 <jkridner> ZeekHuge: have you seen http://baylibre.com/acme/
Apr 06 20:50:16 <jkridner> ?
Apr 06 20:51:26 <jkridner> ZeekHuge: have you compared your proposal with that?
Apr 06 20:52:05 <ZeekHuge> No i didn't came along it .. looking at it now.
Apr 06 20:53:20 <jkridner> k. I know the guys that designed it. Seems your proposal might benefit from building upon it.
Apr 06 20:55:43 <ZeekHuge> Ohk so they are providing the hardware, its driver and the userspace sigrok SW .. right ?
Apr 06 20:59:35 <ZeekHuge> btw they have used the ADC with 7KHz max sampling rate, while BBB can handle upto about 15-20 MHz
Apr 06 21:01:32 <jkridner> seems they made a pretty slow solution: 140us conversion time minimum
Apr 06 21:01:33 <jkridner> yup.
Apr 06 21:01:42 <ZeekHuge> and it is without using the PRUs ? .. it seems so ..
Apr 06 21:01:50 <jkridner> probably without, yeah.
Apr 06 21:01:57 <jkridner> their ADC seems too slow.
Apr 06 21:02:17 <jkridner> not a SPI or parallel ADC.... using I2C! :(
Apr 06 21:02:30 <ZeekHuge> But yes the userspace part and sigrok binding will be cool !
Apr 06 21:02:39 <ZeekHuge> and the cape part too !
Apr 06 21:26:04 <ZeekHuge> jkridner: So it seems that hardwares like this ACME cape will greatly be benefited by this project (ofc with some modification)
Apr 06 21:32:00 * jkridner doesn't see PRU support in http://git.ti.com/ti-linux-kernel/ti-linux-kernel/trees/linux-4.4.y/drivers/remoteproc
Apr 06 21:32:10 <jkridner> ds2: ^^^ ???
Apr 06 21:32:38 <jkridner> https://github.com/beagleboard/linux/tree/4.1/drivers/remoteproc has more stuff.
Apr 06 21:33:12 <jkridner> not in http://git.ti.com/ti-linux-kernel/ti-linux-kernel/trees/ti-linux-4.4.y/drivers/remoteproc either
Apr 06 21:33:49 <jkridner> ahh... all in http://git.ti.com/ti-linux-kernel/ti-linux-kernel/trees/ti-linux-4.1.y/drivers/remoteproc :(
Apr 06 21:34:27 * jkridner wonders why it doesn't seem to include panto-cloud in the history
Apr 06 21:34:51 <jkridner> http://git.ti.com/ti-linux-kernel/ti-linux-kernel/blobs/ti-linux-4.1.y/drivers/remoteproc/pru_rproc.c
Apr 06 21:35:16 <panto-cloud> jkridner: I was deleted from memory it seems
Apr 06 21:35:24 <jkridner> :(
Apr 06 21:47:57 * jkridner compares https://github.com/beagleboard/linux/tree/4.1.17-ti-rt-r48/drivers/remoteproc to https://github.com/beagleboard/linux/tree/4.1.18-ti-rt-r56/drivers/remoteproc
Apr 06 21:49:06 <jkridner> ZeekHuge: It seems to follow a reasonable history actually...
Apr 06 21:49:12 <jkridner> https://github.com/beagleboard/linux/commit/3bc4dfbdca01291167d3039339f7df37ec7ebfa3 splits the driver
Apr 06 21:51:10 <jkridner> seems rcn-ee might have missed applying https://github.com/beagleboard/linux/commit/d5ad86346f389917a6b3abae036bbfdcc8af61d8
Apr 06 21:53:12 <jkridner> oh, nope, it's there: https://github.com/beagleboard/linux/blob/4.1.18-ti-rt-r56/drivers/remoteproc/pru_rproc.c#L251
Apr 06 22:00:25 <ZeekHuge> jkridner: ohk so they arent changing it, just re-organizing it into logical chunks.
Apr 06 22:01:08 <ZeekHuge> right ?
Apr 06 22:01:49 <jkridner> that's what that patch looks like to me
Apr 06 22:03:35 <ZeekHuge> hmm .. things are quite clear now ... finally.
Apr 06 22:03:48 <ZeekHuge> thank you jkridner :)
Apr 06 22:04:10 <ZeekHuge> And now no need for that mail.
Apr 06 22:12:55 <ZeekHuge> Cool ! there the mail goes ..
Apr 06 22:16:42 * ZeekHuge will be going to bed now, its 3:46 AM here.
Apr 06 22:16:58 <ZeekHuge> jkridner: Thank you :)
**** ENDING LOGGING AT Thu Apr 07 02:59:58 2016