12:01:23 <jki> #startmeeting CIP IRC weekly meeting
12:01:23 <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:23 <collab-meetbot`> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
12:01:23 <collab-meetbot`> The meeting name has been set to 'cip_irc_weekly_meeting'
12:01:31 <jki> #topic AI review
12:01:36 <jki> none on my list
12:01:41 <jki> 5
12:01:43 <jki> 4
12:01:44 <jki> 3
12:01:46 <jki> 2
12:01:48 <jki> 1
12:01:50 <jki> #topic Kernel maintenance updates
12:02:00 <uli_> working on 4.19
12:02:01 <masami> This week reported 69 new CVEs and 0 updated CVEs.
12:02:22 <pave1> I was reviewing 6.12.55 and .58
12:02:23 <jki> iwamatsu wrote: "I reviewed 6.12.55 and 56."
12:03:17 <jki> anything else?
12:03:44 <jki> 5
12:03:46 <jki> 4
12:03:48 <jki> 3
12:03:49 <jki> 2
12:03:51 <jki> 1
12:03:53 <jki> #topic Kernel release status
12:04:02 <jki> all on track today
12:04:16 <jki> anything to add?
12:04:33 <jki> 5
12:04:35 <jki> 4
12:04:37 <jki> 3
12:04:39 <jki> 2
12:04:41 <jki> 1
12:04:44 <jki> #topic Kernel testing
12:05:10 <patersonc> Hello
12:05:14 <patersonc> Nothing that new in my world
12:05:34 * jki is struggling with getting the boards sent, formal issues, not unexpected
12:05:57 <patersonc> Thanks Jan. Let me know if you need any additional info from my side
12:06:32 <jki> ECCN and AL numbers? :)
12:07:07 <arisut> nothing on my side, currently documenting kci-dev
12:07:15 <patersonc> I may be able to dig out an ECCn for the Renesas boards
12:07:44 <jki> patersonc: that would be a good start already
12:07:52 <arisut> struggling getting updates on the x86 boards
12:08:22 <patersonc> Iwamatsu-san isn't here today
12:09:28 <jki> arisut: an issue related to our infrastructure?
12:10:36 <arisut> we are not yet sure, probably configuration related
12:12:38 <jki> cip-kernel-configs again...?
12:13:09 <arisut> yes
12:13:53 <jki> are you using the cip_merged_defconfig? and on which device(s)?
12:16:35 <jki> should we move on?
12:17:05 <arisut> we are using merged config as far as I remember
12:17:10 <arisut> x86
12:17:48 <jki> that is rather broad
12:18:04 <jki> the defconfig boots on the IPCs and the MCOM to my best knowledge
12:18:11 <arisut> de0 nano for example
12:18:27 <jki> that ist armhf, not x86 :)
12:18:39 <jki> which kernel version?
12:19:02 <jki> I still have some nanosocs close to me, could do a build for it
12:19:36 <arisut> sorry there is a list that I made with patersonc searching it
12:19:58 <arisut> https://docs.google.com/spreadsheets/d/1UH9oi8ETJ6ndtd2tmFGEcc12L3JCPbtUbRgnWBYdshw/edit?gid=0#gid=0
12:22:14 <jki> the references job for the nanosoc gives 404
12:23:06 <jki> not seeing any x86 issues in that list
12:23:23 <jki> but let me get the nanosoc booting with out config(s)
12:23:52 <jki> okay...
12:23:57 <jki> more topics?
12:25:43 <jki> 5
12:25:45 <jki> 4
12:25:47 <jki> 3
12:25:49 <jki> 2
12:25:50 <jki> 1
12:25:52 <jki> #topic AOB
12:26:17 <jki> riscv reference board:
12:26:45 <jki> the beaglev-fire is definitely a good option
12:27:02 <jki> availability for 10 years is likely
12:27:11 <jki> 6.12 upstream support
12:27:33 <jki> and we would probably get some 4-6 boards from beagleboard
12:27:49 <jki> the other candidate was the visionfive2 lite
12:27:52 <patersonc> Sounds promising
12:28:09 <jki> 5 years+, 6.12 dtb backparts needed, boards would be provided as well
12:28:50 <jki> still, it looks like we should propose the fire to the TSC next week, right?
12:29:17 <patersonc> It seems the best fit to me
12:29:49 <pave1> Both look nice to me.
12:31:03 <jki> further opinions?
12:31:22 <jki> we can, of course, have a short discussion during the call as well
12:32:52 <jki> i will list the results, but unless there are arguments brought forward, I would propose the fire in the name of the kernel WG
12:34:11 <jki> other topics for today?
12:34:36 <patersonc> FYI you can see the latest CIP testing status in kernelci here: https://dashboard.kernelci.org/tree?i=14&ts=cip
12:34:36 <patersonc> It looks like our x86 boot issues have gone. Maybe a recent update in cip-kernel-config?
12:34:59 <jki> we raised the number of cores used on the mcom
12:35:09 <arisut> oh? I should check
12:35:10 <arisut> again
12:35:11 <jki> that resolved the IEC test issues with cip-core at least
12:35:12 <arisut> thanks
12:36:27 <jki> then let's close for today, /me needs to build for the nanosoc...
12:36:33 <jki> 5
12:36:36 <jki> 4
12:36:38 <jki> 3
12:36:40 <jki> 2
12:36:42 <jki> 1
12:36:44 <jki> #endmeeting