From 19f30ed33b5e65fd66319eda736f62bc66376090 Mon Sep 17 00:00:00 2001 From: Toshaan Bharvani Date: Mon, 26 Jul 2021 11:55:26 +0200 Subject: [PATCH] add meeting from april to july Signed-off-by: Toshaan Bharvani --- 2021/20210414.md | 137 ++++++++++++++++++++++++++ 2021/20210527.md | 246 +++++++++++++++++++++++++++++++++++++++++++++++ 2021/20210609.md | 222 ++++++++++++++++++++++++++++++++++++++++++ 2021/20210624.md | 186 +++++++++++++++++++++++++++++++++++ 2021/20210722.md | 105 ++++++++++++++++++++ 5 files changed, 896 insertions(+) create mode 100644 2021/20210414.md create mode 100644 2021/20210527.md create mode 100644 2021/20210609.md create mode 100644 2021/20210624.md create mode 100644 2021/20210722.md diff --git a/2021/20210414.md b/2021/20210414.md new file mode 100644 index 0000000..84d0779 --- /dev/null +++ b/2021/20210414.md @@ -0,0 +1,137 @@ +--- +title: Meeting Minutes 2021-04-14 +date: 2021-04-14 +attendees: + - timansell,google + - paullecocq,ibm + - toshaanbharvani,vantosh + - billflynn,ibm + - paulmackerras,ibm + - toddrosedahl,ibm + - stevenroberts,ibm + - jameskulina,openpowerfoundation + - zevweiss,equinix + - mendyfurmanek,ibm + - michaelneuling,ibm + - arjunnaj,tataconsultancy + - mytroung,equinix +draft: false +--- + +# Call to order / Attendance + +### Anti-trust Reminder + +This is a reminder that all OpenPOWER Foundation activities are subject to strict compliance with the OpenPOWER Foundation’s Antitrust Guidelines. Each individual participant and attendee at this meeting is responsible for knowing the contents of the Antitrust Guidelines, and for complying with the Antitrust Guidelines. Copies of the Antitrust Guidelines are available at: https://members.openpowerfoundation.org/wg/OPF/document/498 + +# Workgroup Housekeeping +Update on workgroup charter process +Call for participation went out until +Chair and maintainer process +Taking nominations / volunteers for positions +Chair +Paul Lecocq, IBM +Tim Pearson, Raptor +POWER Core technical lead +? +Uncore Technical Lead +Tim Pearson, Raptor +Software Technical Lead +? +Github Maintainers +? +Reminder of tentative Workgroup organization +3 subproject proposal +POWER Core selection, design, and optimization +FPGA "uncore" required interface definition, I/O definition, on chip bus, build process +OpenBMC updates and performance tuning, what is the minimum feature set / libraries needed +Reminder of workgroup collaboration tools +Slack / IRC +https://openpowerfoundation.slack.com/archives/C01UVKFKUQY +#librebmc on freenode (namespace) +https://chat.openpower.foundation/opf/channels/librebmc +Google Drive +https://drive.google.com/drive/u/1/folders/1p7YL3urCf4NtYbJTRxXDluytmMotUwty +OPF Discuss +https://discuss.openpower.foundation/c/sig/librebmc/11 +GIT repository +https://git.openpower.foundation/librebmc/librebmc +Larger shared storage area to save meeting recordings +Files.openpower.foundation +Need mailing list tool that people can add themselve to. +discuss.openpower.foundation +LibreBMC press announcement +OpenPOWER Blog +https://openpowerfoundation.org/openpower-foundation-announces-librebmc-a-power-based-fully-open-source-bmc/ +TheRegister +https://www.theregister.com/2021/05/10/openpower_open_source_bmc/ +Phoronix +https://www.phoronix.com/scan.php?page=news_item&px=OpenPOWER-LibreBMC +Twitter +@OpenPOWERorg +@LibreBMC +Last Meeting Follow-up +OCP Global Summit, Nov 8-10, Call for Papers June 1. +New Business +A2P - Bill Flynn, IBM +Pretaped Video presentation and slides +https://drive.google.com/drive/u/1/folders/18VRoR-tLlmUDs3a2zIIfiMJ8-jSxOzNP +Open Items document +Need to convert to github issues +https://git.openpower.foundation/librebmc/librebmc +Use this for issues for the overall project +Need to start getting content into git +License file +Apache V2 with hardware +Readme +Go from the charter and add more description on working way +….. +How to select base core(s) to start from +Microwatt (from BoxArty) +Kestrel +A2P +Discussion on what components are needed on FPGA +What exists +Updates required? +What needs to be designed + +Notes +LibreBMC Charter Status: +Call for participation went out May 10 +14 day window closes May 26 +Expect first official meeting to be May 27, need to send that out to membership +Workgroup organization + +A2P, Bill Flynn +A2P started from VexRISC-V and converted it to POWER ISA +32b core +See presentation in Google Drive A2P folder for details +A2P is currently ~5400 LUTs, VexRISCV is around 2000 LUTs +Possible differences 1000 LUTS for GPR implementation in FF vs BRAM +Hazard logic is more complex in POWER +May have more hardcoded instructions vs microcoded in VexRISCV + +Open Items + +Git repository items + +Core selection + +FPGA Components / Status +Action Items +Start document of links to tools and hardware for others to replicate work. +Diagram of all open tools, how they fit together, what is missing, what needs significant improvement - FuseSoc, OpenLane, Symbiflow, Yosys, openroads, etc https://github.com/hdl +EDA Tooling - Containers - https://github.com/hdl/containers +Make sure these support Power. I believe that Rob Taylor added Power support. +EDA Tooling - Conda - https://hdl.github.io/containers/ + +EDA Tooling - if you are a Bazel fan; +https://github.com/hdl/bazel_rules_hdl +Used by Google’s XLS team -> http://github.com/google/xls + + Add current projects that you are working on that relate to LibreBMC or opentools. Plan would be to schedule presentations on them to stir conversation and collahttps://notes.openpower.foundation/T0w6qPMJQkaj_u-UTvkUAQ?both#boration. This will highlight areas where technical issues can be worked across projects. +Next Meeting Agenda Items + +## Future topics +Arjun to present +Tim Pearson to give update on where Raptor is going with Kestrel \ No newline at end of file diff --git a/2021/20210527.md b/2021/20210527.md new file mode 100644 index 0000000..81aaa25 --- /dev/null +++ b/2021/20210527.md @@ -0,0 +1,246 @@ +--- +title: Meeting Minutes 2021-05-27 +date: 2021-05-27 +attendees: + - timansell,google + - paullecocq,ibm + - timpearson,raptor + - toshaanbharvani,vantosh + - michaelgielda,antmicro + - alexeystepanov,yadro + - lancealbertson,oregonstateuniversity + - billflynn,ibm + - paulmackerras,ibm + - toddrosedahl,ibm + - stevenroberts,ibm + - jameskulina,openpowerfoundation + - zevweiss,equinix + - mendyfurmanek,ibm + - michaelneuling,ibm + - arjunnaj,tataconsultancy + - mytroung,equinix + - michalzygowski,3mdeb + - karolgugala,antmicro +draft: false +--- + +# Call to order / Attendance + +### Anti-trust Reminder +This is a reminder that all OpenPOWER Foundation activities are subject to strict compliance with the OpenPOWER Foundation’s Antitrust Guidelines. Each individual participant and attendee at this meeting is responsible for knowing the contents of the Antitrust Guidelines, and for complying with the Antitrust Guidelines. Copies of the Antitrust Guidelines are available at: Antitrust Guidelines in Google Drive or Antitrust Guidelines OPF in OpenPOWER Foundation member area + +## Workgroup Housekeeping +Review of voting members +Chair Nominations +Chair vote +Reminder of workgroup collaboration tools +Last Meeting Follow-up +New Business +Git Repository Structure Discussion +Nominations for Maintainers +Vote for maintainers +Core strategy +Discussion on what components are needed on FPGA +Discussion on open tools to use +Open Items document +First milestones and actions + + +Minutes +Call to order / Attendance +Anti-trust Reminder +Workgroup Housekeeping +Review of voting members +Chair Nominations +Paul Lecocq, IBM +Tim Pearson, Raptor +Call for additional nominations - none +Chair vote +Tim Ansell, Google - Paul Lecocq (IBM) +Paul Lecocq, IBM - Paul Lecocq (IBM) +Tim Pearson, Raptor - Timothy Pearson (Raptor) +Toshaan Bharvani, VanTosh - Paul Lecocq (IBM) +Michael Gielda, Antmicro - Paul Lecocq (IBM) +Alexey Stepanov, Yadro - Timothy Pearson (Raptor) +Lance Albertson, Oregon State - Paul Lecocq (IBM) +Reminder of workgroup collaboration tools +Slack / IRC +https://openpowerfoundation.slack.com/archives/C01UVKFKUQY +#librebmc on libera / freenode (namespace) +https://chat.openpower.foundation/opf/channels/librebmc +Google Drive +https://drive.google.com/drive/u/1/folders/1p7YL3urCf4NtYbJTRxXDluytmMotUwty +OPF Discuss +https://discuss.openpower.foundation/c/sig/librebmc/11 +GIT repository +https://git.openpower.foundation/librebmc/librebmc +Will be mirrored to gh and gl +Larger shared storage area to save meeting recordings +Files.openpower.foundation +Last Meeting Follow-up +New Business +Git Repository Structure Discussion +https://git.openpower.foundation/librebmc/librebmc +https://git.openpower.foundation/librebmc/librebmc-gateware +Can we just call this gateware ? +Scratch places for OpenBMC / LSB +Nominations for Maintainers +Vote for maintainers (unanimity) +Tim Ansel (Google) +Tim Pearson (Raptor) +Karol Gugala (Antmicro) +Toshaan Bharvani (VanTosh) +Core strategy +Multiple cores using LiteX wrappers +Need to define core interface so cores can selected at build time +Discussion on what components are needed on FPGA +What exists +What needs to be designed +See document LibreBMC open items for now +Discussion on open tools to use + + +Open Items document +Need to convert to github issues +https://git.openpower.foundation/librebmc/librebmc +Use this for issues for the overall project +First milestones and actions +Need to start getting content into git +License file +Apache V2 with hardware +Readme +Open Discussion +As we are targeting Artix7, are we planning to focus on open tools, Symbiflow +Answer is yes, use open source tools first +Only allow upstream of designs that do not break open source tooling until the open sourcing tools +Need CICD pipeline that is common and accessible +Need to figure out where to host this, what resources +Raptor could volunteer some +OpenPOWER will host front end +OSU open source lab +Action Items +Need lower resource core to replace microwatt in the future +Need to be FPGA optimized +Work streams +Core optimization for FPGA + + +Start document of links to tools and hardware for others to replicate work. + + +http://j.mp/openfpga-diagram + + +https://symbiflow.readthedocs.io/en/latest/toolchain-desc/design-flow.html + +https://symbiflow-examples.readthedocs.io/en/latest/building-examples.html#linux-litex-demo + +https://hdl.github.io/containers/#_graphs + + +Diagram of all open tools, how they fit together, what is missing, what needs significant improvement - FuseSoc, OpenLane, Symbiflow, Yosys, openroads, etc https://github.com/hdl +EDA Tooling - Containers - https://github.com/hdl/containers +Make sure these support Power. I believe that Rob Taylor added Power support. +EDA Tooling - Conda - https://hdl.github.io/containers/ + +EDA Tooling - if you are a Bazel fan; +https://github.com/hdl/bazel_rules_hdl +Used by Google’s XLS team -> http://github.com/google/xls + + Add current projects that you are working on that relate to LibreBMC or opentools. Plan would be to schedule presentations on them to stir conversation and collaboration. This will highlight areas where technical issues can be worked across projects. + + +Next Meeting Agenda Items + +Future topics +Arjun to present +Tim Pearson to give update on where Raptor is going with Kestrel + + +WEBEX CHAT HISTORY: +from Toshaan Bharvani (External) to Everyone: 10:03 AM +Anybody coming in late, please note that this meeting is being recordered +from Lance Albertson (External) to Everyone: 10:07 AM +Are you able to hear me? +from Timothy Pearson (External) to Everyone: 10:07 AM +No +from Lance Albertson (External) to Everyone: 10:07 AM +Let me reconnect my audio +from Tim 'mithro' Ansell (External) to Everyone: 10:09 AM +Paul: Can you put a link to do doc here? +from Paul Lecocq (IBM) to Everyone: 10:09 AM +https://docs.google.com/document/d/15wC51JWJl5HOjijP8mmfvUtvws5RQaVZDgI8TvTqr9c/edit# +from Paul Lecocq (IBM) to Everyone: 10:16 AM +Slack / IRC +https://openpowerfoundation.slack.com/archives/C01UVKFKUQY +#librebmc on libera / freenode (namespace) +https://chat.openpower.foundation/opf/channels/librebmc +Google Drive +https://drive.google.com/drive/u/1/folders/1p7YL3urCf4NtYbJTRxXDluytmMotUwty +OPF Discuss +https://discuss.openpower.foundation/c/sig/librebmc/11 +GIT repository +https://git.openpower.foundation/librebmc/librebmc +Larger shared storage area to save meeting recordings +Files.openpower.foundation +from Alexey Stepanov YADRO (External) to Everyone: 10:19 AM +kind of welcome thread, good idea! +from Alexander Amelkin [YADRO] (External) to Everyone: 10:19 AM +OpenBMC has moved from FreeNode to Discord. Did you consider moving there as well? +from Toshaan Bharvani (External) to Everyone: 10:22 AM +No, I did not, I will need to look into Discord, I did consider OFTC and we do have a channel there, but not official +from Timothy Pearson (External) to Everyone: 10:23 AM +Discord requires people either run a binary on their machine (no open source client) or keep a Web browser open. On this side, it has the same issues as Slack without significant advantages +from Timothy Pearson (External) to Everyone: 10:24 AM +In our experience, there's a lot of the dev community prefers IRC or mailing list, and if not then Github or similar where the Web tooling is designed for asynchronous work +from Alexander Amelkin [YADRO] (External) to Everyone: 10:27 AM +I understand this point. However, I personally think IRC is completely obsolete in 2021, and the only way to more or less efficiently use it is connecting to it via Matrix / Riot, which also imlies running a binary. :) +from Timothy Pearson (External) to Everyone: 10:28 AM +If it's a matter of functionality, there's also open source options for the more centralized model. :) +from Timothy Pearson (External) to Everyone: 10:29 AM +e.g. Mattermost +from Toshaan Bharvani (External) to Everyone: 10:29 AM +We want to maintain an IRC solution and we have mattermost also on chat.openpower.foundation +from Timothy Pearson (External) to Everyone: 10:30 AM +yes, agreed +from Timothy Pearson (External) to Everyone: 10:30 AM +just saying I don't want things to move in a direction that requires proprietary clients for effective collaboration. +from Timothy Pearson (External) to Everyone: 10:31 AM +appreciate all the integration work toshaan! +from Toshaan Bharvani (External) to Everyone: 10:32 AM +I do not know Discord, I will look at it just for informational purposes +from Alexander Amelkin [YADRO] (External) to Everyone: 10:32 AM +Why do we need that scratch space for OpenBMC ? OpenBMC uses Gerrit Review, which can (and does) effectively serve as a scratch space. +from Toshaan Bharvani (External) to Everyone: 10:33 AM +for staging new functions and checking compatibility +from Alexander Amelkin [YADRO] (External) to Everyone: 10:34 AM +I'm just worried that we could end up like Intel with their Intel-BMC that diverges quite significantly from OpenBMC and is rarely merged back. +from Timothy Pearson (External) to Everyone: 10:35 AM +That's always a concern if a primary goal isn't to upstream the work on a regular basis. It's something we've had to struggle with as well; the only solution to it is resources that are available and ready / willing to quickly rewrite any of the new code to upstream's expectations or desires. +from Timothy Pearson (External) to Everyone: 10:36 AM +Basically, we can either move fast and break things (add functionality rapidly) or move at the speed of upstream merges. +from Timothy Pearson (External) to Everyone: 10:36 AM +So which one is the primary goal? :) +from Toshaan Bharvani (External) to Everyone: 10:37 AM +No, we will monitor that +from Alexander Amelkin [YADRO] (External) to Everyone: 10:38 AM +I guess, unless we set up a policy for upstreaming our changes from "the scratch" on a regular basis, we will inevitably diverge. +from Timothy Pearson (External) to Everyone: 10:39 AM +In our experience yes, and that would have to basically include a stop work until the merges are complete. Maybe something like the Linux merge windows -- devs can keep additional changes local / out of staging, but no further changes / enhancements accepted that aren't directly related to upstreaming accepted until upstream merges? +from Toshaan Bharvani (External) to Everyone: 10:40 AM +Ok, we will document some policy around that +from Alexander Amelkin [YADRO] (External) to Everyone: 10:41 AM +Sounds good +from Alexander Amelkin [YADRO] (External) to Everyone: 10:50 AM +You're discussing some diagram, but I can't see any media shared. Is it just me? +from Toshaan Bharvani (External) to Everyone: 10:51 AM +That is in the google docs for the moment +from Alexander Amelkin [YADRO] (External) to Everyone: 10:52 AM +Oh, ok +from Karol Gugala (External) to Everyone: 11:00 AM +I have to switch to another meeting +from Karol Gugala (External) to Everyone: 11:00 AM +bye +from Michael (External) to Everyone: 11:01 AM +Need to run too... + diff --git a/2021/20210609.md b/2021/20210609.md new file mode 100644 index 0000000..ab72d68 --- /dev/null +++ b/2021/20210609.md @@ -0,0 +1,222 @@ +--- +title: Meeting Minutes 2021-06-09 +date: 2021-06-09 +attendees: + - paullecocq,ibm + - toshaanbharvani,vantosh + - timansell,google + - billflynn,ibm + - toddrosedahl,ibm + - paulmackerras,ibm +draft: false +--- + +# Call to Order + +### Anti-trust Reminder +This is a reminder that all OpenPOWER Foundation activities are subject to strict compliance with the OpenPOWER Foundation’s Antitrust Guidelines. Each individual participant and attendee at this meeting is responsible for knowing the contents of the Antitrust Guidelines, and for complying with the Antitrust Guidelines. Copies of the Antitrust Guidelines are available at: Antitrust Guidelines in Google Drive or Antitrust Guidelines OPF in OpenPOWER Foundation member area + +# Workgroup Housekeeping +- Reminder of workgroup collaboration tools +- Last Meeting Follow-up +- New Business +- Git Repository Structure +- AC922 Interposer Update +https://git.openpower.foundation/librebmc/ac922interposer +- Options for access to hardware +- First milestones and actions + +# Minutes + +## Reminder of workgroup collaboration tools +- Slack / IRC / Mattermost +https://openpowerfoundation.slack.com/archives/C01UVKFKUQY +#librebmc on libera / freenode (namespace) +https://chat.openpower.foundation/opf/channels/librebmc +- OPF Files / Google Drive +https://files.openpower.foundation/s/iZRseq3XLtRcjtX +https://drive.google.com/drive/u/1/folders/1p7YL3urCf4NtYbJTRxXDluytmMotUwty +- OPF Discuss +https://discuss.openpower.foundation/c/sig/librebmc/11 +- OPF GIT repository +https://git.openpower.foundation/librebmc/librebmc +Will be mirrored to github and gitlab + +## Last Meeting Follow-up +- New Business +- Git Repository Structure +- Maintainers + - Tim Ansel (Google) + - Tim Pearson (Raptor) + - Karol Gugala (Antmicro) + - Toshaan Bharvani (VanTosh) +- Options for hardware +- AC922 Interposer Update +https://git.openpower.foundation/librebmc/ac922interposer +- First milestones and actions + - Need to start getting content into git + - License file : Apache V2 with hardware + - Readme +- BoxArty FPGA image into Github as a starting point + - Blocking issue is license compatibility + - BoxArty is built from + - Microwatt which is CCx4 (moving to Apache V2 + patent rights) + - LPC code from Kestrel which is GPL v3 + - This is not compatible with non-viral ApacheV2 + - Intel LPC (low pin count) is a bi-directional bus, transfers host firmware to HPM, legacy bmc to host interface + - Options to fix: + 1. find a different LPC source + 2. Raptor relicense LPC under non-viral license + - First work item once microwatt is linked to LibreBMC + - Optimize microwatt for size and performance needed for BMC + - Build time for quad core vexRiscV reported to be around 5 mins, current microwatt is ~10 mins. Can improve through tooling or RTL design. Single core size with peripherals is ~50% of Arty 100T + - Most users have Arty 35C + - VexRISC-V vs BoxArty Microwatt +- Work Items +“Create microwatt equivalent of https://github.com/litex-hub/linux-on-litex-vexriscv repo” +https://github.com/litex-hub/linux-on-litex-microwatt +https://github.com/litex-hub/pythondata-cpu-microwatt/blob/master/pythondata_cpu_microwatt/__init__.py + +- LPC controller (RTL) + +- PowerPC core optimization (RTL) + +- Symbiflow toolchain optimizations for build times EDA software + +## Open Discussion + +As we are targeting Artix7, are we planning to focus on open tools, Symbiflow +Answer is yes, use open source tools first +Only allow upstream of designs that do not break open source tooling until the open sourcing tools +Need CICD pipeline that is common and accessible +Need to figure out where to host this, what resources +Raptor could volunteer some +OpenPOWER will host front end +OSU open source lab +Action Items +Need lower resource core to replace microwatt in the future +Need to be FPGA optimized +Work streams +Core optimization for FPGA + +Start document of links to tools and hardware for others to replicate work. + +http://j.mp/openfpga-diagram + +https://symbiflow.readthedocs.io/en/latest/toolchain-desc/design-flow.html + +https://symbiflow-examples.readthedocs.io/en/latest/building-examples.html#linux-litex-demo + +https://hdl.github.io/containers/#_graphs + + +Diagram of all open tools, how they fit together, what is missing, what needs significant improvement - FuseSoc, OpenLane, Symbiflow, Yosys, openroads, etc https://github.com/hdl +EDA Tooling - Containers - https://github.com/hdl/containers +Make sure these support Power. I believe that Rob Taylor added Power support. +EDA Tooling - Conda - https://hdl.github.io/containers/ + +EDA Tooling - if you are a Bazel fan; +https://github.com/hdl/bazel_rules_hdl +Used by Google’s XLS team -> http://github.com/google/xls + + Add current projects that you are working on that relate to LibreBMC or opentools. Plan would be to schedule presentations on them to stir conversation and collaboration. This will highlight areas where technical issues can be worked across projects. + + +# Next Meeting Agenda Items + +## Future topics + +- Arjun to present +- Tim Pearson to give update on where Raptor is going with Kestrel + +# WEBEX CHAT HISTORY + +from Toshaan Bharvani (External) to Everyone: 10:03 AM +Anybody coming in late, please not that this meeting is being recordered +from Lance Albertson (External) to Everyone: 10:07 AM +Are you able to hear me? +from Timothy Pearson (External) to Everyone: 10:07 AM +No +from Lance Albertson (External) to Everyone: 10:07 AM +Let me reconnect my audio +from Tim 'mithro' Ansell (External) to Everyone: 10:09 AM +Paul: Can you put a link to do doc here? +from Paul Lecocq (IBM) to Everyone: 10:09 AM +https://docs.google.com/document/d/15wC51JWJl5HOjijP8mmfvUtvws5RQaVZDgI8TvTqr9c/edit# +from Paul Lecocq (IBM) to Everyone: 10:16 AM +Slack / IRC +https://openpowerfoundation.slack.com/archives/C01UVKFKUQY +#librebmc on libera / freenode (namespace) +https://chat.openpower.foundation/opf/channels/librebmc +Google Drive +https://drive.google.com/drive/u/1/folders/1p7YL3urCf4NtYbJTRxXDluytmMotUwty +OPF Discuss +https://discuss.openpower.foundation/c/sig/librebmc/11 +GIT repository +https://git.openpower.foundation/librebmc/librebmc +Larger shared storage area to save meeting recordings +Files.openpower.foundation + +## Chat History + +from Alexey Stepanov YADRO (External) to Everyone: 10:19 AM +kind of welcome thread, good idea! +from Alexander Amelkin [YADRO] (External) to Everyone: 10:19 AM +OpenBMC has moved from FreeNode to Discord. Did you consider moving there as well? +from Toshaan Bharvani (External) to Everyone: 10:22 AM +No, I did not, I will need to look into Discord, I did consider OFTC and we do have a channel there, but not official +from Timothy Pearson (External) to Everyone: 10:23 AM +Discord requires people either run a binary on their machine (no open source client) or keep a Web browser open. On this side, it has the same issues as Slack without significant advantages +from Timothy Pearson (External) to Everyone: 10:24 AM +In our experience, there's a lot of the dev community prefers IRC or mailing list, and if not then Github or similar where the Web tooling is designed for asynchronous work +from Alexander Amelkin [YADRO] (External) to Everyone: 10:27 AM +I understand this point. However, I personally think IRC is completely obsolete in 2021, and the only way to more or less efficiently use it is connecting to it via Matrix / Riot, which also imlies running a binary. :) +from Timothy Pearson (External) to Everyone: 10:28 AM +If it's a matter of functionality, there's also open source options for the more centralized model. :) +from Timothy Pearson (External) to Everyone: 10:29 AM +e.g. Mattermost +from Toshaan Bharvani (External) to Everyone: 10:29 AM +We want to maintain an IRC solution and we have mattermost also on chat.openpower.foundation +from Timothy Pearson (External) to Everyone: 10:30 AM +yes, agreed +from Timothy Pearson (External) to Everyone: 10:30 AM +just saying I don't want things to move in a direction that requires proprietary clients for effective collaboration. +from Timothy Pearson (External) to Everyone: 10:31 AM +appreciate all the integration work toshaan! +from Toshaan Bharvani (External) to Everyone: 10:32 AM +I do not know Discord, I will look at it just for informational purposes +from Alexander Amelkin [YADRO] (External) to Everyone: 10:32 AM +Why do we need that scratch space for OpenBMC ? OpenBMC uses Gerrit Review, which can (and does) effectively serve as a scratch space. +from Toshaan Bharvani (External) to Everyone: 10:33 AM +for staging new functions and checking compatibility +from Alexander Amelkin [YADRO] (External) to Everyone: 10:34 AM +I'm just worried that we could end up like Intel with their Intel-BMC that diverges quite significantly from OpenBMC and is rarely merged back. +from Timothy Pearson (External) to Everyone: 10:35 AM +That's always a concern if a primary goal isn't to upstream the work on a regular basis. It's something we've had to struggle with as well; the only solution to it is resources that are available and ready / willing to quickly rewrite any of the new code to upstream's expectations or desires. +from Timothy Pearson (External) to Everyone: 10:36 AM +Basically, we can either move fast and break things (add functionality rapidly) or move at the speed of upstream merges. +from Timothy Pearson (External) to Everyone: 10:36 AM +So which one is the primary goal? :) +from Toshaan Bharvani (External) to Everyone: 10:37 AM +No, we will monitor that +from Alexander Amelkin [YADRO] (External) to Everyone: 10:38 AM +I guess, unless we set up a policy for upstreaming our changes from "the scratch" on a regular basis, we will inevitably diverge. +from Timothy Pearson (External) to Everyone: 10:39 AM +In our experience yes, and that would have to basically include a stop work until the merges are complete. Maybe something like the Linux merge windows -- devs can keep additional changes local / out of staging, but no further changes / enhancements accepted that aren't directly related to upstreaming accepted until upstream merges? +from Toshaan Bharvani (External) to Everyone: 10:40 AM +Ok, we will document some policy around that +from Alexander Amelkin [YADRO] (External) to Everyone: 10:41 AM +Sounds good +from Alexander Amelkin [YADRO] (External) to Everyone: 10:50 AM +You're discussing some diagram, but I can't see any media shared. Is it just me? +from Toshaan Bharvani (External) to Everyone: 10:51 AM +That is in the google docs for the moment +from Alexander Amelkin [YADRO] (External) to Everyone: 10:52 AM +Oh, ok +from Karol Gugala (External) to Everyone: 11:00 AM +I have to switch to another meeting +from Karol Gugala (External) to Everyone: 11:00 AM +bye +from Michael (External) to Everyone: 11:01 AM +Need to run too... + diff --git a/2021/20210624.md b/2021/20210624.md new file mode 100644 index 0000000..dd512ae --- /dev/null +++ b/2021/20210624.md @@ -0,0 +1,186 @@ +--- +title: Meeting Minutes 2021-06-24 +date: 2021-06-24 +attendees: + - paullecocq,ibm + - toshaanbharvani,vantosh + - timansell,google + - billflynn,ibm + - steveroberts,ibm + - peterkatarzynski,antmicro + - alexeystepanov,yadro + - karolgugala,antmicro + - lancealbertson,osu + - michaelgielda,antmicro +draft: false +--- + +# LibreBMC SIG Meeting +## June 24, 2021 +# Call to Order + +# July 7 meeting is being canceled due to US Holidays. Next meeting July 22. + +### Anti-trust Reminder +This is a reminder that all OpenPOWER Foundation activities are subject to strict compliance with the OpenPOWER Foundation’s Antitrust Guidelines. Each individual participant and attendee at this meeting is responsible for knowing the contents of the Antitrust Guidelines, and for complying with the Antitrust Guidelines. Copies of the Antitrust Guidelines are available at: [Antitrust Guidelines](https://drive.google.com/drive/folders/1k9F3ww5cQL30xQvUL1dt4DE5qLVLax_J?ths=true) in Google Drive or [Antitrust Guidelines OPF](https://members.openpowerfoundation.org/wg/OPF/document/498) in OpenPOWER Foundation member area. + +# AGENDA + +## REMINDERS +- Reminder of workgroup collaboration tools + - This Agenda is at https://notes.openpower.foundation/ + +## Publicity + +- Google is looking at putting something around DC-SCM / LibreBMC into the OCP conference. + - Proposals due by end of July. + - +- People to invite; + - Rob Taylor + - Carlos Eduardo (RedHat Brazil) -- https://twitter.com/carlosedp + - Big in RISC-V + - Did https://carlosedp.medium.com/xilinx-open-source-fpga-toolchain-on-docker-containers-93202650a615 + - Look into to people in the Open Source Firmware Conference - https://osfc.io/ + - https://oxide.computer/ + - (maybe) Jon Masters (?) - https://twitter.com/jonmasters + - + +## HARDWARE +- Antmicro DC-SCM Overview and Update + - https://github.com/antmicro?q=dc-scm - Hardware Repository + - Designed on KiCAD under open source license + - Compatible with DC-SCM v1.0 standard + - Artix 7 version + - ECP5 version + - Currently targetted to run https://github.com/litex-hub/linux-on-litex-vexriscv + +- Overall components of POWER9 Platform test - Steve Roberts + - AC922 + - Interposer + https://git.openpower.foundation/librebmc/ac922interposer + - Antmicro DC-SCM compatible (not tested at present) + - 50$ price estimate + +- Next Steps + - Hardware Availability + - Who would be interested in hardware. + Please add you name and quantity + https://notes.openpower.foundation/ZbAY9R0bSpW93fUW_Qy32Q + +## GATEWARE + +- Existing Components + - BoxARTY + - Microwatt + - Litex Microwatt + - https://github.com/antonblanchard/microwatt/issues/294 + - + - A2P (in progress) + - https://files.openpower.foundation/apps/files/?dir=/LibreBMC/A2P&fileid=368 + +- Making a linux-on-litex-microwatt repository + - https://github.com/litex-hub/linux-on-litex-vexriscv + - https://github.com/litex-hub/linux-on-litex-rocket + - @mithro has created https://github.com/litex-hub/litex-on-litex-power + - Who needs / want's access? + +- Linux support for LiteX peripherals + - See ["Firmware sheet" in @mithro's LiteX Soft-CPU, FPGA and Firmware Support](https://docs.google.com/spreadsheets/d/1XTHfdYXuvwoYdPXm4M6qDA0D2fZCPy220-9q6qZpTw4/edit#gid=1131619550) + - UART + - Clocks + - GPIO / PWM / misc + - SPI + - Ethernet + - SD Card + - USB + +- Emulation of gateware in Renode + - + +- Simulation of gateware in Verilator + - + +- Next steps + - Release BoxARTY as starting point for LibreBMC + - Improve Litex Microwatt + - Create Litex on Linux for Microwatt + - Start work on "Small" version of Microwatt + - Remove FP + - Minimum Compliancy + - FPGA optimizations (using arrays instead of latches) + - Microcode infrequently used complex instructions + - Review A2P for additional FPGA optimization techniques + - Release A2P + - Create Litex A2P + - Create Litex on Linux for A2P + - 64 bit version of A2P? + +## SOFTWARE + +- Future Discussion on what will be needed from OpenBMC (Todd) +- Profiling of OpenBMC code would be useful for LibreBMC optimizations + +## TOOLS + +- Document tool flow in LibreBMC repo w/ links to tools + - Please don't do your own thing, use the stuff at https://github.com/hdl and send the stuff upstream. + - These are now being published at http://gcr.io/hdl-containers (Google Container Registry) + - We should reach Rob Taylor + +- Two "precompiled tooling / package" flows: + - [SymbiFlow Environment Providers](https://docs.google.com/drawings/d/15sVUnCHS1ex3lmuD3J7nDR-F1Xst6Panotc-2WlNRtQ/edit) + - Containers + - https://github.com/hdl/containers + - More Cloud like flow + - + - Conda + - https://github.com/hdl?q=conda + - Cross platform support -- Windows, Linux, MacOS + - Provides everything in a self contained environment which doesn't need root access. + - Integrates with the scientific Python + machine learning environments. + - Integrates with the codelab / Jupyter notebooks. + - make-env to "build an environment" using Makefile + - https://github.com/SymbiFlow/make-env + - Currently only support conda, but would like to support containers and "system". + +- CICD Flows + - OPF HUB / Raptor / VanTosh / Google / ... + +## OTHER TOPICS + +# MINUTES + +## Reminder of workgroup collaboration tools + +- Slack / IRC / Mattermost +https://openpowerfoundation.slack.com/archives/C01UVKFKUQY +#librebmc on libera / freenode (namespace) +https://chat.openpower.foundation/opf/channels/librebmc +- OPF Discuss (with calendar and link to chat) +https://discuss.openpower.foundation/c/sig/librebmc/11 +webcal://discuss.openpower.foundation/c/sig/librebmc/l/calendar.ics +- OPF Files / Google Drive +https://files.openpower.foundation/s/iZRseq3XLtRcjtX +https://drive.google.com/drive/u/1/folders/1p7YL3urCf4NtYbJTRxXDluytmMotUwty +- OPF Discuss +https://discuss.openpower.foundation/c/sig/librebmc/11 +- OPF GIT repository +https://git.openpower.foundation/librebmc/librebmc +Will be mirrored to github and gitlab +- OPF Kanban (linked with chat) +https://kanban.openpower.foundation/b/hgDqwnbiZDHFR3B3b/librebmc + +## HARDWARE MINUTES + +# Antmicro DC-SCM + +- Peter Katarzynski (Antmicro) presented Artix7 DC-SCM and status + - 2 Rev 1.05. boards in early bringup + - VexRISC and firmware running to control leds on board + - 10 Rev 1.06 ordered from ?? + - Breakout board also designed + - Provides additional test points of all I2C as well as litex console interface, pcie edge connector, etc + - Design files will be open sourced once validated + - Discussion on how to get a supply for developers who want hardware + - Proposal to get quotes and present to OPF board to see if OPF can fund a small number +- Steve Roberts (IBM) presented POWER AC922 Test platform \ No newline at end of file diff --git a/2021/20210722.md b/2021/20210722.md new file mode 100644 index 0000000..14d1fb6 --- /dev/null +++ b/2021/20210722.md @@ -0,0 +1,105 @@ +--- +title: Meeting Minutes 2021-07-22 +date: 2021-07-22 +attendees: + - toshaanbharvani,vantosh + - alexeystepanov,yadro + - timpearson,raptor + - timansell,google + - michaelgielda,antmicro + - karolgugala,antmicro + - lancealbertson,osu + - zevweiss,equinix +draft: false +--- + +# LibreBMC SIG Meeting + +Meeting date: 22 July 2021 +Access link: https://zoom.us/j/91597478078 + + +# Call to Order + +### Anti-trust Reminder + +This is a reminder that all OpenPOWER Foundation activities are subject to strict compliance with the OpenPOWER Foundation’s Antitrust Guidelines. Each individual participant and attendee at this meeting is responsible for knowing the contents of the Antitrust Guidelines, and for complying with the Antitrust Guidelines. Copies of the Antitrust Guidelines are available at: [Antitrust Guidelines](https://drive.google.com/drive/folders/1k9F3ww5cQL30xQvUL1dt4DE5qLVLax_J?ths=true) in Google Drive or [Antitrust Guidelines OPF](https://members.openpowerfoundation.org/wg/OPF/document/498) in OpenPOWER Foundation member area. + +# AGENDA + + +## WG Chair Update + +- Nominations + - on hold +- Votes + - on hold + +## TODO List + +- Create ToDo list (kanban) + - Major missing piece NCSI RMI piece (driver for LiteX) + - https://www.dmtf.org/sites/default/files/standards/documents/DSP0222_1.1.0.pdf + Built on RMII + - Tim has previously created [LibreBMC Open Items](https://docs.google.com/document/d/10RJUk_uXhku6FTnb-WtpIDHrkrEaWdAREF4wafYzfV4/edit) + - Google + Antmicro are working on getting PCI Express going on the Xilinx hardware using open source tools (symbiFlow.github.io) + - Currently target is to get https://github.com/timvideos/litex-buildenv/wiki/HowTo-HDMI2PCIe-on-NeTV2 working with fully open source tools. + - Currently deprioritized behind getting FPGA interchange work going. + - Seems like we can *probably* get by without PCIe initially. + - There is some work on Lattice PCIe stuff that was done in GSoC; + - https://github.com/whitequark/Yumewatari + - https://github.com/ECP5-PCIe/ECP5-PCIe + - https://github.com/enjoy-digital/litepcie/blob/master/doc/architecture.png + - Need to understand what components are hard macro / (currently) encrypted HDL / currently open (LiteX) for both Lattice + Xilinx + - https://github.com/greatscottgadgets/bucatini + - Graphics / VGA support + - Currently a nice to have. + - Raptor has working HDMI on ECP5 via transceiver on Sparrowhawk, code upstream in LiteX + - Need PCIe endpoint to provide VGA controller to host + - Can currently display serial console via text terminal (BMC-driven) +- Start gateware repo (git) +- Create BOM for first hardware batch (git) + + +- Using HedgeDoc? Is there a folder for Meeting Notes like in Google Drive? + - [GoogleDrive folder for Meeting Agenda + Notes](https://drive.google.com/drive/folders/1k9F3ww5cQL30xQvUL1dt4DE5qLVLax_J) + - https://files.openpower.foundation/s/iZRseq3XLtRcjtX +- Improve SoftCore for FPGA purposes + - Can softcore reduce the size? + - http://j.mp/softcpus-on-fpgas + - 3 ways of core optimization : fpga / asic / education +- Hardware status + - Getting the IBM Machine (AC922) + - On the way, coming soon with a link + - Getting the Interposer for AC922 + - Getting an interposer to Antmicro (Michael / Pieter / Karol) + - Getting the FPGA DC-SCM BMC boards + - Getting a board to IBM OzLab + - Currently lots of confusion between IBM and Antmicro. + - Need to get Antmicro hardware ASAP so they can replicate the IBM work. + - IBM being the only one doing hardware work is a huge roadblock here. + - Possible alternate (Lattice not Xilinx) Raptor has ModBMC (derived from RunBMC) product for use with Talos II/Blackbird + - October 2021 timeframe for retail launch + - Organize a discussion between Antmicro, Tim Ansell (Google), Raptor around getting Artix 7 / Xilinx board compatible with ModBMC for use with Talos hardware. + - + + +## Workgroup Collaboration Tools + +- OPF Discuss (with calendar and link to chat) +https://discuss.openpower.foundation/c/sig/librebmc/11 +webcal://discuss.openpower.foundation/c/sig/librebmc/l/calendar.ics +- Slack / IRC / Mattermost +https://openpowerfoundation.slack.com/archives/C01UVKFKUQY +#librebmc on libera / freenode (namespace) +https://chat.openpower.foundation/opf/channels/librebmc +- OPF Files (Google Drive being phased out) +https://files.openpower.foundation/s/iZRseq3XLtRcjtX +(https://drive.google.com/drive/u/1/folders/1p7YL3urCf4NtYbJTRxXDluytmMotUwty) +- OPF Discuss +https://discuss.openpower.foundation/c/sig/librebmc/11 +- OPF GIT repository +https://git.openpower.foundation/librebmc/librebmc +Will be mirrored to github and gitlab +- OPF Kanban (linked with chat) +https://kanban.openpower.foundation/b/hgDqwnbiZDHFR3B3b/librebmc \ No newline at end of file