09:32 < geertu> Welcome to today's Core Group Chat Meeting!
09:32 < geertu> Agenda:
09:32 < geertu> 1. Status Updates
09:32 < geertu> 2. Discussion Topics
09:32 < geertu> A) What have we done since last time:
09:32 < geertu> Marek worked on U-Boot (driver model conversion for Lager/Koelsch/Gose,
09:32 < geertu> and experiments with OpenOCD/USB), ATF (passing DT to OpTee OS), and
09:32 < geertu> VLAB VM OE prototyping.
09:32 < geertu> Morimoto-san posted SH warning cleanup patches, and worked on the
09:32 < geertu> Renesas Wiki transfer project.
09:32 < geertu> Niklas tested the re-enablement of debugfs.
09:32 < geertu> Geert updated periject/core for v5.5-rc1, added more M3-W+ support,
09:32 < geertu> investigated merge window issues, sent various fixes for DTS and PFC
09:32 < geertu> validation, and split/renamed R-Car H3 and ULCB support.
09:33 < geertu> B) What we plan to do till next time:
09:33 < geertu> Marek plans to continue working on OpTee and JTAG.
09:33 < geertu> Morimoto-san plans to go snowboarding, and let presents and blessings
09:33 < geertu> rain down on all the people.
09:33 < geertu> Shimoda-san plans to convert rcar-dmac and ipmmu DT bindings to
09:33 < geertu> json-schema, and will continue using SMMU-v3.
09:33 < geertu> Geert plans to have holidays, post new sh-pfc runtime checks, and resume
09:33 < geertu> DMAC sysfs work.
09:34 < geertu> C) Problems we have currently:
09:34 < geertu> Marek is still suffering from the upstream ATF (non)process.
09:34 < geertu> Morimoto-san needs a well-deserved power boost.
09:34 < geertu> Shimoda-san has difficulty finding time for upstream activities.
09:34 < geertu> Geert wonders if the sh73a0 DTSes should be renamed to r8a73a0.
09:35 < geertu> ---EOT---
09:35 < geertu> Anything I missed?
09:35 < geertu> Marex: I assume VLAB VM OE prototyping is for Magnus' lab?
09:40 < Marex> geertu: yes
09:41 < Marex> geertu: so we can run OpenOCD easily for example
09:41 < Marex> geertu: which reminds me, I might want to add gitlab-runner into the VM, so we can implement CI workers easily
09:41 < geertu> Marex: OK, that's what I thought it was
09:41 < Marex> geertu: which, yes, would then allow for easy CI of the boards :-)
09:41 < Marex> so much possibility for improving the process here
09:42 < geertu> Topic 2. Discussion Topics
09:42 < geertu> A) Renesas Wiki
09:42 < geertu> But we already discussed that in I/O
09:43 < geertu> Anyone with an opinion about sh73a0=>r8a73a0?
09:43 < morimoto> Oops which repository we will use ? Gitlab ?
09:43 < geertu> The latter name is already mentioned in several files
09:43 < Marex> morimoto: I would prefer gitlab, because of the wiki and CI runner support
09:43 < geertu> morimoto: Hasn't been decided yet
09:43 < Marex> morimoto: then you can CI boards on push :)
09:44 < morimoto> OK :)
09:44 -!- pinchartl [~laurent@85-76-163-249-nat.elisa-mobile.fi] has joined #periperi
09:44 < geertu> Marex: gitlab@gitlab or gitlab@elsewhere?
09:44 < Marex> could save a lot of manual work with boards
09:44 < Marex> geertu: private instance of course
09:44 < Marex> geertu: gitlab@magnus :)
09:44 < geertu> Marex: I believe you can still host a private instance @gitlab, too?
09:44 < pinchartl> (gandi has to fail me right during the meeting :-S sorry about that)
09:45 < wsa> I gotta run for today
09:45 < Marex> geertu: I don't want to ?
09:45 < Marex> geertu: esp. with sensitive stuff like renesas topics
09:46 < wsa> please let me know if there are new conclusions about next meeting or new repos
09:46 < wsa> have a nice day!
09:46 -!- wsa [~wsa@p54B33138.dip0.t-ipconnect.de] has quit [Quit: ...]
09:49 < geertu> Marex: OK, so how to add gitlab to your VM? ;-)
09:50 < geertu> Anything else to discuss?
09:50 < Marex> geertu: no
09:51 < Marex> geertu: you only need the runner in the VM
09:51 < Marex> geertu: the gitlab instance can run somewhere else, maybe in another VM :)
09:52 < geertu> Marex: <ironic>And the latter has no need to be set up?</ironic>
09:53 < Marex> geertu: that's a separate topic
09:54 < Marex> geertu: so, do you have another suggestion for a git server (with wiki and CI) ? I use gitlab to satisfaction this way for years :)
09:54 < geertu> Marex: No more suggestions from my side
09:55 < Marex> :(
09:55 < Marex> geertu: but do you at least agree that the CI would be quite helpful ?
09:55 < geertu> I there are no more topics to discussion, I'll pass the mic to pinchartl
09:55 < geertu> Marex: Yes, a CI is nice
09:55 < Marex> good
09:55 < geertu> But do we need a CI for the wiki?
09:56 < Marex> geertu: errrr, what ?
09:56 < Marex> geertu: wiki could be a replacement for the redmine we use now
09:56 < Marex> geertu: CI would CI the U-Boot/Linux patches on the boards to keep the quality high, without manual frobbing
09:56 -!- pinchartl [~laurent@85-76-163-249-nat.elisa-mobile.fi] has quit [Quit: leaving]
09:56 < geertu> Currently the git repo just has periject
09:57 < geertu> Do we need a CI for periject?
09:57 -!- pinchartl [~laurent@perceval.ideasonboard.com] has joined #periperi
09:58 < Marex> geertu: you can add u-boot/linux/atf/opteeos repos there and trigger CI on push
09:59 < geertu> Marex: All of that is public work, so no need to host it locally at Magnus
09:59 < geertu> Anyway, time's up
09:59 < Marex> geertu: does korg support CI workers now ?
09:59 < geertu> Thanks for joining, and have a nice continued day
09:59 < geertu> Marex: it relies on e.g. kernelci
10:00 < geertu> pinchartl: ready?
10:00 < Marex> geertu: which is only for kernel
10:00 < pinchartl> geertu: yes, thank you
10:00 < Marex> geertu: and can you register custom workers ?