09:00:08 <szlin> #startmeeting CIP IRC weekly meeting
09:00:08 <brlogger> Meeting started Thu Sep  5 09:00:08 2019 UTC and is due to finish in 60 minutes.  The chair is szlin. Information about MeetBot at http://wiki.debian.org/MeetBot.
09:00:08 <brlogger> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
09:00:08 <brlogger> The meeting name has been set to 'cip_irc_weekly_meeting'
09:00:18 <szlin> #topic rollcall
09:00:22 <patersonc> hi
09:00:23 <szlin> please say hi if you're around
09:00:28 <pave1> hi
09:00:40 <fujita[m]> hi
09:00:59 <vidda> hi
09:01:08 <szlin> #topic AI review
09:01:15 <iwamatsu> hi
09:01:16 <szlin> 1. Provide the cases to cip-testing to build up the test environment - Iwamatsu-san
09:01:32 <szlin> iwamatsu: would you like to update the status?
09:01:33 <iwamatsu> szlin: no update. this is WIP.
09:01:39 <szlin> iwamatsu: thanks.
09:01:48 <szlin> 2. Ask cip-dev which configurations need testing - patersonc
09:02:03 <patersonc> Balls, I forgot to chase this again. Sorry!
09:02:29 <szlin> patersonc: no worry, I will keep this AI
09:02:38 <szlin> 3. Test LTS (pre)releases directly – patersonc
09:02:55 <patersonc> No progress
09:03:13 <szlin> noted.
09:03:20 <szlin> #topic Kernel maintenance updates
09:03:32 <pave1> I've most of reviewed 4.19.36. I am debugging the -rt build failure.
09:03:45 <szlin> pave1: thank you!
09:04:20 <iwamatsu> I am reviewing Renesas's patches. I do not review LTS this week.
09:04:43 <patersonc> Thanks
09:04:59 <szlin> I plan to start cve tracker task next week.
09:05:07 <szlin> any other topics?
09:05:22 <szlin> 3
09:05:23 <szlin> 2
09:05:24 <szlin> 1
09:05:32 <szlin> #topic Kernel testing
09:05:44 <patersonc> Hello
09:05:49 <patersonc> Not much from me this week...
09:05:52 <patersonc> #info There is some initial information on the RZ/G2M board added to the CIP wiki. More updates will come.
09:05:56 <patersonc> #link https://wiki.linuxfoundation.org/civilinfrastructureplatform/ciptesting/cipreferencehardware/hihope-rzg2m
09:06:03 <patersonc> #info linux-cip-ci can now build the RT configs from the cip-kernel-config repo.
09:06:23 <patersonc> I'll submit patches to update .gitlab-ci.yml in the RT branches soon
09:06:28 <pave1> Thanks for that :-)
09:06:31 <szlin> patersonc: thank you very much for your detailed report
09:06:37 <patersonc> FYI, I'm on holiday next week without a laptop.
09:06:53 <szlin> patersonc: happy holiday :-)
09:07:00 <patersonc> That's it from me
09:07:15 <szlin> any other topics?
09:07:24 <szlin> 3
09:07:26 <szlin> 2
09:07:27 <szlin> 1
09:07:32 <szlin> #topic CIP Core
09:07:40 <kazu> 1. Package decision process (rev.2) was reviewed by WG members
09:07:51 <kazu> AI: Get the number of CVEs of proposed package mechanically
09:08:00 <kazu> I found that security issues in Debian packages are managed in the following repsitory:
09:08:09 <kazu> https://salsa.debian.org/security-tracker-team/security-tracker/tree/master/data
09:08:18 <kazu> and https://packages.debian.org/ja/sid/debsecan can parse them and print the summary
09:08:31 <kazu> I will check if debsecan can generate information we want
09:08:42 <kazu> 2. Update https://gitlab.com/cip-playground/cip-pkglist
09:08:57 <kazu> To apply the changes in PDP rev.2
09:09:03 <kazu> Do you know the formal process to move a repo from playground to CIP?
09:09:23 <kazu> sorry, cip-project i meant
09:09:46 <szlin> sorry, I don't know. Maybe Chris knows.
09:10:32 <szlin> kazu: we can check it after the meeting.
09:10:42 <kazu> Thanks SZ
09:10:45 <szlin> any other updates?
09:10:54 <kazu> 3. Decide the CIP Core WG companies
09:11:01 <kazu> That's all
09:11:09 <szlin> kazu: thank you
09:11:12 <szlin> any other topics?
09:11:27 <szlin> 3
09:11:27 <szlin> 2
09:11:28 <szlin> 1
09:11:33 <szlin> #topic Software update
09:11:49 <patersonc> kazu: https://gitlab.com/cip-playground/cip-private-docs/blob/master/CIP_Process.md
09:11:51 <kazu> There is no update about this topic in this week
09:11:54 <szlin> swupdate got rejected due to logo license issue, Iwamatsu-san will handle it.
09:12:13 <kazu> patersonc Thank you!
09:12:44 <szlin> any other topics?
09:12:53 <szlin> 3
09:12:53 <szlin> 2
09:12:53 <szlin> 1
09:12:57 <kazu> @szlin thank you for the information
09:13:08 <szlin> #topic AOB
09:13:14 <szlin> any other business?
09:13:17 <fujita[m]> hi
09:13:22 <fujita[m]> Does any company around here interested in Arm’s big.LITTLE with Energy Aware Scheduling (EAS)?
09:13:31 <fujita[m]> It has been upstreamed from kernel 5.0
09:13:40 <fujita[m]> Unfortunately, 4.19 doesn’t have the code.
09:14:52 <szlin> we havn't used big.LITTLE SoC so far.
09:16:00 <patersonc> It might be a good feature for CIP to have?
09:16:13 <patersonc> Something that we provide over LTS
09:16:30 <pave1> Ummm. Dunno. Do we?
09:16:57 <iwamatsu> RZ G2M  has big.little, maybe.
09:17:05 <patersonc> Yep
09:17:10 <pave1> It is useful for maximum performance on high-end cellphones
09:17:19 <kazu> fujita[m]  there is no requirement in my current jobs at the moment, but not sure in the future
09:17:44 <pave1> And it is fairly young (not being in 4.19)
09:18:10 <pave1> That does not play well with maximum stability and 10 years of support :-)
09:18:11 <patersonc> Hasn't it been used in Android for a while?
09:18:40 <fujita[m]> Ummm
09:19:03 <pave1> Yes, Android does a lot of crazy stuff :-)
09:19:21 <fujita[m]> Some industory company, which are our customers seems to interestet in that
09:19:41 <pave1> I mean, yes, we can do it if it is really needed.
09:19:55 <pave1> But "it sounds cool" .. is not good enough reason.
09:19:58 <patersonc> Also, if CIP is targeting IOT (edgex etc.), wouldn't EAS be a valid use case?
09:20:11 <pave1> Not really.
09:20:20 <patersonc> Doesn't it save power?
09:20:39 <patersonc> Or are IOT too small for biglittle?
09:20:40 <pave1> Yes, but IOT devices should not require this powerful silicon in the first place.
09:20:48 <szlin> allow me to end this meeting first, and we can continue to discuss afterward.
09:20:53 <patersonc> :)
09:21:02 <fujita[m]> Thanks for comments
09:21:09 <szlin> any other topics?
09:21:12 <szlin> #endmeeting