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
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
|
10:03 < geertu> Welcome to Today's Core Group Meeting!
10:03 < geertu> (and today we're celebrating https://en.wikipedia.org/wiki/Sinterklaas !)
10:04 [Users #periperi]
10:04 [ damm ] [ kbingham ] [ Marex ] [ mturquette] [ pinchartl]
10:04 [ geertu] [ kbingham[m]] [ marex-cloud] [ neg ] [ shimoda ]
10:04 [ jmondi] [ ldts ] [ morimoto ] [ patersonc ] [ wsa_ ]
10:04 -!- Irssi: #periperi: Total of 15 nicks [0 ops, 0 halfops, 0 voices, 15 normal]
10:04 < geertu> Agenda:
10:04 < geertu> 1. Status Updates
10:04 < geertu> 2. Discussion Topics
10:04 < pinchartl> (and https://en.wikipedia.org/wiki/Independence_Day_(Finland))
10:04 < geertu> pinchartl: But I read the islands are under attack again?
10:04 < geertu> Topic 1. Status updates
10:05 < geertu> A) What have we done since last time:
10:05 < geertu> Kaneko-san worked on R-ar E3 thermal and PMIC support.
10:05 < geertu> Marek work on U-Boot (SDHI, various fixes and cleanups), Linux (PCA953x,
10:05 < geertu> VC5 suspend/resume, RPC review), and ATF (DRAM config passing).
10:05 < geertu> Niklas submitted HS400 clock driver patches.
10:05 < geertu> Shimoda-san worked on IPMMU whitelisting and reported an R-Car E3's
10:05 < geertu> USB3_OVC pull-up issue.
10:05 < geertu> Geert worked on CPG/IPMMU/SYSC topology errata, SYSCEXTMASK support,
10:05 < geertu> sent CLK/PFC pull requests, and reviewed lots of patches.
10:05 < geertu> B) What we plan to do till next time:
10:05 < geertu> Kaneko-san will follow up on posted work.
10:05 < geertu> Marek plans to work on U-Boot (extracting patches from the Android BSP,
10:05 < geertu> USB gadget rework) and ATF (updates from Renesas + PCI suspend).
10:05 < geertu> Morimoto-san will ask the HW team about SYSCEXTMASK.
10:05 < geertu> Shimoda-san plans to continue to make an IPMMU driver's plan with
10:05 < geertu> Magnus-san.
10:05 < geertu> Ulrich plans to review patches.
10:05 < geertu> Geert will fix the pull-up only pin on R-Car E3, and plans to finalize
10:05 < geertu> instantiating generic devices from DT in QEMU.
10:07 < geertu> C) Problems we have currently:
10:07 < geertu> None.
10:07 < geertu> EOT
10:07 < geertu> Anything I missed?
10:08 < pinchartl> geertu: possibly Kieran working on periject ?
10:08 < pinchartl> (is that part of core ?)
10:10 < geertu> Is that under A or C? ;-)
10:10 < pinchartl> A
10:11 < kbingham> Good point - I guess that is part of core rather than MM :)
10:12 < geertu> It's part of meta
10:12 < kbingham> Now then - I have a question for periject - Who 'owns' the project. I have done a small task to help define the schema ... I am not assuming that I now own periject ... so I'm concerned that it is losing direction and management fast !
10:13 < pinchartl> morimoto: ^^
10:13 < pinchartl> kbingham: you may well be the owner now :-)
10:16 < pinchartl> seems there's a lack of volunteers ?
10:17 < morimoto> according to EthPad (http://muistio.tieke.fi/p/ppcedi18)
10:17 < morimoto> I can do is create git tree
10:19 < kbingham> Aha - we have earlier defined action points.
10:20 < kbingham> morimoto, could you let me know where to push the patches I have done so far then please?
10:21 < pinchartl> morimoto: about the next steps, would you like to continue development with Kieran ?
10:21 < morimoto> development what ?
10:22 < pinchartl> development of periject
10:22 < morimoto> kbingham: do you want to have new clean git repository ?
10:22 < morimoto> or contine
10:23 < morimoto> continue to use exist one ?
10:23 < morimoto> I can do both
10:25 < kbingham> I would have said continue to use the existing one - but there is quite a lot of code that would need to be ported to the new formats. So that makes me think a clean repository, as we import existing functionality on the new data format. What do you think ?
10:26 < morimoto> OK, no problem
10:26 < morimoto> I will remove existing periject, and create new clean one
10:27 < kbingham> morimoto, Don't 'remove' it completely :)
10:27 < pinchartl> or create a new branch in the existing repo ?
10:27 < morimoto> kbingham: I don't think we can reuse it
10:28 < morimoto> OK, not remove, but rename. periject -> periject-nack
10:31 < kbingham> Well either a new branch, in the same repo - or a fresh repo (whilst keeping the existing code in a separate) repo is fine by me. I think it's important to keep the existing code as reference for the design goals you had
10:31 < geertu> Yes, just rename the old master branch.
10:32 < morimoto> OK, move existing code to new branch, and create clean main branch !
10:34 < kbingham> Ok great. So I saw wsa_ had interest in participation from the EDI notes...
10:35 < kbingham> wsa_, Is there anything blocking you currently ?
10:35 < wsa_> what kind of "participation"?
10:35 < kbingham> wsa_, "Peri upport list # Wofram : migrate data # Wolfram"
10:36 < wsa_> the discussions i saw on the mailing list were YAML state details where I had no strong opinion on
10:36 < wsa_> ah, that
10:36 < wsa_> yes, I am still there for that
10:36 < kbingham> wsa_, Great ... is there anything blocking you from doing it :) (other than time.. :D)
10:37 < wsa_> yes, a notification like "everything you need for that is in place now" :)
10:37 < wsa_> like YAML scheme being ready, repo to work on
10:37 < wsa_> "ready enough" is good enough, too
10:38 < kbingham> Well then you can reply to the YAML schema saying 'Acked-by:' then :)
10:38 < kbingham> The YAML schema is 'close enough' as far as I can tell...
10:39 < kbingham> And it can still change where necessary ...
10:39 < wsa_> good to know
10:39 < kbingham> So having some real data put in and run with the validator to know if it works would certainly help.
10:39 < wsa_> okay
10:39 < wsa_> morimoto: can you announce when the updated repo is ready?
10:40 < morimoto> Yeah
10:40 < wsa_> on periperi-list?
10:40 < wsa_> great
10:40 < wsa_> thanks!
10:40 < morimoto> Maybe tomorrow
10:40 < morimoto> (Japanese time zone, of course :)
10:42 < kbingham> Ok - so we have some progress points ...
10:42 < kbingham> Shall we move on - and try to continue this in the ML?
10:42 < wsa_> ack
10:44 < pinchartl> should we proceed with multimedia then ?
10:44 < geertu> I think so, unless someone has another Core discussion topic?
10:45 < neg> I'm all cored out :-)
10:45 < pinchartl> :-)
10:46 < geertu> Thanks for joining, and have a nice continued day!
|
