**** BEGIN LOGGING AT Fri Jan 30 03:00:00 2015 Jan 30 14:41:03 Is anyone active here now ? Jan 30 14:42:06 I have some questions ! Jan 30 14:42:29 I'm active Jan 30 14:42:40 ask questions Jan 30 14:42:46 don't ask to ask Jan 30 14:42:54 as av500 would say it Jan 30 14:43:01 Oh ! Great ! Jan 30 14:43:14 I have an idea for gsoc Jan 30 14:43:40 great, let us know :) Jan 30 14:43:42 But it involves use of some other MCUs too Jan 30 14:43:52 what's the idea? Jan 30 14:44:19 Its basically a lab - master kind !! Jan 30 14:44:28 Or lab -manager !! Jan 30 14:45:05 1. It would be able to program any mcu , avr,8051 or whatever Jan 30 14:45:40 2. An oscilloscopes (some what) Jan 30 14:46:04 3. Music player ! (Yes !!) Jan 30 14:46:04 you mean logic analyzer? Jan 30 14:46:32 4. Speech synthesizer Jan 30 14:46:43 Yes logic analyzer ! Jan 30 14:46:53 And some more things !! Jan 30 14:46:57 All in one !! Jan 30 14:47:13 Wirelessly connected Jan 30 14:47:44 good, you should look at beagleLogic then, see if you can integrate it into your 'lab', which I presume is a web dashboard Jan 30 14:47:53 But as i said ! It would involve use of other MCUs too !! Some 8 bit AVRs may be ! Jan 30 14:47:56 also have a look at : http://jadonk.github.io/Beaglebone-UI/BBUI.html Jan 30 14:48:43 Ok but can such a project be considered ?? Jan 30 14:49:12 See, what you should do is write a proposal jotting down what exactly you want to do, how you want to achieve it and how it is useful to the community. Jan 30 14:49:20 a single page is enough Jan 30 14:49:37 post it on the beagle-gsoc mailing list Jan 30 14:50:19 You will get feedback and suggestions Jan 30 14:50:24 So whats important is its use to community ? Right ? Or should it be a software project ? (Atleast much of it ) Jan 30 14:50:47 based on that decide whether it is feasible or not. Jan 30 14:51:00 software should be written Jan 30 14:51:06 that is a GSoC rule Jan 30 14:51:23 and it has to be useful to the community Jan 30 14:51:26 Ok ! Thank you ! Jan 30 14:51:30 that is a BB.org thing Jan 30 14:51:54 so go and post it to the mailing list Jan 30 14:52:03 bye Jan 30 14:54:15 Will do that !! Jan 30 15:34:20 gm _av500_ Jan 30 15:34:22 sorry I'm late Jan 30 15:34:25 anyone around? Jan 30 15:35:27 av500, ds2, karki__, vvu, vmayoral, sidbh_, jj2baile, alexanderhiam: ping Jan 30 15:35:32 ahoy jkridner, how goes it? Jan 30 15:35:44 _av500_ was wanting to have a GSoC chat today. Jan 30 15:38:40 cool, I'm around Jan 30 15:39:27 ello :) Jan 30 15:39:41 thanks alexanderhiam. you participating again this year? starting to hack on the ideas page yet? Jan 30 15:39:45 hi karki__ Jan 30 15:39:51 hi Jan 30 15:39:56 what time? Jan 30 15:39:58 * jkridner wonders if he missed ds2 and _av500_ earlier. Jan 30 15:40:11 I'd said 9am US Central to them yesterday, I think Jan 30 15:40:12 jkridner: would love to Jan 30 15:40:17 it is about 9:40 now. Jan 30 15:40:45 av500 was definitely about and hour and half ago..... Jan 30 15:44:24 k. Jan 30 15:47:31 I should be online for another hour or two..... Jan 30 15:55:13 <_av500_> jkridner: ping Jan 30 15:55:15 <_av500_> im here Jan 30 15:55:19 <_av500_> was on my way home Jan 30 15:55:24 <_av500_> tram broke down Jan 30 15:55:27 <_av500_> took a while Jan 30 15:55:37 hi _av500_ sorry I'm so late. Jan 30 15:55:53 probably was supposed to catch you before you got on that train. Jan 30 15:56:00 might still be a bit early for ds2 Jan 30 15:56:30 <_av500_> right Jan 30 15:56:53 <_av500_> I guess what we need fast is an ideas page for 2015 Jan 30 15:56:58 <_av500_> and to know who can mentor Jan 30 15:57:46 * jkridner just moderated a bunch of student queries on the list. Jan 30 15:58:16 <_av500_> yes Jan 30 15:58:23 <_av500_> students we can have easily :) Jan 30 15:59:18 :-) Jan 30 16:00:16 <_av500_> I should have some time over the weekend Jan 30 16:00:26 <_av500_> so if you copy paste the ideas, I can work on that Jan 30 16:00:33 * jkridner takes a look at the ideas page. Jan 30 16:03:18 <_av500_> ok, needs some sed 2014/2015 Jan 30 16:05:30 are the students pinging early this year or is this typical? Jan 30 16:05:37 guess we are almost in February. Jan 30 16:06:11 oh crap, only 10 days before they start taking applications! Jan 30 16:06:18 ugh, and I thought we were ahead of the curve. Jan 30 16:06:34 <_av500_> yeah Jan 30 16:06:36 <_av500_> me too :) Jan 30 16:08:17 <_av500_> jkridner: for mentors, I guess you have more insight than me Jan 30 16:08:22 <_av500_> I will ask a few ppl Jan 30 16:08:35 <_av500_> I guess we can inolve beaglepilot too? Jan 30 16:08:45 _av500_: I'm thinking I might remove the "free hardware" promise and make it more of a best-effort thing. I think we can pay for some good accessories and we'd be better to focus on that than trying to get Blacks to them on time. Jan 30 16:08:47 thoughts? Jan 30 16:09:35 every author at http://bit.ly/bbb-books should be required to be a mentor. :-) Jan 30 16:09:45 <_av500_> ack Jan 30 16:10:00 <_av500_> jkridner: well, you know the google concern about HW Jan 30 16:10:10 oh, right. Jan 30 16:10:14 guess I should keep that in. Jan 30 16:10:19 <_av500_> yes Jan 30 16:10:36 <_av500_> jkridner: if TI has trouble shipping, we'll find a way Jan 30 16:10:59 yeah, I really just need to order directly from distributors in the local region. Jan 30 16:11:00 <_av500_> as long as you can secure half a dozen boards today Jan 30 16:11:05 <_av500_> ok Jan 30 16:11:09 * jkridner goes afk for 15 seconds Jan 30 16:13:01 * jkridner is back Jan 30 16:16:27 okay Jan 30 16:16:33 so what the agenda ? Jan 30 16:16:47 jkridner ^ Jan 30 16:18:38 just trying to enumerate the tasks and prioritize them.... Jan 30 16:18:55 ideas page clean-up (doing a bit of that with searching for 2014 and doing updates there) Jan 30 16:19:25 I guess I can put in a few hours this weekend Jan 30 16:19:28 I'm currently drafting a letter to go out to prospective mentors. I've sent one the last few years to the mailing list and individuals. Jan 30 16:19:33 Abhishek can help Jan 30 16:19:43 _av500_: other thoughts on agenda items for today? Jan 30 16:20:51 <_av500_> no Jan 30 16:20:55 <_av500_> mentors is key Jan 30 16:21:23 <_av500_> jkridner: can you copy the current page to 2014 Jan 30 16:21:42 <_av500_> so that we keep the old stuf and can overhaul the current one? Jan 30 16:21:51 <_av500_> before karki__ and me start on it Jan 30 16:26:28 _av500_: thought I already did that! Jan 30 16:26:54 yeah, I did that before I encouraged anyone to hack around with the Ideas page. Jan 30 16:27:02 <_av500_> ok Jan 30 16:27:08 <_av500_> im blind Jan 30 16:27:18 :p Jan 30 16:27:45 fine, #1 : cleanup old ideas Jan 30 16:27:51 #2 add new ones :D Jan 30 16:28:14 #3 find mentors for all ideas, plus extras. Jan 30 16:28:35 (making sure the mentors will be committed) Jan 30 16:28:54 * jkridner should have mentioned GSoC in the newsletter. :( Jan 30 16:29:09 I'd like to mentor, probably PyBBIO or PRU-stuff Jan 30 16:29:50 guess the Feb newsletter should go out a bit early. Jan 30 16:30:00 karki__: you around for a bit? I'd like to brain storm ideas Jan 30 16:30:22 alexanderhiam : oh, yeah I am Jan 30 16:31:18 so I'm admittedly a bit out of the 3.8 -> 3.14 loop atm, but is there any potential for GSoC projects this year depending on capemgr then becoming obsolete? Jan 30 16:35:15 the universal cape thing? Jan 30 16:36:25 yeah Jan 30 16:39:35 karki__: it's on my mind because PyBBIO is still using overlays to enable/configure specific peripherals at run time Jan 30 16:39:56 I don't know much about the universal cape myself..... Jan 30 16:41:03 last time I checked the universal cape (or the version that rcn-ee pulled in at least) only covered pinmux Jan 30 16:41:27 jkridner should be able to tell us more! Jan 30 16:42:02 I also haven't tried out a 3.14 build in a while Jan 30 16:43:06 alexanderhiam: it enables a bunch of interfaces at the same time, then you can pinmux independently Jan 30 16:43:35 so, I don't know what you mean by it only does pinmux. Jan 30 16:43:57 most of the peripherals already have runtime configuration support. Jan 30 16:44:08 like gpio, spi-dev, etc. Jan 30 16:44:29 if you need to load specific spi drivers, then you still need an overlay. Jan 30 16:44:44 the universal overlay probably conflicts by enabling spi-dev. Jan 30 16:44:59 cool, like I said I'm a bit out of date on the subject Jan 30 16:53:11 karki__: do you think it would make sense to do a whole project on botspeak/python/node.js integration? That could include writing a bunch of botspeak drivers for devices Jan 30 16:54:32 I was thinking about that Jan 30 16:55:06 wait, you mean userspace linux? Jan 30 16:55:10 or PRU stuff? Jan 30 16:55:18 PRU Jan 30 16:55:22 ah Jan 30 16:55:33 yeah, I was thinking about that Jan 30 16:55:45 + having a firmata kind of interface Jan 30 16:55:50 import pru Jan 30 16:56:04 pru.pin(1, "high") Jan 30 16:56:19 a *very* simple interface to get started Jan 30 16:56:46 I also like the idea of having a remote procedure call + shared variables API for PRU assembly (and C as well I guess) Jan 30 16:56:52 obviously not much useful, but is a warm intro to the pru Jan 30 16:57:31 I'm thinking more a way to setup drivers that could act as extensions for userspace libraries Jan 30 16:57:41 as I said I though about all this for the PRU Jan 30 16:58:26 but then it struck me that the main thing thats bugging me is not having a robust communication channel from userspace linux to PRU Jan 30 16:58:39 right Jan 30 16:58:45 a high speed, simple, lightweight shared memory system Jan 30 16:59:01 and what is exposed to both ends is like a socket Jan 30 16:59:26 pru.write("abc") in userspace Jan 30 16:59:44 get_data(buff, len) on PRU side Jan 30 17:00:07 This would make pruspeak much robust Jan 30 17:00:23 as of now there is unwanted memory management code flying about Jan 30 17:00:33 I looked at my own code a few days back...... Jan 30 17:00:40 debugging is going to be hell Jan 30 17:00:50 so there is a need for a generic bridge Jan 30 17:01:02 which uses the upcall-downcall interface Jan 30 17:01:18 I would have done it myself if I had the time Jan 30 17:01:24 but gah Jan 30 17:01:30 I have an internship Jan 30 17:02:03 well I'd love to work on this as well Jan 30 17:02:12 cool! Jan 30 17:02:32 I'll write an email to the group giving what exactly I want to do Jan 30 17:03:06 and then we can have a round of suggestions and bashings Jan 30 17:03:08 ;) Jan 30 17:03:28 I had created a repo 6 months ago on github Jan 30 17:03:34 called pru_serial Jan 30 17:03:44 did not get any time to work on it :( Jan 30 17:03:56 I have some ideas for a more integrated approach than a socket as well, I'll get an example together on a gist or something Jan 30 17:04:56 I wanted to have this ready by this GSoC :( so that more serious work could have been done on pruspeak Jan 30 17:05:02 oh, well Jan 30 17:05:21 atleast this in itself can be a project Jan 30 17:06:46 yeah, I think if we have something well defined by the start of gsoc the interface could get done pretty quickly and some cool stuff could be made with it Jan 30 17:07:09 exactly my thoughts Jan 30 17:07:35 you could help with a Python integration, I'd love to try NodeJS Jan 30 17:08:04 have been learning a bit of node, better put it to some good news ;) Jan 30 17:12:26 I think it makes more sense for me to focus on this than another straight PyBBIO project, unless someone can come up with a very compelling proposal for PyBBIO Jan 30 17:14:19 +1 Jan 30 17:17:06 alexanderhiam : once this project starts developing, I will begin to refactor pruspeak too :) Jan 30 17:21:55 hmmm not many fresh ideas yet Jan 30 19:00:31 hmm Jan 30 19:01:41 I've made five groups of ideas to try to get us a bit focused. Let me know your thoughts on the categories: http://beagleboard.org/blog-drafts/gsoc-2015/ Jan 30 22:18:40 is getting the ADC support characterized and inshape still a worthwhile goal or is the ADC dead and buried? Jan 30 23:38:49 sorry for not being around here today :) Jan 30 23:57:57 **** ENDING LOGGING AT Sat Jan 31 02:59:58 2015