Hi all,
Here is the proposed agenda for tomorrow, please let us know if have additional topics. I got accepts from @Stabellini, Stefano<mailto:stefano.stabellini@amd.com> and @Ashfield, Bruce<mailto:bruce.ashfield@amd.com> for the System DT topics. Note that Bill is unable to join this week's call.
* System Device Tree:
* Are there things we can do in this group to make sure it gets into Yocto, works with our reference platforms, 1st class citizen, etc.
* AMD Xilinx HW can mutate for each customer, so what gets checked into kernel isn't that interesting. In other markets, where HW doesn't mutate, what is checked into kernel is important. If Lopper took what's in kernel & transform into SDT that other operating systems could use - flipping the inputs & outputs. Might increase interest in System DT if you didn't need 2 ways to do things.
* Discuss brainstorm list of Google Summer Of Code topics. https://docs.google.com/document/d/1zHxaMVERQwfh-Sy5ulFACi6NO58ENOdsC04dag1…
If you have trouble accessing this link, then contact me directly and let me know your Google account email.
Reminder to add your ideas to the brainstorm list before the call :)
* Q2/Q3 task tracking<https://docs.google.com/spreadsheets/d/1N5eO0FDX-gqpJtBleh_iGn-k9gr3j-w8Byj…> status
* Individual updates
Reminder of action items from last call:
* Tomas & Nishanth: Discuss OpenAMP with RISC-V Foundation at Santa Clara event
* Tomas: Check if anyone at AMD is working on System DT for RISC-V
* Nishanth will work on cleaner video of the GSOC projects, let us know when the more polished one is on Beagle channel & we will link to it in our Playlist on OpenAMP channel
* [DONE] Nathalie: Put on agenda for next call to discuss starting w/ kernel DT & transforming into System DT w/ Lopper and invite @Ashfield, Bruce<mailto:bruce.ashfield@amd.com>
* [DONE] Nathalie to create a Google doc where ppl can drop in their brainstorm ideas & we can look at the list next time
* [DONE] Dan will add tasks that he's working on to the [https://docs.google.com/spreadsheets/d/1N5eO0FDX-gqpJtBleh_iGn-k9gr3j-w8Byj… task tracking sheet]
Thanks & regards,
Nathalie
Hi all,
The notes from today's call are posted at https://github.com/OpenAMP/openamp-system-reference/wiki/OpenAMP-System-Ref…
== Action items ==
* Tomas & Nishanth: Discuss OpenAMP with RISC-V Foundation at Santa Clara event
* Tomas: Check if anyone at AMD is working on System DT for RISC-V
* Nathalie: Put on agenda for next call to discuss starting w/ kernel DT & transforming into System DT w/ Lopper and invite @Ashfield, Bruce<mailto:bruce.ashfield@amd.com>
* [DONE] Nathalie to create a Google doc where ppl can drop in their brainstorm ideas & we can look at the list next time
* Nishanth will work on cleaner video of the GSOC projects, let us know when the more polished one is on Beagle channel & we will link to it in our Playlist on OpenAMP channel
* Dan will add tasks that he's working on to the [https://docs.google.com/spreadsheets/d/1N5eO0FDX-gqpJtBleh_iGn-k9gr3j-w8Byj… task tracking sheet]
Stefano has accepted the invitation to the call 2 weeks from now, so we can have the topic then:
System Device Tree: Are there things we can do in this group to make sure it gets into Yocto, works with our reference platforms, 1st class citizen, etc.
Here is the link to the GSOC project brainstorm sheet:
https://docs.google.com/document/d/1zHxaMVERQwfh-Sy5ulFACi6NO58ENOdsC04dag1…
If you have trouble accessing this link, then contact me directly and let me know your Google account email.
Thanks & regards,
Nathalie
Hi all,
Please let us know if you have any topics for the call. Here is what I gathered so far:
* System Device Tree: Are there things we can do in this group to make sure it gets into Yocto, works with our reference platforms, 1st class citizen, etc.
* @Stabellini, Stefano<mailto:stefano.stabellini@amd.com>, @Hatle, Mark<mailto:mark.hatle@amd.com>, @Ashfield, Bruce<mailto:bruce.ashfield@amd.com>: Would you be available to join the call this week at 9am Pacific/noon Eastern?
* Google Summer of Code:
* Any questions for TI on the video posted to our Discord?
* Start brainstorming Google Summer of Code ideas for next year & what we need to discuss with TSC/Board. Last year, program was announced in December & applications closed in January.
* Q2/Q3 task tracking<https://docs.google.com/spreadsheets/d/1N5eO0FDX-gqpJtBleh_iGn-k9gr3j-w8Byj…> status
* Individual updates
Below are some GSOC resources that Nishanth shared early this year:
https://www.youtube.com/playlist?list=PLxNYxgaZ8RscKC8NFOyQK2YdMCrM9Gb5Ahttps://summerofcode.withgoogle.com/programs/2023
[cid:image001.png@01D9DFEA.A0A353E0]
Thanks & regards,
Nathalie
Hello All,
RPMsg in U-Boot is under development. First proof of concept patch v1 was sent to upstream mailing list as RFC patch here: http://patchwork.ozlabs.org/project/uboot/list/?series=365
Here is the video of demo of RPMsg framework introduced in above patch series:
https://www.youtube.com/watch?v=PxGNR_FYGt8
This document explains patch series and motivation to introduce RPMsg in U-Boot and future work that needs to be done: https://drive.google.com/file/d/1Bjtzj58klMPVuWEtRK89oyem7_Hdajn8/view?usp=…
This patch series is very basic implementation of virtio based RPMsg framework referenced from the Linux kernel. For now, U-Boot is communicating with remote processor over fix hard-coded endpoint. More advance features such as name-service, multiple endpoint support etc.. will be added in coming revisions of this patch series. Meanwhile, please feel free to review existing work and provide review comments and any other suggestions.
Thanks,
Tanmay
Hi all,
Notes from today are posted at https://github.com/OpenAMP/openamp-system-reference/wiki/OpenAMP-System-Ref…
Action items:
* Tanmay will add info on limitations & create public link to his document and share it to openamp-rp mailing list
* Andrew will add a note related to today's discussion & close TI intern's PR15
* Arnaud will try prototyping system reference example on his GitHub integrating all the work done by ST intern, with goal to put it in branches in OpenAMP GitHub
Please let us know if you spot any errors or important omissions.
Thanks & regards,
Nathalie
Hi all,
Here are the topics I've collected. Please let us know if you have additional topics:
* Integrating board/environment specific code into system reference a generic way
* Q2/Q3 task tracking<o%09https:/docs.google.com/spreadsheets/d/1N5eO0FDX-gqpJtBleh_iGn-k9gr3j-w8…> status
* Individual updates
Pushing the System DT topic out to the next call, as Bruce is OOO and Tomas has a conflict.
Thanks & regards,
Nathalie
Hi all,
The notes from this week's call are posted at https://github.com/OpenAMP/openamp-system-reference/wiki/OpenAMP-System-Ref…
Action items:
* @Shah, Tanmay<mailto:tanmay.shah@amd.com> will post link to the recording of his demo to OpenAMP-rp call to Discord
* @Shah, Tanmay<mailto:tanmay.shah@amd.com> will create a short video to explain more about his patch series & work with Nathalie to get it shared
* @Nishanth Menon<mailto:nm@ti.com> will try to get some TI guys to review Tanmay's patch series http://patchwork.ozlabs.org/project/uboot/cover/20230725140650.951581-1-tan…
* Nathalie will look through Openamp-system-reference call notes & try to file GitHub issues for actions related to repos
* Nathalie to invite @Stabellini, Stefano<mailto:stefano.stabellini@amd.com> & @Hatle, Mark<mailto:mark.hatle@amd.com> & @Ashfield, Bruce<mailto:bruce.ashfield@amd.com> to next call: Are there things we can do in this group to make sure it gets into Yocto, works with our reference platforms, 1st class citizen, etc.
Have a great weekend,
Nathalie
Hi all,
Here are the topics I've collected. Please let us know if you have additional topics:
* Reference platforms:
* Nishanth confirmed Beaglebone-AI64 will be TI's reference platform for OpenAMP
* Using GH Issues to track action items related to specific repos
* Q2/Q3 task tracking<o%09https:/docs.google.com/spreadsheets/d/1N5eO0FDX-gqpJtBleh_iGn-k9gr3j-w8…> status
* 8/9 call: Nathalie & Arnaud OOO. Does someone else want to be the call host? Or will others be OOO & should cancel?
Thanks & regards,
Nathalie