IRC logs for #cip for Thursday, 2021-11-18

« Wednesday, 2021-11-17 Index Friday, 2021-11-19 »
*** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has joined #cip07:24
*** monstr <monstr!~monstr@2a02:768:2307:40d6::45a> has joined #cip08:20
*** toscalix <toscalix!~toscalix@174.red-79-144-82.dynamicip.rima-tde.net> has joined #cip10:22
*** toscalix <toscalix!~toscalix@174.red-79-144-82.dynamicip.rima-tde.net> has quit IRC10:25
*** toscalix <toscalix!~toscalix@174.red-79-144-82.dynamicip.rima-tde.net> has joined #cip10:26
*** masami <masami!~masami@FL1-122-133-108-128.tky.mesh.ad.jp> has joined #cip12:01
*** uli <uli!~uli@55d4f913.access.ecotel.net> has joined #cip12:01
*** pave1 <pave1!~mobian@78-80-25-189.customers.tmcz.cz> has joined #cip12:53
*** jki <jki!~jki@165.225.26.235> has joined #cip13:00
jki#startmeeting CIP IRC weekly meeting13:00
*** patersonc[m] <patersonc[m]!~patersonc@2001:470:69fc:105::aaf> has joined #cip13:00
brlogger`Meeting started Thu Nov 18 13:00:48 2021 UTC and is due to finish in 60 minutes.  The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot.13:00
brlogger`Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:00
brlogger`The meeting name has been set to 'cip_irc_weekly_meeting'13:00
*** brlogger` changes topic to " (Meeting topic: CIP IRC weekly meeting)"13:00
jkihi everyone!13:00
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #cip13:01
patersonc[m]Afternoon13:01
ulihello13:01
masamiHi13:01
pave1hi13:01
alicefmHi13:01
jkiso, let's get started13:03
jki#topic AI review13:03
*** brlogger` changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"13:03
jki1. Combine root filesystem with kselftest binary - iwamatsu & alicef13:03
jkialicefm: thanks for sending the patches!13:04
jkii think i only had minor remarks on the structuring13:04
alicefmYes I’m rebasing and I will send again13:05
jkiwhat will be needed to kick off kselftest?13:06
alicefmI’m currently working with gtucker for the kselftest pull request13:07
*** toscalix_ <toscalix_!~agustinbe@174.red-79-144-82.dynamicip.rima-tde.net> has joined #cip13:08
jkiok13:08
alicefmAnd recently we got Patersonc pull request merged https://github.com/kernelci/kernelci-core/pull/78313:09
*** toscalix_ <toscalix_!~agustinbe@174.red-79-144-82.dynamicip.rima-tde.net> has quit IRC13:09
alicefmThat is enabling lab cip to execute more test case13:11
patersonc[m]alicef: Thanks for your help getting it over the line13:11
alicefmnp13:11
*** pave1 <pave1!~mobian@78-80-25-189.customers.tmcz.cz> has quit IRC13:12
jkianything else for this AI?13:12
jki2. Look into S3 artifact upload issues - patersonc13:13
*** pave1 <pave1!~mobian@nat-179.starnet.cz> has joined #cip13:14
patersonc[m]No updates13:14
jkiok, any other AIs I missed?13:14
jki313:15
jki213:15
jki113:15
jki#topic Kernel maintenance updates13:15
*** brlogger` changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"13:15
pave1I was reviewing 5.10.79 and am now reviewing 5.10.8013:15
ulinow reviewing 5.10.8013:15
masamiThere is 2 new CVEs in this week.  Patches are available but they haven't been merged into the mainline yet.13:15
pave1Yup. And in general news, rowhammer is back with new variant13:16
pave1and new CVE.13:16
jkiyeah, but no more fixes for rowhammer...13:17
jkianything else here?13:19
patersonc[m]o/13:20
patersonc[m]I picked up a task to enable WiFI configs for the RZ/G2M platform13:20
patersonc[m]How does CIP want to handle the firmware?13:20
patersonc[m]Include it in the filesystem? Or build it into the Kernel?13:20
jkiwhat speaks against filesystem?13:22
jkiis it part of linux-firmware?13:23
patersonc[m]yes, part of linux-firmware13:23
patersonc[m]https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/ti-connectivity/wl18xx-fw-4.bin13:23
jkidebian-packaged then, I assume13:24
patersonc[m]no objections to including it in isar-cip-core then?13:24
patersonc[m]Do we have connman in cip-core?13:24
jkiseems it's not packaged by bullseye, or I'm missing it ATM13:25
jkihttps://packages.debian.org/source/bullseye/firmware-nonfree13:25
jkiwe can write a recipe for pulling the binaries and making a debian package when it's currently missing13:26
jkimaybe also file a bug or packaging request with Debian if so13:26
jkibut there is https://packages.debian.org/bullseye/conman at least - why?13:27
jkino, https://packages.debian.org/bullseye/connman13:28
patersonc[m]Don't we need a network manager of some sort to actually use/test the WiFi?13:28
pave1not really13:29
jkiiw tools, ifupdown would work as well13:29
jkiwe likely only need to run a scan and check if it's non-empty13:29
patersonc[m]Okay13:29
jkiprovided there some AP around the lab at least13:30
jkiand not too much metal...13:30
patersonc[m]Okay13:31
pave1unencrypted wifi can be setup using iwconfig13:31
jkiencrypted only required wpa_supplication in addition13:31
jkibut the question is what we want to test under that "basic testing" promise13:32
patersonc[m]Just running a scan would be the easiest choice13:33
pave1Doing scan is already big improvement over current situation.13:33
jkithen let's start like this, I would say13:34
patersonc[m]I can get a wifi network set up at lab-cip-renesas for testing if we really want13:34
patersonc[m]Would just mean a lot of arguing with IT13:34
jki:)13:35
prabhakarladwe can have one board setup as an AP instead?13:35
pave1patersonc: for testing, ap not connected anywhere would be enough13:36
pave1we could try to connect to its web server.13:36
patersonc[m]prabhakarlad: It's possible. LAVA even supports multiple boards for testing.13:36
pave1that should not be too scary for IT13:36
patersonc[m]You'd be surprised ;)13:37
jkiless scary than asking to let the devices join the corporate wifi ;)13:37
patersonc[m]Anyhow, let's park this discussion for now. I'll investigate13:38
jkiok13:38
jkiTIA!13:38
jkito the topic we already touched:13:39
jki#topic Kernel testing13:39
*** brlogger` changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"13:39
patersonc[m]:)13:39
jkiFYI: Quirin is currently exploring how to improve automated RT testing, also for cip-rt13:40
jkihttps://lore.kernel.org/linux-rt-users/20211112143020.ci72q3yfamjx6pgt@linutronix.de/T/#t13:40
patersonc[m]Yea not much to add really. Other then I really meant to get around to the CI issues this week. So far have failed, sorry13:41
patersonc[m]Awesome13:41
alicefmKernelCI is working on adding rt testing also to cip13:41
jkiany pointer on that?13:42
jkiwould forward right away13:42
alicefmI open a issue on that not yet a pull request13:42
alicefmBut working on that13:42
patersonc[m]https://github.com/kernelci/kernelci-core/issues/47413:43
patersonc[m]https://github.com/kernelci/kernelci-core/issues/80013:43
jkithanks, just found as well13:43
alicefmVeremitz is sometime helping out with Gentoo and gkernelci13:44
alicefmMjeveritt13:44
alicefmHe also was interested in rt testing13:45
jkimaybe you can connect them?13:46
jkiunless he's already active in one of the issues13:46
alicefmHe already commented on the issue13:47
jkiperfect13:47
jkianything else?13:48
jki313:48
jki213:48
jki113:48
jki#topic AOB13:48
*** brlogger` changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"13:48
jkiwho has any?13:49
patersonc[m]alicef: Are you aware of the "extended CIP TSC" coming up?13:49
alicefmExtended?13:49
patersonc[m]Long meeting :P It's what we used to do face to face at conferences13:49
alicefmNo I didn’t know13:50
alicefmIs my presence needed?13:50
patersonc[m]It may be good if you could attend, given that you do most of the testing work13:50
patersonc[m]Up to you13:50
patersonc[m]It's on the 26th Nov13:51
alicefmOk I will look if I can join13:51
alicefmThanks13:51
patersonc[m]Thank you13:52
patersonc[m]I'll get an invite sent13:52
jkigood point, I think I had to draft my own blocker as well...13:54
jkianything else?13:55
jki313:56
jki213:56
jki113:56
jki#endmeeting13:56
brlogger`Meeting ended Thu Nov 18 13:56:12 2021 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:56
brlogger`Minutes:        https://irclogs.baserock.org/meetings/cip/2021/11/cip.2021-11-18-13.00.html13:56
brlogger`Minutes (text): https://irclogs.baserock.org/meetings/cip/2021/11/cip.2021-11-18-13.00.txt13:56
brlogger`Log:            https://irclogs.baserock.org/meetings/cip/2021/11/cip.2021-11-18-13.00.log.html13:56
*** brlogger` changes topic to "Civil Infrastructure Platform Project. Find the logs at https://irclogs.baserock.org/cip/"13:56
jkithanks all!13:56
masamithank you!13:56
ulibye13:56
alicefmThanks you13:57
jkibye!13:57
pave1thank you... and stay safe.13:57
patersonc[m]ttfn13:58
*** pave1 <pave1!~mobian@nat-179.starnet.cz> has quit IRC13:58
alicefmAh I forgot13:59
alicefmWe have now a cip project board14:00
alicefmhttps://github.com/orgs/kernelci/projects/1114:00
alicefmpatersonc: ^14:01
alicefmMaybe would be nice to tweet about this14:01
patersonc[m]jki: Do you know if CIP has a new marketing person yet?14:02
jkino idea, better ask neal14:02
jkialready did that, you were on CC14:41
patersonc[m]jki: Thanks14:52
*** jki <jki!~jki@165.225.26.235> has quit IRC14:54
*** monstr <monstr!~monstr@2a02:768:2307:40d6::45a> has quit IRC15:08
*** patersonc[m] <patersonc[m]!~patersonc@2001:470:69fc:105::aaf> has quit IRC16:24
*** alicefm <alicefm!~alicefm@user/alicefm> has quit IRC16:24
*** dl9pf <dl9pf!sid395223@helmsley.irccloud.com> has quit IRC16:35
*** patersonc[m] <patersonc[m]!~patersonc@2001:470:69fc:105::aaf> has joined #cip16:35
*** sashal <sashal!sid491190@hampstead.irccloud.com> has quit IRC16:36
*** rynofinn____ <rynofinn____!sid362734@lymington.irccloud.com> has quit IRC16:39
*** jwardy <jwardy!sid454028@uxbridge.irccloud.com> has quit IRC16:39
*** arnd <arnd!sid21101@hampstead.irccloud.com> has quit IRC16:39
*** jjardon <jjardon!sid723@tinside.irccloud.com> has quit IRC16:40
*** rynofinn____ <rynofinn____!sid362734@lymington.irccloud.com> has joined #cip16:41
*** dl9pf <dl9pf!sid395223@helmsley.irccloud.com> has joined #cip16:41
*** arnd <arnd!sid21101@hampstead.irccloud.com> has joined #cip16:41
*** jwardy <jwardy!sid454028@uxbridge.irccloud.com> has joined #cip16:42
*** sashal <sashal!sid491190@hampstead.irccloud.com> has joined #cip16:42
*** jjardon <jjardon!sid723@tinside.irccloud.com> has joined #cip16:44
*** alicefm <alicefm!~alicefm@user/alicefm> has joined #cip16:56
*** patersonc[m] <patersonc[m]!~patersonc@2001:470:69fc:105::aaf> has quit IRC17:00
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC17:30
*** toscalix <toscalix!~toscalix@174.red-79-144-82.dynamicip.rima-tde.net> has quit IRC17:48
*** toscalix_ <toscalix_!~agustinbe@174.red-79-144-82.dynamicip.rima-tde.net> has joined #cip18:24
*** toscalix_ <toscalix_!~agustinbe@174.red-79-144-82.dynamicip.rima-tde.net> has quit IRC18:25
*** toscalix_ <toscalix_!~agustinbe@174.red-79-144-82.dynamicip.rima-tde.net> has joined #cip18:26
*** toscalix_ is now known as toscalix18:26
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #cip18:26
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC20:44
*** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has quit IRC22:51
« Wednesday, 2021-11-17 Index Friday, 2021-11-19 »

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