| *** rajm has joined #cip | 06:19 | |
| *** pave1 has joined #cip | 08:57 | |
| *** vidda has joined #cip | 08:58 | |
| szlin | #startmeeting CIP IRC weekly meeting | 09:00 |
|---|---|---|
| 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 |
| brlogger | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 09:00 |
| brlogger | The meeting name has been set to 'cip_irc_weekly_meeting' | 09:00 |
| *** brlogger changes topic to " (Meeting topic: CIP IRC weekly meeting)" | 09:00 | |
| szlin | #topic rollcall | 09:00 |
| *** brlogger changes topic to "rollcall (Meeting topic: CIP IRC weekly meeting)" | 09:00 | |
| patersonc | hi | 09:00 |
| szlin | please say hi if you're around | 09:00 |
| pave1 | hi | 09:00 |
| fujita[m] | hi | 09:00 |
| vidda | hi | 09:00 |
| szlin | #topic AI review | 09:01 |
| *** brlogger changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)" | 09:01 | |
| iwamatsu | hi | 09:01 |
| szlin | 1. Provide the cases to cip-testing to build up the test environment - Iwamatsu-san | 09:01 |
| *** kazu has joined #cip | 09:01 | |
| szlin | iwamatsu: would you like to update the status? | 09:01 |
| iwamatsu | szlin: no update. this is WIP. | 09:01 |
| szlin | iwamatsu: thanks. | 09:01 |
| szlin | 2. Ask cip-dev which configurations need testing - patersonc | 09:01 |
| patersonc | Balls, I forgot to chase this again. Sorry! | 09:02 |
| szlin | patersonc: no worry, I will keep this AI | 09:02 |
| szlin | 3. Test LTS (pre)releases directly – patersonc | 09:02 |
| patersonc | No progress | 09:02 |
| szlin | noted. | 09:03 |
| szlin | #topic Kernel maintenance updates | 09:03 |
| *** brlogger changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)" | 09:03 | |
| pave1 | I've most of reviewed 4.19.36. I am debugging the -rt build failure. | 09:03 |
| szlin | pave1: thank you! | 09:03 |
| iwamatsu | I am reviewing Renesas's patches. I do not review LTS this week. | 09:04 |
| patersonc | Thanks | 09:04 |
| szlin | I plan to start cve tracker task next week. | 09:04 |
| szlin | any other topics? | 09:05 |
| szlin | 3 | 09:05 |
| szlin | 2 | 09:05 |
| szlin | 1 | 09:05 |
| szlin | #topic Kernel testing | 09:05 |
| *** brlogger changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)" | 09:05 | |
| patersonc | Hello | 09:05 |
| patersonc | Not much from me this week... | 09:05 |
| patersonc | #info There is some initial information on the RZ/G2M board added to the CIP wiki. More updates will come. | 09:05 |
| patersonc | #link https://wiki.linuxfoundation.org/civilinfrastructureplatform/ciptesting/cipreferencehardware/hihope-rzg2m | 09:05 |
| patersonc | #info linux-cip-ci can now build the RT configs from the cip-kernel-config repo. | 09:06 |
| patersonc | I'll submit patches to update .gitlab-ci.yml in the RT branches soon | 09:06 |
| pave1 | Thanks for that :-) | 09:06 |
| szlin | patersonc: thank you very much for your detailed report | 09:06 |
| patersonc | FYI, I'm on holiday next week without a laptop. | 09:06 |
| szlin | patersonc: happy holiday :-) | 09:06 |
| patersonc | That's it from me | 09:07 |
| szlin | any other topics? | 09:07 |
| szlin | 3 | 09:07 |
| szlin | 2 | 09:07 |
| szlin | 1 | 09:07 |
| szlin | #topic CIP Core | 09:07 |
| *** brlogger changes topic to "CIP Core (Meeting topic: CIP IRC weekly meeting)" | 09:07 | |
| kazu | 1. Package decision process (rev.2) was reviewed by WG members | 09:07 |
| kazu | AI: Get the number of CVEs of proposed package mechanically | 09:07 |
| kazu | I found that security issues in Debian packages are managed in the following repsitory: | 09:08 |
| kazu | https://salsa.debian.org/security-tracker-team/security-tracker/tree/master/data | 09:08 |
| kazu | and https://packages.debian.org/ja/sid/debsecan can parse them and print the summary | 09:08 |
| kazu | I will check if debsecan can generate information we want | 09:08 |
| kazu | 2. Update https://gitlab.com/cip-playground/cip-pkglist | 09:08 |
| kazu | To apply the changes in PDP rev.2 | 09:08 |
| kazu | Do you know the formal process to move a repo from playground to CIP? | 09:09 |
| kazu | sorry, cip-project i meant | 09:09 |
| szlin | sorry, I don't know. Maybe Chris knows. | 09:09 |
| szlin | kazu: we can check it after the meeting. | 09:10 |
| kazu | Thanks SZ | 09:10 |
| szlin | any other updates? | 09:10 |
| kazu | 3. Decide the CIP Core WG companies | 09:10 |
| kazu | That's all | 09:11 |
| szlin | kazu: thank you | 09:11 |
| szlin | any other topics? | 09:11 |
| szlin | 3 | 09:11 |
| szlin | 2 | 09:11 |
| szlin | 1 | 09:11 |
| szlin | #topic Software update | 09:11 |
| *** brlogger changes topic to "Software update (Meeting topic: CIP IRC weekly meeting)" | 09:11 | |
| patersonc | kazu: https://gitlab.com/cip-playground/cip-private-docs/blob/master/CIP_Process.md | 09:11 |
| kazu | There is no update about this topic in this week | 09:11 |
| szlin | swupdate got rejected due to logo license issue, Iwamatsu-san will handle it. | 09:11 |
| kazu | patersonc Thank you! | 09:12 |
| szlin | any other topics? | 09:12 |
| szlin | 3 | 09:12 |
| szlin | 2 | 09:12 |
| szlin | 1 | 09:12 |
| kazu | @szlin thank you for the information | 09:12 |
| szlin | #topic AOB | 09:13 |
| *** brlogger changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)" | 09:13 | |
| szlin | any other business? | 09:13 |
| fujita[m] | hi | 09:13 |
| fujita[m] | Does any company around here interested in Arm’s big.LITTLE with Energy Aware Scheduling (EAS)? | 09:13 |
| fujita[m] | It has been upstreamed from kernel 5.0 | 09:13 |
| fujita[m] | Unfortunately, 4.19 doesn’t have the code. | 09:13 |
| szlin | we havn't used big.LITTLE SoC so far. | 09:14 |
| patersonc | It might be a good feature for CIP to have? | 09:16 |
| patersonc | Something that we provide over LTS | 09:16 |
| pave1 | Ummm. Dunno. Do we? | 09:16 |
| iwamatsu | RZ G2M has big.little, maybe. | 09:16 |
| patersonc | Yep | 09:17 |
| pave1 | It is useful for maximum performance on high-end cellphones | 09:17 |
| kazu | fujita[m] there is no requirement in my current jobs at the moment, but not sure in the future | 09:17 |
| pave1 | And it is fairly young (not being in 4.19) | 09:17 |
| pave1 | That does not play well with maximum stability and 10 years of support :-) | 09:18 |
| patersonc | Hasn't it been used in Android for a while? | 09:18 |
| fujita[m] | Ummm | 09:18 |
| pave1 | Yes, Android does a lot of crazy stuff :-) | 09:19 |
| fujita[m] | Some industory company, which are our customers seems to interestet in that | 09:19 |
| pave1 | I mean, yes, we can do it if it is really needed. | 09:19 |
| pave1 | But "it sounds cool" .. is not good enough reason. | 09:19 |
| patersonc | Also, if CIP is targeting IOT (edgex etc.), wouldn't EAS be a valid use case? | 09:19 |
| pave1 | Not really. | 09:20 |
| patersonc | Doesn't it save power? | 09:20 |
| patersonc | Or are IOT too small for biglittle? | 09:20 |
| pave1 | Yes, but IOT devices should not require this powerful silicon in the first place. | 09:20 |
| szlin | allow me to end this meeting first, and we can continue to discuss afterward. | 09:20 |
| patersonc | :) | 09:20 |
| fujita[m] | Thanks for comments | 09:21 |
| szlin | any other topics? | 09:21 |
| szlin | #endmeeting | 09:21 |
| brlogger | Meeting ended Thu Sep 5 09:21:12 2019 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 09:21 |
| brlogger | Minutes: https://irclogs.baserock.org/meetings/cip/2019/09/cip.2019-09-05-09.00.html | 09:21 |
| brlogger | Minutes (text): https://irclogs.baserock.org/meetings/cip/2019/09/cip.2019-09-05-09.00.txt | 09:21 |
| brlogger | Log: https://irclogs.baserock.org/meetings/cip/2019/09/cip.2019-09-05-09.00.log.html | 09:21 |
| *** brlogger changes topic to "Civil Infrastructure Platform Project. Find the logs at https://irclogs.baserock.org/cip/" | 09:21 | |
| szlin | thanks. | 09:21 |
| kazu | Thank you | 09:21 |
| pave1 | Thank you! :) | 09:21 |
| fujita[m] | Thank you! | 09:21 |
| iwamatsu | thanks | 09:21 |
| pave1 | I'd say IOT is normally too small to this, yes. | 09:21 |
| iwamatsu | pave1: I'd like to fix a pinctl series commit with space problems, can I do it? | 09:21 |
| patersonc | iwamatsu: I have a question for you before after the current topic | 09:21 |
| szlin | pave1: usually IoT end device used Cortex-M in the most of the time | 09:22 |
| iwamatsu | pave1: https://lists.cip-project.org/pipermail/cip-dev/2019-September/003149.html | 09:22 |
| pave1 | iwamatsu: Yes, I don't think that's a problem. We can still identify upstream using the hashes embedded. | 09:22 |
| iwamatsu | patersinc: please. | 09:22 |
| iwamatsu | pave1: ok, thanks. | 09:22 |
| iwamatsu | patersonc: please | 09:23 |
| patersonc | iwamatsu: Do you want me to submit the gitlab-ci changes to build/test RZ/G2M now? | 09:23 |
| patersonc | So you can merge the first board patches and CI test them at the same time? | 09:23 |
| iwamatsu | patersonc: Okay. | 09:24 |
| patersonc | Okay | 09:25 |
| patersonc | 5 mins... | 09:25 |
| iwamatsu | patersonc: it is good idea. please send patch. | 09:25 |
| patersonc | Let me just check cip-kernel-config | 09:26 |
| patersonc | That may need updating as well | 09:26 |
| pave1 | Concerning big.Little: I'd not be surprised if it appeared in car entertainment systems. If we have to support it, we can try. .. I'd have to see the patches. But unlike normal changes ("lets introduce these few drivers") this will likely need core changes. That's not cool, that's scary ;-). | 09:27 |
| iwamatsu | patersonc: thanks! | 09:27 |
| patersonc | Ah, actually I'll need to update linux-cip-ci with the healthcheck as well for testing | 09:28 |
| fujita[m] | pave1: True. These patches will be changed the scheduler | 09:28 |
| patersonc | iwamatsu: Maybe give me an hour ;) | 09:29 |
| iwamatsu | patersonc: No problem, Japan is now dinner time :-) | 09:30 |
| fujita[m] | If there are exact users, do you all think backporting EAS will be acceptable? | 09:31 |
| pave1 | I guess that is not my decision. | 09:32 |
| pave1 | I would have to see the patch. | 09:32 |
| pave1 | But stable kernel rules would not allow it, and we are normally "mostly following" them. | 09:32 |
| fujita[m] | Yes, I can understand that. | 09:33 |
| fujita[m] | So, why CIP adoupt RT then? Does anyone know? | 09:34 |
| pave1 | If EAS is considered important enough, I believe it would make sense to be handled same way realtime is: separate branch, so that we can not create problems for people not needing it. | 09:35 |
| pave1 | fujita: not sure about realtime... I joined CIP project after the decision was made. | 09:35 |
| fujita[m] | Ummm | 09:36 |
| fujita[m] | We shoud find real potential customers first. | 09:36 |
| fujita[m] | Anyway, thank you for the comments | 09:38 |
| pave1 | You are welcome :-) | 09:39 |
| patersonc | pave1: Are you going to Lyon? | 09:40 |
| pave1 | patersonc: I'm in Prague now... and not planning any conferences this month. | 09:41 |
| patersonc | okay | 09:43 |
| *** kazu has quit IRC | 09:44 | |
| pave1 | bye for now... | 09:45 |
| *** pave1 has quit IRC | 09:45 | |
| fujita[m] | thanks, see you all | 09:46 |
| *** vidda has quit IRC | 10:05 | |
| *** alicef has quit IRC | 10:14 | |
| *** alicef has joined #cip | 10:17 | |
| *** mungaip_ has joined #cip | 13:48 | |
| *** mungaip has joined #cip | 13:58 | |
| *** mungaip has quit IRC | 14:05 | |
| *** mungaip has joined #cip | 14:11 | |
| *** mungaip has quit IRC | 14:32 | |
| *** mungaip_ has quit IRC | 14:50 | |
| *** mungaip_ has joined #cip | 14:50 | |
| *** mungaip_ has quit IRC | 15:12 | |
| *** rajm has quit IRC | 21:55 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!