Thursday, 2025-11-13

*** prabhakalad <prabhakalad!~prabhakar@122.167.136.50> has quit IRC (Ping timeout: 256 seconds)05:05
*** prabhakalad <prabhakalad!~prabhakar@122.167.136.50> has joined #cip05:05
*** prabhakalad <prabhakalad!~prabhakar@122.167.136.50> has quit IRC (Ping timeout: 244 seconds)06:38
*** prabhakalad <prabhakalad!~prabhakar@122.167.136.50> has joined #cip06:40
*** monstr <monstr!~monstr@nat-108f.starnet.cz> has joined #cip06:50
*** monstr <monstr!~monstr@nat-108f.starnet.cz> has quit IRC (Ping timeout: 256 seconds)06:55
*** prabhakalad <prabhakalad!~prabhakar@122.167.136.50> has quit IRC (Ping timeout: 256 seconds)07:39
*** prabhakalad <prabhakalad!~prabhakar@171.61.180.247> has joined #cip08:01
*** monstr <monstr!~monstr@nat-108f.starnet.cz> has joined #cip10:12
*** monstr <monstr!~monstr@nat-108f.starnet.cz> has quit IRC (Ping timeout: 256 seconds)10:27
*** prabhakalad <prabhakalad!~prabhakar@171.61.180.247> has quit IRC (Ping timeout: 260 seconds)10:43
*** prabhakalad <prabhakalad!~prabhakar@171.61.180.247> has joined #cip10:44
*** masami <masami!~masami@fl1-125-197-94-238.tky.mesh.ad.jp> has joined #cip11:57
*** jki <jki!~jki@62.156.206.62> has joined #cip11:57
jkihi all12:00
arisuthi12:00
uli_hello12:00
pave1Hi!12:00
masamihi12:01
jki#startmeeting CIP IRC weekly meeting12:01
collab-meetbot`Meeting started Thu Nov 13 12:01:23 2025 UTC and is due to finish in 60 minutes.  The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot.12:01
collab-meetbot`Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.12:01
collab-meetbot`The meeting name has been set to 'cip_irc_weekly_meeting'12:01
*** collab-meetbot` changes topic to " (Meeting topic: CIP IRC weekly meeting)"12:01
jki#topic AI review12:01
*** collab-meetbot` changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"12:01
jkinone on my list12:01
jki512:01
jki412:01
jki312:01
jki212:01
jki112:01
jki#topic Kernel maintenance updates12:01
*** collab-meetbot` changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"12:01
uli_working on 4.1912:02
masamiThis week reported 69 new CVEs and 0 updated CVEs.12:02
pave1I was reviewing 6.12.55 and .5812:02
jkiiwamatsu wrote: "I reviewed 6.12.55 and 56."12:02
jkianything else?12:03
jki512:03
jki412:03
jki312:03
jki212:03
jki112:03
jki#topic Kernel release status12:03
*** collab-meetbot` changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)"12:03
jkiall on track today12:04
jkianything to add?12:04
jki512:04
jki412:04
jki312:04
jki212:04
jki112:04
jki#topic Kernel testing12:04
*** collab-meetbot` changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"12:04
patersoncHello12:05
patersoncNothing that new in my world12:05
* jki is struggling with getting the boards sent, formal issues, not unexpected12:05
patersoncThanks Jan. Let me know if you need any additional info from my side12:05
jkiECCN and AL numbers? :)12:06
arisutnothing on my side, currently documenting kci-dev12:07
patersoncI may be able to dig out an ECCn for the Renesas boards12:07
jkipatersonc: that would be a good start already12:07
arisutstruggling getting updates on the x86 boards12:07
patersoncIwamatsu-san isn't here today12:08
jkiarisut: an issue related to our infrastructure?12:09
arisutwe are not yet sure, probably configuration related12:10
jkicip-kernel-configs again...?12:12
arisutyes12:13
jkiare you using the cip_merged_defconfig? and on which device(s)?12:13
jkishould we move on?12:16
arisutwe are using merged config as far as I remember12:17
arisutx8612:17
jkithat is rather broad12:17
jkithe defconfig boots on the IPCs and the MCOM to my best knowledge12:18
arisutde0 nano for example12:18
jkithat ist armhf, not x86 :)12:18
jkiwhich kernel version?12:18
jkiI still have some nanosocs close to me, could do a build for it12:19
arisutsorry there is a list that I made with patersonc searching it12:19
arisuthttps://docs.google.com/spreadsheets/d/1UH9oi8ETJ6ndtd2tmFGEcc12L3JCPbtUbRgnWBYdshw/edit?gid=0#gid=012:19
jkithe references job for the nanosoc gives 40412:22
jkinot seeing any x86 issues in that list12:23
jkibut let me get the nanosoc booting with out config(s)12:23
jkiokay...12:23
jkimore topics?12:23
jki512:25
jki412:25
jki312:25
jki212:25
jki112:25
jki#topic AOB12:25
*** collab-meetbot` changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"12:25
jkiriscv reference board:12:26
jkithe beaglev-fire is definitely a good option12:26
jkiavailability for 10 years is likely12:27
jki6.12 upstream support12:27
jkiand we would probably get some 4-6 boards from beagleboard12:27
jkithe other candidate was the visionfive2 lite12:27
patersoncSounds promising12:27
jki5 years+, 6.12 dtb backparts needed, boards would be provided as well12:28
jkistill, it looks like we should propose the fire to the TSC next week, right?12:28
patersoncIt seems the best fit to me12:29
pave1Both look nice to me.12:29
jkifurther opinions?12:31
jkiwe can, of course, have a short discussion during the call as well12:31
jkii will list the results, but unless there are arguments brought forward, I would propose the fire in the name of the kernel WG12:32
jkiother topics for today?12:34
patersoncFYI you can see the latest CIP testing status in kernelci here: https://dashboard.kernelci.org/tree?i=14&ts=cip12:34
patersoncIt looks like our x86 boot issues have gone. Maybe a recent update in cip-kernel-config?12:34
jkiwe raised the number of cores used on the mcom12:34
arisutoh? I should check12:35
arisutagain12:35
jkithat resolved the IEC test issues with cip-core at least12:35
arisutthanks12:35
jkithen let's close for today, /me needs to build for the nanosoc...12:36
jki512:36
jki412:36
jki312:36
jki212:36
jki112:36
jki#endmeeting12:36
collab-meetbot`Meeting ended Thu Nov 13 12:36:44 2025 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)12:36
collab-meetbot`Minutes:        http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/11/cip.2025-11-13-12.01.html12:36
collab-meetbot`Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/11/cip.2025-11-13-12.01.txt12:36
collab-meetbot`Log:            http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/11/cip.2025-11-13-12.01.log.html12:36
*** collab-meetbot` changes topic to "Civil Infrastructure Platform Project. CIP mailing list at https://lists.cip-project.org/g/cip-dev | CIP kernel meeting every Thursday at 13:00 UTC | Find the meeting logs at https://ircbot.wl.linuxfoundation.org/meetings/cip/ and chat logs at https://ircbot.wl.linuxfoundation.org/logs/%23cip/"12:36
jkithanks!12:36
pave1Thank you!12:36
uli_thanks12:36
masamithank you12:36
*** masami <masami!~masami@fl1-125-197-94-238.tky.mesh.ad.jp> has quit IRC (Quit: Leaving)12:36
patersoncThanks all12:36
*** jki <jki!~jki@62.156.206.62> has quit IRC (Quit: Leaving)13:40
*** collab-meetbot <collab-meetbot!~supybot@ec2-35-167-58-160.us-west-2.compute.amazonaws.com> has joined #cip17:44
*** ChanServ sets mode: +o collab-meetbot17:44
*** collab-meetbot` <collab-meetbot`!~supybot@ec2-35-167-58-160.us-west-2.compute.amazonaws.com> has quit IRC (*.net *.split)17:50
*** shoragan <shoragan!~shoragan@user/shoragan> has quit IRC (*.net *.split)17:50
*** prabhakalad <prabhakalad!~prabhakar@171.61.180.247> has quit IRC (Ping timeout: 256 seconds)17:53
*** prabhakalad <prabhakalad!~prabhakar@171.61.180.247> has joined #cip17:54
*** prabhakalad <prabhakalad!~prabhakar@171.61.180.247> has quit IRC (Quit: Konversation terminated!)18:29

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!