**** BEGIN LOGGING AT Wed Aug 21 02:59:58 2019 Aug 21 09:18:32 embden_new[m]: It depends if you are using IOMMUs or not. Is there any reason for this question? Aug 21 09:18:58 platform.init is called much earlier than domain are created. What are you trying to achieve? Aug 21 11:07:54 julieng: hm, I wanted to init crossbar in platform.init function, so, I put your code there, and in this peace of code the domain is required: Aug 21 11:07:55 /* Map all irqs virq=irq */ Aug 21 11:07:55 for( i = NR_LOCAL_IRQS; i < vgic_num_irqs(d); i++ ) Aug 21 11:11:15 embden_new[m]: How about omap5_specific_mapping? Hopefully we can get rid of the workaround in a later revision of the patch. Aug 21 11:15:00 julieng: for now, I call omap5_init function from omap5_specific_mapping. Just like an ordinary function, I don't use it as .init=omap5_init yet. Aug 21 11:59:32 embden_new[m]: I think this is a misnomer, omap5_init feels to me this is related to platform initialization. So it should be done as soon as Xen boot not when the hardware domain (dom0) is built. Aug 21 12:12:29 julieng: I agree, that's why I called tegra's implementation not the best (though I can't propose a better one) they do basically the same thing with lic initialization. Aug 21 14:11:54 vaishnav98_: did I miss your weekly report? Aug 21 14:16:46 jkridner: sorry I was late in sending it, I had sent it today. I had to finish some urgent work for school which I had to complete last week. Aug 21 14:55:12 I see it now. thanks. Aug 21 14:58:56 vaishnav98_: so, it is a pattern that i2c clicks don't require custom manifests, but spi clicks do? Aug 21 15:01:01 vaishnav98_: which is the top-level project with the overall install instructions? Aug 21 15:03:03 jkridner: greybus has spi_device_setup method Aug 21 15:03:04 and has no equivalent for i2c , so SPI devices without platform data can be directly instantiated via the manifest itself, but devices on the Greybus i2c bus has to be instantiated manually Aug 21 15:04:41 jkridner: currently I am having the documentation for trying out different clicks under the blog : https://vaishnav98.github.io/GSoC19/ , currently I am working on moving it to the wiki under gbsim Aug 21 15:06:06 k. gbsim wiki seems like a good spot. Aug 21 15:09:00 jkridner : I think I will be able to finish preparing a draft wiki today itself , will update you after getting a draft version ready Aug 21 15:10:06 thanks. Aug 21 16:14:55 Abhishek_: I got a usb-uart converter and am able to use it. Am I right that it is to send out debug info from the PRU firmware? Or is it to be used in some other way? Aug 21 16:16:53 pratimugale : You connect the USB-UART converter to the dedicated boot port of the beagleboard and get a serial console first Aug 21 16:17:25 Abhishek_: yes, i got a serial console Aug 21 16:18:24 Okay, then I think you can try on using kdb. I wish I had time to guide you through the process step by step but I run really busy these days. Aug 21 16:28:59 Abhishek_: ok, I will start with kdb now and keep you updated with the problems that I face. Thanks a lot for the help despite your schedule Aug 21 16:31:17 Hi all Aug 21 16:31:33 hi all Aug 21 16:31:58 I see vaishnav98_ and pratimugale .... embden, are you here as well? Aug 21 16:32:07 hi Aug 21 16:32:13 super. Aug 21 16:32:40 cwicks is out today, so the batton is in my hand. Aug 21 16:33:01 final evaluations begin aug 26! Aug 21 16:33:03 Hi all Aug 21 16:33:22 student code submissions and evaluations started Monday! Aug 21 16:33:55 all code submissions and student-completed evaluations should be completed before the 26th. Aug 21 16:34:43 drhunter, Abhishek_ : you both here? Aug 21 16:35:16 Yes I'm here Aug 21 16:36:09 Abhishek_: are you and pratimugale well aligned on wrap-up tasks and anything necessary for you to complete your evaluation next week? Aug 21 16:36:29 drhunter: same question to you with regards to embden_new . Aug 21 16:36:46 embden_new: has drhunter been available by IRC? e-mail? Aug 21 16:37:24 jkridner: yes Aug 21 16:37:41 vaishnav98_: can you mark off completed milestones on https://elinux.org/BeagleBoard/GSoC/2019_Projects ? Aug 21 16:37:53 swap rtc5 for rtc6, etc. Aug 21 16:38:03 I think the waveform generator was the only miss. Aug 21 16:39:07 maybe rcn-ee can take a look at the image integration hurdles as I think it should be straight-forward from here. Aug 21 16:39:39 drhunter: did you miss this was the meeting time? Aug 21 16:39:58 Abhishek_: I have discussed with zeekhuge that inline documentation comments have to be added, and the kernel oops needs to be solved. Aug 21 16:40:15 jkridner: Sure I'm doing it now, also microSD support is not properly working , still it is giving the unrecognised CSD structure error :( Aug 21 16:40:17 * jkridner[m] wonders if a meeting next week is needed, since students will have already completed code submissions and evaluations. Aug 21 16:40:43 Just to make sure everyone completes the evals, yes Aug 21 16:40:47 vaishnav98_: oh, I'd missed that was still an issue on microSD. Aug 21 16:41:13 Abhishek_: but the student eval deadline is before the meeting time. Aug 21 16:41:23 Abhishek_: mentors only? Aug 21 16:43:15 Yes Aug 21 16:43:37 pratimugale : Make sure you make the code submission according to Google guidelines Aug 21 16:46:36 vaishnav98_: any questions about google's code submission guidelines? Aug 21 16:47:08 embden_new: have you spoken enough with drhunter to know what you are submitting and how he'll be evaluating you? Aug 21 16:47:18 Hello everyone! Aug 21 16:47:25 howdy zeekhuge ! Aug 21 16:48:33 julieng: sstabellini drhunter we have spoken, and I believe we decided that I should tidy up the code and prepare documentation. The draft version is here: https://medium.com/@denisobrezkov/xen-on-beagleboard-x15-a517ea7d9bb Aug 21 16:49:31 jkridner: I have updated the milestones, also regarding the Temp/Humidity click currently I do not have the hardware but I think I can add support for it by creating a click device json entry (as it have same interface as the mpu9dof click: i2c + gpio irq) , shall I add it? Aug 21 16:50:05 Abhishek_: yes, can the submission link be this https://github.com/pratimugale/PRUSS-Bindings/wiki. I can add the work done by me and other required details in this link itself. Or does it need to be any other link? Aug 21 16:51:29 vaishnav98_: yes, please. don't think it should take long, no? Aug 21 16:52:06 embden_new: I'm a bit confused in your doc if Xen works in the end. Aug 21 16:54:17 jkridner docs are not complete yet, at the end it will be shown that xen works Aug 21 16:54:27 jkridner : I think currently I don't have any doubts regarding the Google's code submission guidelines, but regarding os image integration currently the dependencies are compiled on source , so how should the packaging be done in a proper manner Aug 21 16:55:32 jkridner: Sure I'll do it, yes it can be done easily Aug 21 16:58:25 vaishnav98_: in packaging, there should be a 'make' process and a 'sudo make install' process, putting things into global positions for all users. There are conventions that make this much easier. I'd say, if you have a clearly documented 'make' process as well as steps to verify it all works, rcn-ee should be able to see if it is easy to install into a permanent position. Part of that could depend on how big it is Aug 21 16:58:25 and the things it depends on. Aug 21 16:59:06 pratimugale: are you also thinking about how to get rcn-ee to integrate your code? I've seen a bit of packaging stuff in your work, even going so far as building a debian package? Aug 21 17:03:53 jkridner: yes, I have made a debian package and have some questions as to how rcn-ee would want it and would there be any changes required Aug 21 17:04:50 maybe cc him on an e-mail to beagleboard-gsoc ? Aug 21 17:05:13 or "to him" rather. Aug 21 17:05:29 and cc the list. Aug 21 17:06:13 jkridner: ok, will do so Aug 21 17:09:03 jkridner: Thanks, currently gbsim and all its dependencies have gnu autotools set-up and I was able to create a .deb package using check-install , and was able verify install/uninstall with dpkg , what other things should be done before asking rcn-ee on os image integration Aug 21 17:09:55 that sounds like enough. kernel pull requests as needed against https://github.com/beagleboard/linux. Aug 21 17:10:22 k, one last confirmation and we'll wrap the official meeting. Aug 21 17:11:16 vaishnav98_, pratimugale, embden_new can you each say "yes" if you know how to do your code submission, complete your evaluation and know how your primary mentor will determine pass/fail? Aug 21 17:11:19 jkridner: Thanks, will do that Aug 21 17:12:06 jkridner: yes Aug 21 17:15:45 I am not sure about criterion on determination of fail/pass Aug 21 17:15:51 jkridner: Aug 21 17:16:09 embden_new: k, let's take it to drhunter via e-mail. Aug 21 17:16:19 ok Aug 21 17:16:34 zeekhuge Abhishek_ : I'm not entirely sure about how to show my work because it is a fork of the previous students. My commits during the start of the project are a bit messy Aug 21 17:18:59 embden_new: e-mail sent. Aug 21 17:19:04 you are in copy. Aug 21 17:21:56 jkridner: I haven't discussed with Abhishek_ about pass/fail criteria Aug 21 17:22:20 jkridner: I just checked my mail and fount out that Iain is at a funeral, so, he wasn't able to attend the meeting. Aug 21 17:22:58 k, glad he'd sent something. sorry for his loss. Aug 21 17:24:10 I have discussed with zeekhuge about the things left to complete Aug 21 17:24:40 zeekhuge: Can you explain the pass/fail criteria Aug 21 17:27:25 pratimugale: what do you mean by "showing my work"? Are you talking about the url? Aug 21 17:31:20 zeekhuge: Because the code is a fork of Muneeb(previous student's) repository. The guidelines require showing the work that the student has done during gsoc Aug 21 17:35:09 Ah, if this is about the url to show the work, then the wiki is fine. If you are talking about - the amount of work you have done - then your commits , reports, submitted proposal and then the level of your community engagement will be the factors/parameters that will be used to decide the eval result. Aug 21 17:36:31 From the proposal, we might look into Milestones that were proposed and achieved and the final deliverables compared proposed vs what has been done. Aug 21 17:37:02 *deliverables proposed Aug 21 17:37:36 zeekhuge: ok, thanks Aug 21 17:53:13 ds2: you at ELC? Aug 21 17:59:07 ds2: Hi, I have sent you a mail describing an issue I am facing. It would be great if you could help me out with it. Aug 21 18:26:23 jkridner[m]: no Aug 21 20:32:43 juliengsstabellini I tried to rework my code, and now I can't receive interrupts but can boot till the console prompt (also no interrupts). Could you look on it, what might be wrong: https://github.com/embeddedden/xen/commit/b98ce88d77765bd08d03559ec4405c146e038cd0 Aug 21 20:33:12 I believe that I forgot to map something in xen, because in crossbar everything should be fine Aug 21 20:33:50 (I started to map to 69 line because it's a default uart3 line) Aug 21 20:34:11 The implementaion that worked is here: https://github.com/embeddedden/xen/commit/bd3ea6e0f0041ff4d7f7601f2877132e9bccb9d5 **** ENDING LOGGING AT Thu Aug 22 02:59:56 2019