**** BEGIN LOGGING AT Wed Aug 07 03:02:32 2019 Aug 07 09:02:39 embden_new[m]: returning 1 in the IO handlers means you have handled the IO. How this was handled is up to the driver. Aug 07 09:02:50 It may be just storing in internal structure or replicating to the host. Aug 07 09:05:05 julieng: so, I need to write the value to a register anyway (it is not handled autmatically)? Aug 07 09:06:43 embden_new[m]: Yes you will have to do (if this is the approach you choose). Aug 07 09:14:19 julieng: that's make sense, thank you Aug 07 09:21:31 * @freenode_julieng:matrix.org: that makes sense, thank you Aug 07 11:39:53 julieng: sstabellini how long ioremap'ped region stays mapped? For example, if I map it in in a function will it be still mapped after return from the function? Aug 07 11:40:19 embden_new[m]: It will stay there as long as iounmap is not called. Aug 07 11:58:13 julieng: sstabellini so, now I can enter to the console. But the strange thing is that I have to type one letter for three times to make it appear. Aug 07 11:58:42 But Enter works from the first time Aug 07 11:59:06 hm, now other letters also work from the first time... Aug 07 11:59:55 https://pastebin.com/rAXmaptx Aug 07 12:06:53 The code is here: https://github.com/embeddedden/xen/commit/cb303a5d45e7826135c1e873c2192086318f157a Aug 07 12:07:48 now I believe I need to implement some control logic for crossbar Aug 07 15:37:57 zeekhuge: Could you please have a look at https://github.com/pratimugale/PRUSS-Bindings/blob/pruss-api-driver/drivers/pruss_api.c. It is derived from rpmsg_pru.c itself. I have tested its working and the pru firmware now looks like this: https://github.com/pratimugale/PRUSS-Bindings/blob/f2118c0f129bd50a6398e78a5b832c53f18df956/examples/firmware_examples/example9-multichannel-waveform-gen/PRU1/main.c#L66. Aug 07 15:44:51 embden_new[m]: usually it is because the interrupts are getting lost Aug 07 15:46:00 zeekhuge abhishek_[m] I have also updated the main Readme.md Aug 07 16:05:08 Good morning ChanServ 26 mins til our meeting :) Aug 07 16:08:32 pratimugale: looks nice. Did you test it completely? Aug 07 16:08:37 Using prussd? Aug 07 16:08:49 Yes Aug 07 16:09:10 Nice. Good work. Aug 07 16:09:38 Btw, that readme is taking me to something core.com Aug 07 16:11:28 zeekhuge: Ohh.. I didn't mean to write it as a link Aug 07 16:11:29 https://github.com/pratimugale/PRUSS-Bindings/tree/pruss-api-driver#pruss-bindings---an-api-to-control-the-bbb-prus Aug 07 16:28:20 cwicks: I'll be 10-15 minutes late Aug 07 16:30:36 Hi all Aug 07 16:33:05 Hello everyone Aug 07 16:33:17 thanks embden_new we'll put you third today Aug 07 16:35:19 Hi vaishnav98_ Hi pratimugale Aug 07 16:35:20 pratimugale: do you have your mentors in the room active today yet? Aug 07 16:36:05 Hi cwicks Aug 07 16:36:18 cwicks: Yes, I think abhishek_[m] is here Aug 07 16:36:33 I think also zeekhuge Aug 07 16:36:47 So pratimugale can you please go first today? Aug 07 16:37:04 cwicks: sure Aug 07 16:39:55 cwicks: I am here Aug 07 16:40:42 cwicks zeekhuge abhishek_[m] This week I studied about the rpmsg drivers and implemented a 'pruss_api' driver for rpmsg communication for the project. I have started working on the Documentation and adding continuous integration. Aug 07 16:42:56 I still have to complete documentation the working of some of the pru firmware examples Aug 07 16:45:23 I have installed and tested 'prudebug' and will next try to integrate it with this project. Aug 07 16:47:20 zeekhuge abhishek_[m] Regarding GSoC's email, how should the final submission be done? Aug 07 16:48:31 First, it should be a url to a page that will "always" Be there. Then, that page can redirect to different pages for different things. Aug 07 16:50:18 This first page should describe your project and its part. It can have all the details, or can provide with links to different pages that would further describe more details. Aug 07 16:50:20 Usually, this "first" Page is the github repo's wiki or readme. Aug 07 16:50:44 pratimugale: zeekhuge abhishek_[m] Would this be helpful to see how the 2018 projects stored/documented their projects https://elinux.org/BeagleBoard/GSoC/2018_Projects Aug 07 16:51:28 ie do we have a benchmark project that you really liked in the past how they documented the submission , etc Aug 07 16:53:53 zeekhuge: understood, I'll update the github wiki. cwicks I'll update the elinux page of the project Aug 07 16:54:01 As far as I know, different projects have done it differently. So not sure if is a benchmark project. Aug 07 17:04:43 OKay - well something we can check in with jkridner about, but former GSoc Students who are now mentors can provide good advice here Aug 07 17:21:12 cwicks: Hi, shall I provide my update? Aug 07 17:21:33 Yes please Aug 07 17:21:47 I don't know that jkridner will join today, butyour other mentors are here Aug 07 17:21:58 cwicks: when are the final videos to be made? Aug 07 17:24:37 jkridner cwicks ravikp7: Hi, last week I was trying to implement gpio irq support in gbsim, I was able to implement it using libsoc helper functions and tested it using a simple led-push button kernel driver and it was working well, I was also able to fix the issue with instantiating i2c clicks with interrupt requirement, and currently mpu9dof click is also supported via greybus simulator, I am a bit confused on Aug 07 17:24:38 providing a uniform way of instantiating the clicks, currently clicks without additional platform data can be instantiated directly from userspace, but if there is additional platform data it is done via the Mikrobus kernel driver, also I would like to hear from jkridner and ravikp7 on how to prepare the work for final evaluation Aug 07 17:33:05 thanks vaishnav98_ Aug 07 17:33:24 pratimugale: I'll check on that date for you Aug 07 17:33:36 embden: thanks for joining can you give your update? Aug 07 17:33:41 yes Aug 07 17:33:55 pratimugale: any blockers?? Aug 07 17:34:12 Hello, this week I have started to implement virtualization of the crossbar. I added io handlers and allowed Linux to write into the register of the crossbar except of the register 4 which is used internally by xen. And the good news is that I have some kind access to the Linux console. Aug 07 17:34:13 The main blocker right now is to understand what is a way better of handling Linux writes to crossbar controll registers. We have discussed this with the mentors, so, I need to understand better how virq, irq and crossbar's io handlers are involved. Another issue is that sometimes interrupts are not go through the crossbar for some reason. So, I should investigate this. Aug 07 17:34:14 The plan for the next week is to solve those blockers and to discuss with mentors how to prepare my work for the final evaluation. Aug 07 17:37:15 julieng: sstabellini drhunter ds2 a weekly update ^ Aug 07 17:37:30 vaishnav98_: any blockers? Aug 07 17:38:42 thanks embden_new have you good interactions from the mentors/community to help - are you on target to your milestones planned? Aug 07 17:39:18 vaishnav98_: pratimugale same questions - if you look at your milestones on the plan - are you at or ahead of your plan? Aug 07 17:40:00 cwicks: yes, the interaction is good, and I am doing good regarding the schedule, though the mentors can answer better this question Aug 07 17:40:14 cwicks: There are no major blockers right now, but I still haven't been able to solve the kernel oops error I had last week. Also I was down with viral fever last weekend but I have completely recovered. Aug 07 17:40:27 thanks embden_new Aug 07 17:40:42 julieng: any feedback on the milestones questions Aug 07 17:41:15 pratimugale: sorry you were sick, glad to know you are getting better - stay hydrated, my friend. Aug 07 17:41:27 cwicks: still needs to fix issues with instantiating SPI devices with interrupt requirements through greybus, also would like to hear jkridner 's views on how exactly to handle device instantiation, I think of adding calls to Mikrobus driver from greybus device setup methods would it be a good idea? Aug 07 17:42:06 vaishnav98_: do you know how to go onto jkridner calendar and schedule a 30 min session to ensure you are both available at the same time? Aug 07 17:42:51 jkridner: uses "calendly" https://calendly.com/jkridner Aug 07 17:42:57 cwicks: thanks a lot, I am doing well on the schedule, zeekhuge are there any other things that must be done? Aug 07 17:44:19 apart from the debugger addition, debian packaging and Documentation, which are remaining Aug 07 17:45:30 cwicks: I have received total 8 click boards during the start of gsoc , currently support for 5 of them is done(microSD click fails) through greybus needs to finish the rest of the clicks, seem like a little behind what was proposed Aug 07 17:47:20 Hi vaishnav98_ I see - so do you have a priority for the remaining clicks Aug 07 17:47:50 ChanServ: I need to exit the meeting for today - but as usual please continue to work w/ your mentors on the channel while you have them. Aug 07 17:48:19 cwicks: thanks, I have scheduled a meeting with jkridner Aug 07 17:56:43 cwicks: I am planning to go with the SPI based eth click first which has an interrupt requirement, fixing it could then provide a generic way to Instantiate other SPI based clicks with interrupt requirements, I am not sure if I will be able to add support for the function generator click and ultrasonic distance click within the short span as I couldn't get those clicks Aug 07 17:56:43 to work outside greybus , the waveform click when instantied fails(no device under iio) without any error messages in kernel logs and I couldn't find any Linux based support for the ultrasonic distance sensor click **** ENDING LOGGING AT Thu Aug 08 02:59:57 2019