07:18:40 * ** tpollard has quit IRC
07:52:08 * ** rajm has joined #cip
07:56:33 * ** mungaip has joined #cip
08:12:05 * ** sangorrin has joined #cip
08:19:39 * ** tpollard has joined #cip
08:48:39 * ** vidda has joined #cip
08:54:09 * ** toscalix has joined #cip
09:00:08 <szlin> #startmeeting
09:00:15 <szlin> #roll call
09:00:18 <patersonc> hi
09:00:19 <vidda> hi
09:00:20 <szlin> please say hi if you're here
09:00:25 <szlin> hi ._./~\
09:00:29 <fujita[m]> hi
09:00:41 <mungaip> hi
09:00:45 <mungaip> hi
09:01:13 <szlin> #topic kernel maintenance updates
09:01:18 <szlin> Ben imported more data in cip-kernel-sec
09:01:19 <szlin> https://lists.cip-project.org/pipermail/cip-dev/2019-January/001735.html
09:01:20 <iwamatsu> Hi
09:01:34 <szlin> #action Daniel will start to work on v4.4.166-cip29-rt21 this friday
09:01:36 <sangorrin> hi
09:01:47 <szlin> iwamatsu: do you have any updates?
09:02:11 <bwh> Hi, sorry I'm late
09:02:19 <szlin> bwh: (wave
09:02:20 <iwamatsu> szlin: No, I am testing 4.19.y now.
09:03:20 <szlin> iwamatsu: thanks
09:03:44 <szlin> bwh: do you have any updates? I've mentioned the cip-kernel-sec update
09:04:18 <bwh> No, I haven't done much else as I was mostly on holiday
09:04:35 <szlin> Feel free to inform us if you need any collaboration work with cip-kernel-sec
09:04:49 <szlin> bwh: thanks.
09:05:03 <szlin> wagi: are you around?
09:05:32 <szlin> any other points?
09:05:51 <szlin> 3
09:05:52 <szlin> 2
09:05:53 <szlin> 1
09:06:01 <szlin> #topic kernel testing
09:06:34 <patersonc> We've been having some issues with the LAVA master. Restoring backups keeps failing. LF is currently investigating.
09:07:01 <patersonc> Not a lot else to report due to the holidays
09:08:13 <szlin> patersonc: thanks.
09:08:27 <szlin> iwamatsu: could you elaborate 4.19.y testing?
09:09:43 <iwamatsu> szlin: I am build, boot and LTP test on RZ board and QEMU.
09:09:57 <szlin> any issues founded or new test cases added with new feature in 4.19.y?
09:10:10 <iwamatsu> And I am updating cip-kernel-config to 4.19.
09:11:20 <szlin> iwamatsu: thanks.
09:11:21 <iwamatsu> There is no problem for now.
09:11:22 <iwamatsu> Please let me know if there is any valid document about test cases.
09:12:08 <patersonc> iwamatsu: I'm working to publish some test cases for the RZ board(s).
09:12:40 <patersonc> Mainly these will be designed to run in the LAVA env, but there is no reason not to run them directly on the board.
09:13:19 <sangorrin> patersonc: are you booting from NFS, NBDROOT or just from a ramdisk?
09:13:44 <sangorrin> oh probably its written in the guide i have to read ^^
09:13:52 <patersonc> At the moment either NFS or ramdisk
09:14:14 <sangorrin> i had problems running ltp on ramdisk
09:14:30 <sangorrin> i think NFS has problems too
09:14:36 <iwamatsu> patersonc: Do you have a document that I see about it?
09:14:39 <sangorrin> in AGL they use nbdroot, or sth like that
09:14:44 <patersonc> I haven't tried running LTS yet.
09:14:56 <patersonc> iwamatsu: Not yet. Will publish something when the scripts are ready.
09:15:39 <iwamatsu> patersonc: I see.
09:16:33 <szlin> patersonc: the docs and scripts will be uploaded to cip-project right?
09:17:01 <szlin> https://gitlab.com/cip-project/cip-testing <-
09:17:14 <patersonc> yes
09:17:37 <szlin> patersonc: great, we can start to share the test cases
09:17:49 <szlin> any other points?
09:17:54 <patersonc> o
09:18:03 <patersonc> Not from me
09:18:18 <szlin> 3
09:18:19 <szlin> 2
09:18:20 <szlin> 1
09:18:25 <szlin> #topic CIP Core
09:18:47 <sangorrin> Jan prepared an ISAR version of cip core, its on the playground
09:18:55 <sangorrin> we have to integrate it on gitlab
09:19:16 <sangorrin> we decided to use gitlab groups and use separate repositories for each implementation
09:19:33 <sangorrin> some instructions and manuals will need to be updated
09:19:42 <sangorrin> or just announce it on the list
09:20:04 <sangorrin> patersonc: are renesas manuals depending on the cip-core links?
09:20:46 <patersonc> sangorrin: I don't think so, no
09:20:54 <sangorrin> other than that, I am waiting for Siemens to fill my survesy ;_;
09:21:31 <sangorrin> ok, no more points from me
09:22:07 <szlin> sangorrin: IIRC, Wolfgang mentioned they will fill out the survey recently on Monday
09:23:09 <szlin> sangorrin:  BTW, helmut is looking for Kazuhiro. I think he wants to ask debian-cross stuff
09:23:19 <sangorrin> oh
09:23:28 <sangorrin> i will tell him, he is on my left
09:23:41 <szlin> helmut: are you around?
09:23:50 <szlin> any other points?
09:23:57 <szlin> 3
09:23:58 <szlin> 2
09:24:00 <szlin> 1
09:24:03 <szlin> #topic Software update
09:24:24 <sangorrin> i sent the survey
09:24:40 <sangorrin> i am thinking about using binary diffs and a A-B approach
09:25:03 <sangorrin> binary diffs: because iot devices usually run on sim cards that have a limit per month
09:25:12 <sangorrin> or similar restrictions
09:25:18 <szlin> indeed
09:25:34 <sangorrin> A-B approach: because it causes lower downtime
09:25:48 <sangorrin> we can install on partition b in the background and then just reboot
09:26:26 <sangorrin> ill finish a draft of the architecture soon and sent it to the dev list for feedback
09:26:44 <sangorrin> if you have any input please let me know anytime
09:27:16 <szlin> sangorrin: Do you think it necessary to use live patch?
09:27:43 <sangorrin> btw: there are two types of binary diffs: sector based and file-based. I think I want to use file-based but not sure the implications
09:28:05 <sangorrin> szlin: do you think that's stable?
09:28:19 <sangorrin> I prefer a more conservative approach
09:28:20 <szlin> sangorrin: of course not.
09:28:52 <sangorrin> oh and about the bootloader.. i think updating the bootloader can be complicated sometimes
09:29:11 <sangorrin> we could brick our devices ;_;
09:29:17 <szlin> perhaps A/B bootloader
09:29:40 <bwh> szlin: Live patching is stable maintenance on the hardest difficulty level :-)
09:30:16 <szlin> bwh: totally agree
09:30:17 <sangorrin> haha then I will avoid it :D
09:30:34 <patersonc> A/B bootloader is really dependant on the device
09:31:01 <patersonc> And where the flash can be accessed from.
09:31:20 <patersonc> Some newer devices don't allow access to the secure boot medium from the unsecure/Linux world
09:31:58 <sangorrin> patersonc: good point, we also need to think about such devices with trustzone
09:32:09 <szlin> and there're some security issues should be handled if we want to upload bootloder in OS.
09:32:26 <szlin> s/upload/update
09:32:55 <sangorrin> mmm lets start with something simple
09:33:08 <fujita[m]> sangorin: does A-B approach need double storage size?
09:33:19 <fujita[m]> embedded manufacturers do not want to add extra area
09:34:36 <szlin> fujita[m]: that's kind of trade-off
09:34:49 <sangorrin> fujita: yes, that's why i did the survey
09:35:10 <sangorrin> it seems that most members have enough space
09:35:45 <fujita[m]> Oh
09:35:59 <fujita[m]> I'll check again the survey seet
09:36:26 <fujita[m]> our customers always sais they want to reduce their storage
09:36:27 <sangorrin> but i think many devices cant afford it
09:36:41 <sangorrin> for example, routers or something with a small flash memory
09:36:46 <szlin> fujita[m]: I can understand some low-level devices equipped very little size of flash
09:37:15 <fujita[m]> exactly
09:37:16 <sangorrin> fujita: thanks for the feedback, another approach is use meta-updater which does not require a B partitions
09:37:40 <bwh> I think this is going to a little too much detail for this meeting...
09:37:43 <fujita[m]> thank you!
09:37:57 <sangorrin> yeah, lets move the discussion to the list
09:38:16 <szlin> any other points?
09:38:17 <sangorrin> nothing else from my side szlin
09:38:20 <szlin> 3
09:38:21 <szlin> 2
09:38:22 <szlin> 1
09:38:35 <szlin> #topic AOB
09:39:06 <szlin> any other business?
09:39:47 <szlin> 3
09:39:48 <szlin> 2
09:39:49 <szlin> 1
09:39:56 <szlin> #endmeeting