**** BEGIN LOGGING AT Wed Feb 06 02:59:57 2019
Feb 06 06:40:42 <zeekhuge[m]> Hello everyone !
Feb 06 06:40:47 <pac23[m]> hello
Feb 06 06:40:54 <zeekhuge[m]> there is already some traffice here.
Feb 06 06:41:09 <pac23[m]> i think i might have missed some messages directed at me before due to no bnc,
Feb 06 06:41:32 <pac23[m]> shall i add the ideas i had discussed on the beagle gboard back in jan with jkridner to the wiki
Feb 06 07:02:54 <Guest79507> Pac23: go ahead
Feb 06 07:16:00 <pac23[m]> Will do +1
Feb 06 14:47:06 <ravikp7[m]> hey everyone, has anyone tried making a LORA WAN gateway using beaglebone?
Feb 06 14:49:56 <pac23[m]> but since software already exits,making one with a beaglebone should be not that big of a challange,the kind gsoc requires
Feb 06 14:50:09 <pac23[m]> i am sure whatever that runs on pi will work on beaglebone
Feb 06 14:50:11 <ravikp7[m]> as per my knowledge, solutions are already in place for most needs
Feb 06 14:50:36 <ravikp7[m]> pac23: exactly not much too suffice gsoc timeline
Feb 06 14:51:07 <pac23[m]> yeah,even i wanted to build something but then its not gsoc worthy
Feb 06 14:52:28 <ravikp7[m]> hmm, I just wanted to know if somebody has faced any issue or have any project idea worth the gsoc timeline
Feb 06 14:53:01 <pac23[m]> can two people work on a same project ?
Feb 06 14:53:18 <pac23[m]> i had something but the hardware and software part of it definetly requires two people to finish barely in gsoc
Feb 06 14:53:40 <pac23[m]> its crazy diff/clumsy to build it both in terms of hw and code
Feb 06 14:55:49 <ravikp7[m]> pac23: what kind of project?
Feb 06 14:56:22 <zeekhuge[m]> pac23: Since it's GSoCode, it should not have a lot of hardware in it.
Feb 06 14:56:53 <zeekhuge[m]> Also, 2 students on 1 project can become very difficult to handle
Feb 06 14:57:03 <Guest79507> pac23 : One student per project is the GSoC rule officially
Feb 06 14:57:33 <pac23[m]> i have seen debian and fossasia do 2 or even 3 students on one project
Feb 06 14:57:45 <zeekhuge[m]> pac23 (@pac23:matrix.org) :If you could separate it into 2 different and "mostly" independent modules, that would be great.
Feb 06 14:58:00 <Guest79507> They must have clear boundaries between projects
Feb 06 14:58:32 <Guest79507> If common aim, different parts, then it is possible to separate work but it can get clumsy
Feb 06 14:59:08 <Guest79507> Hi hendersa - your project idea is interesting.
Feb 06 14:59:51 <pac23[m]> ravikp7 so basically a beaglebone pocket based calc,that runs on battery,gives the user back the mathematical solution stepwise to complex mathematical problems,user simply puts in the problem statement on the question paper. All the hardware is hosted inside a standard TX instrumetns or casio fx 991 calc ,from the outside anyone would think its a normal calc
Feb 06 14:59:55 <pac23[m]> potentially illegal
Feb 06 15:00:16 <pac23[m]> hardware mapping the keyboard is the clumsiest part of it and modding it
Feb 06 15:00:33 <Guest79507> Pac23: That would need a display + matrix keyboard
Feb 06 15:00:59 <Guest79507> It's not trivial but possibly to build
Feb 06 15:01:04 <pac23[m]> using the standard calc display as a display i mean,
Feb 06 15:01:12 <Guest79507> *possible
Feb 06 15:01:17 <pac23[m]> used by casio in their scientific calcs
Feb 06 15:01:49 <Guest79507> pac23 : Logistically it'd be easier to use a colour TFT LCD display
Feb 06 15:01:57 <zeekhuge[m]> <Guest79507 "Hi hendersa - your project idea "> abhishek_ , hendersa :The "future scope" of Beaglescope included parallel bus like interface using PRUs, infact there are wip branches for parallel interface in there
Feb 06 15:02:30 <pac23[m]> but then it takes away the stealth factor of it abhishek_
Feb 06 15:03:06 <pac23[m]> zeekhuge yeah seperating could be possible idk
Feb 06 15:03:08 <pac23[m]> tbh
Feb 06 15:03:35 <hendersa> zeekhuge[m]: Oh really? I added that project in too late last year, but a lot of students were pinging me on it after the fact.
Feb 06 15:04:15 <hendersa> The PRU aspect was more of an afterthought. I'd like to see a student get the hardware design nailed down and use some help to get a generic parallel bus driver of some sort in place.
Feb 06 15:04:29 <hendersa> Something that anyone could use for a bus-interfacing project.
Feb 06 15:06:03 <zeekhuge[m]> hendersa : Yeah. At beaglescope, The idea was to have a generic parallel bus interface, and PRUs would just make themselves appear (using remoteproc) as parallel - device.
Feb 06 15:06:38 <pac23[m]> abhishek_:
Feb 06 15:07:01 <zeekhuge[m]> hendersa: https://github.com/ZeekHuge/BeagleScope/tree/port_to_4.4.12-ti-r31%2B/driver
Feb 06 15:08:43 <pac23[m]> abhishek_:  zeekhuge the pru user space api project looks interesting
Feb 06 15:08:51 <pac23[m]> would like to work on it
Feb 06 15:09:34 <zeekhuge[m]> Sure. You can try to get hands on with the PRUs
Feb 06 15:09:49 <hendersa> zeekhuge[m]: Is that for a set of PRU-muxed pins working in parallel?
Feb 06 15:10:05 <pac23[m]> the pypruss upstream ends with a 404 can you kindly link a new one
Feb 06 15:10:24 <hendersa> I was thinking more of using far fewer pins (regular GPIOs for flexibility) with a serial-to-parallel shift register setup.
Feb 06 15:10:30 <Guest79507> hendersa , zeekhuge : A parallel interface can potentially be also used to link BeagleBoard to a FPGA.
Feb 06 15:10:52 <hendersa> BeagleScope would need to run those pins in parallel to reduce latency, right?
Feb 06 15:12:05 <zeekhuge[m]> Yeah. PRU pins will have to be muxed. Width could be configured though
Feb 06 15:12:41 <pac23[m]> <zeekhuge[m] "Sure. You can try to get hands o"> can you link to some more reading on the pru's ahve made api's before not worked with pru's would like to learn more as there is still time for the application period to begin
Feb 06 15:13:00 <hendersa> I wanted to give people the opportunity to use a serial-to-parallel interface using any old GPIOs to aid in integrating the bus with their existing projects.
Feb 06 15:13:36 <zeekhuge[m]> pac23 (@pac23:matrix.org): I have some blogs on it for starters.
Feb 06 15:13:52 <hendersa> My purely selfish reasons for something like that would be interfacing with old memory chips, game cartridges, and the like. As well as simulating these interfaces to interact with original vintage hardware.
Feb 06 15:14:14 <zeekhuge[m]> pac23 (@pac23:matrix.org) https://zeekhuge.me
Feb 06 15:15:12 <pac23[m]> zeekhuge: Thanks :)
Feb 06 15:16:53 <hendersa> Anyway, we'll see if any students bite on the idea with some good suggestions and a strong proposal. Anything that builds interest in the Beagles and plays to their strengths, right?
Feb 06 15:18:22 <zeekhuge[m]> Sure. Hope to see good proposal.
Feb 06 15:22:27 <pac23[m]> last year there was this connected pocketbeagle idea listed,is that still valid ?
Feb 06 17:51:34 <underscore> gm all
Feb 06 17:52:05 <pac23[m]> good morning underscore
Feb 06 17:54:13 <underscore> I hope to get my keystroke injector idea noticed this week. I hope I'm not too late
Feb 06 18:07:07 <horizon00[m]> what is the last date for sharing idea proposals on BeagleBoard GSoC mailing list.
Feb 06 20:08:51 <m_w> howdy all
Feb 06 20:16:14 <m_w> released the baconbits cape on groupgets: https://groupgets.com/campaigns/510-baconbits
Feb 06 20:17:58 <m_w> I think that scale17x will be the last e-ale session that uses this board but it is good for learning
Feb 06 20:18:13 <m_w> if you know someone looking to get started with embedded linux and can't attend the conferences this might be a good option
Feb 06 20:20:06 <m_w> any hardware leaning students looking at participating this year?
Feb 06 20:29:35 <zeekhuge[m]> horizon00: You should have enough time to be able to convice the org-mentors to mentor your project, before the student proposal sumbission deadline. Thats pretty much it.
Feb 07 00:45:57 <horizon00[m]> thank you zeekhuge
**** ENDING LOGGING AT Thu Feb 07 02:59:57 2019