summaryrefslogtreecommitdiff
path: root/wiki/Chat_log/20191128-core-chatlog
blob: 72d85920e1c0a5b0cac903feb478f1a5e7f9b188 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
09:08 < geertu> Welcome to today's Core Group Chat Meeting!
09:09 < geertu> Agenda:
09:09 < geertu> 1. Status Updates
09:09 < geertu> 2. Discussion Topics
09:09 < geertu> Topic 1. Status updates
09:09 < geertu> A) What have we done since last time:
09:09 < geertu> Marek worked on U-Boot (HS400), OpTee (Renesas patch stack cleanup,
09:09 < geertu> passing DT from ATF), OpenOCD (RPC-HF + SH-QSPI), and ATF (DDR).
09:09 < geertu> Morimoto-san started a private CI.
09:09 < geertu> Shimoda-san tried ARM SMMU-v3 on ARM Neoverse N1.
09:09 < geertu> Geert implemented new PFC errata, sent v3 of the GPIO
09:09 < geertu> Aggregator/Repeater, investigated ARM Cryptocell on R-Car Gen3, and
09:09 < geertu> updated periject/core for v5.4.
09:09 < geertu> Ulrich reviewed the GPIO Aggregator/Repeater patches.
09:10 < geertu> B) What we plan to do till next time:
09:10 < geertu> Marek plans to continue working on OpTee, and may resume Gen2 U-Boot.
09:10 < geertu> Morimoto-san plans to create and test his private CI.
09:10 < geertu> Shimoda-san plans to convert rcar-dmac and ipmmu DT bindings to
09:10 < geertu> json-schema, and will continue using SMMU-v3.
09:10 < geertu> Geert plans to add more R-Car M3-W+ support, post new sh-pfc runtime
09:10 < geertu> checks and related fixes, and resume DMAC sysfs work.
09:10 < geertu> C) Problems we have currently:
09:10 < geertu> Marek suffers from long and non-transparent ATF patch review, and is
09:10 < geertu> considering alternatives use U-Boot SPL.
09:10 < geertu> Ulrich is learning to cope with Philippinean environmental and
09:10 < geertu> infrastructural quirks.
09:11 < geertu> ---EOT---
09:11 < geertu> s/use/using/
09:11 < geertu> Anything I missed?
09:13 < geertu> Topic 2. Discussion Topics
09:13 < geertu> Anything to discuss?
09:14 < shimoda> i don't have any topic
09:14 < kbingham> geertu, Will you aim to get your periject helper scripts/hooks into periject? Or are they stalled on the git-add issue?
09:14 < geertu> kbingham: They're already on master
09:14 < kbingham> Oh! I missed that :)
09:14 < kbingham> excellent.
09:15 < kbingham> Next question - do we have a script for creating a new task yet? Or is it just a manual copy/paste
09:15 < geertu> I think the gain is bigger than the issues
09:15 < kbingham> geertu, I agree, that's why I was hoping it would go to master already :) and now I learn it is :)
09:16 < geertu> Still manual copy/paste, AFAIK (like for anything yaml/python/<insert fancy new language here>... related)
09:18 < geertu> Nothing else to discuss?
09:18 < wsa> not from me
09:18 < geertu> Then I'm happy to thank you for joining, and pass the mic to whoever wants to take it
09:19 < kbingham> I guess that's me then
09:19 < morimoto> geertu: I have 1
09:20 < morimoto> periject now has per-commit, but you didn't use "git merge" ?
09:20 < morimoto> Because commit ID not much to gitlab/pre-commit branch, I think
09:21 < geertu> morimoto: No I didn't, as your branch contained an older version
09:21 < morimoto> OK, I see.
09:21 < morimoto> Then, we can remove gitlab/pre-commit ?
09:22 < geertu> morimoto: Sorry for confusing you
09:22 < morimoto> no problem.
09:22 < geertu> morimoto: I think so
09:22 < morimoto> OK, will do
09:23 < morimoto> now, he is gone
09:23 < kbingham> Well if we're finishing off some discussions - geerty would you like me to try to set up the patchwork bot and see what we can do to manage that ourselves?
09:24 < kbingham> (gerrty must be my new nickname for geertu :D)
09:24 < morimoto> :D
09:24 < geertu> kbingham: Is it easy to set up your own instance?
09:25 < geertu> BTW, it looks like the bot didn't detect all new commits in renesas-devel that I had missed to mark accepted in patchwork
09:25 < kbingham> geertu, I don't yet know - that's what we'll need to find out. I looked breiefly, so I think it's essentialyl jsut a script that can run on a cron job, and just needs configuring to map to which git repos it will parse, and handle auth-tokens for patchwork.
09:26 < kbingham> Having our own instance will help us debug issues like that too I guess.
09:26 < geertu> yep
09:27 < kbingham> Ok - I'll try to set it up, and I can document what is needed to run it incase we want to set it up somewhere specifically (rather than my dev box/always on pc)
09:27 < geertu> ok, thx!
09:28 < kbingham> geertu, Ready for a mic-drop? :-D
09:29 < geertu> kbingham: Sure, I thought it was already dropped