From 55e3b2f45880faaf06f3c660ca9e8a6d9aa14bce Mon Sep 17 00:00:00 2001 From: Kuninori Morimoto Date: Mon, 9 Dec 2019 15:29:52 +0900 Subject: wiki: Porting wiki: Porting Chat Log Signed-off-by: Kuninori Morimoto --- wiki/Chat_log/20170111-mm-chatlog | 274 ++++++++++++++++++++++++++++++++++++++ 1 file changed, 274 insertions(+) create mode 100644 wiki/Chat_log/20170111-mm-chatlog (limited to 'wiki/Chat_log/20170111-mm-chatlog') diff --git a/wiki/Chat_log/20170111-mm-chatlog b/wiki/Chat_log/20170111-mm-chatlog new file mode 100644 index 0000000..3088275 --- /dev/null +++ b/wiki/Chat_log/20170111-mm-chatlog @@ -0,0 +1,274 @@ +Multimedia-chat-meeting-2017-01-11 + + good morning [16:58] + morning + morning + morning [16:59] + Kieran seems to have left the channel during the night. perhaps as + a consequence of too much birthday partying :-) + any chance Magnus would join today ? [17:00] + I have no idea about him :) [17:01] + I think I'll stop expecting him to join :-) + :) [17:02] + let's start then. I expect the meeting to be short today +*** kbingham (~kbingham@core.do.nakedgeek.co.uk) has joined channel #periperi + hi Kieran ! + we were about to start + Topic 1. Status check for the multimedia tasks + sorry for being late - my IRC bouncer crashed :( + Topic 2. Additional tasks for Q1 2017 + Topic 3. FOSDEM [17:03] + Topic 4. Next meeting + anything else for the agenda ? + no worries + ELC meeting plan I want to know + ok, FOSDEM & ELC then + let's get started with Topic 1. Status check for the multimedia + tasks [17:05] + Kieran, will you do the honours ? + pinchartl: I thought you might say that :D + So - to start, since last meeting: + - Holidays [17:06] + - Had my birthday + - Suspend resume patches reposted + - Rebased all my topic branches + And I'm currently working on the image partitioning overlap topic + So B) Plan until next meeting: [17:07] + - At two weeks away, I hope I will have made most of the headway + to getting the image partitioning task complete, possibly mixed in + with some of the work on the vsp-test improvements - but with no + confirmation from renesas, I guess those topics could stop at any + time. [17:08] + leaving C) + - current work still pending contract from Renesas [17:09] + - Experiencing some issues on vsp-unit-test-0003.sh + : EOT : Sorry - Would normally prepare the text for this in + advance - but finished early due to my birthday yesterday :D + [17:10] + thank you [17:11] + pinchartl: Is there anything you'd like me to do on the pending + topic branches? [17:12] + could you push them to your public tree ? I'll review the patches + you posted + Ok - I'll push my rebased updates. + Should they be re-emailed? [17:13] + not if it's just a rebase, I'll review them first [17:14] + if they have otherwise changed, please resend them + Ok. [17:15] + next in alphabetical order, me + Since last meeting: + - Holidays [17:16] + - New version of the Gen3 HDMI output patches (split in topic + branches) + - Started experimenting with fences in the DU driver + - DRM/KMS community discussions to get the LVDS mode select, LVDS + encoder and HDMI output merged (or at least closer to be merged) + - Helped Jinzai to test HDMI output + For the next two weeks: + - Pending VSP patch review + - Continue advancing Gen3 HDMI output towards merging + - V4L2 & media controller race conditions meeting in Oslo with + Hans Verkuil & Sakari Ailus + (that's this Friday) + Issues and blockers: + - No additional task yet for 2017/Q1 [17:17] + and I will be on holidays from the 20th to the 28th + pinchartl: Of january? [17:18] + yes + pinchartl: Ok :D + skiing in the French Alps + I'll have e-mail access + pinchartl: will you also discusss Media Device Allocator API in Oslo + (that is if it's to be pushed or dropped)? [17:19] + morimoto: that's a topic we've discussed already, but I had to + hand-hold Jinzai because they seemed not to be able to select the + HDMI driver in the kernel config by themselves... + neg: not as such. we'll discuss what needs to be fixed in order to + get that API merged + I want to fix the current code base before building anything new + on top of it + ok thanks for the update [17:20] + next, Morimoto-san [17:21] + OK + A) - Enjoyed New Year + - I posted ALSA SoC framework fixup patches + - Helped BSP team about sound [17:22] + B) I will rebase my HDMI sound on pinchartl's latest branch + - I will book ELC hotel / flight etc + C) nothing + --EOT-- + thank you + neg: your turn [17:23] + A) Noting (rebasaed all my topic branches on v4.10-rc1 and test them) + [17:24] + B) Fix review comments and repost CSI-2 and breakout fixup patches from + VIN Gen3 series and repost as seperat series (needad as to not block + Wolframs work) and pray that series is reviewd/picked up :-) + C) None + EOT + is it OK with you if I start by reviewing the CSI-2 driver, + followed by the VIN driver ? [17:25] + yes, but maybe we can fast track the break out fixup VIN patches as to + not block Wolfram? [17:26] + those patches will be small and only deal with Gen2 concepts + oh yes sure [17:27] + thanks + I meant CSI-2 before VIN Gen3, but obviously other VIN patches can + go in first + would you prefer I try to get CIS-2 merged before Gen3 VIN patches? + s/CIS/CSI/ [17:28] + it might be easier + but it also makes sense to merge everything anyway + so I have no big preference at the moment + ok then I will stop trying to hold CSI-2 back to be merged after VIN + Gen3 and which ever is picked up first is OK + next, uli___ [17:29] + a) + - vacation + - investigated what it takes to get gpu going with binary blobs on + gen3 [17:30] + b) + - trying not to succumb to the infection that has incapacitated my + wife for a week... + c) + - add. tasks not finalized yet + that's it + thank you [17:31] + before going to the next topic + I'd like to thank Morimoto-san for sending his report over e-mail + given that we're just out of the winter holidays, without much to + report, I'll ignore the fact that nobody else has + but please remember to post a summary before next meeting [17:32] + Topic 2. Additional tasks for 2017/Q1 + as you all know, we have no additional tasks finalized for 2017/Q1 + there were discussions at the end of last year + and before a conclusion could be reached the winter holidays + started and Magnus disappeared [17:33] + I haven't heard anything from him since then + which starts worrying me + Magnus disappeared... + morimoto: do you have any information ? + I will meet him tomorrow. + I will kick him [17:34] + thank you + for you guys :) + I've already started working on tasks that will likely be selected + for 2017/Q1 + wear heavy boots :D + so has Kieran, and from what I've heard today from Ulrich, he did + as well + but there's no contract signed yet + so this is really a gesture of good faith + not a situation that I want to experience again in the future + it shows that the task negotiation process doesn't work [17:35] + it's the second time we're late, albeit last time the delay was + shorter + so I will request to move back to a single batch per quarter + i think i would prefer that as well [17:37] + as there seems to be no comment about this, + (oops, except for that comment :-)) + Topic 3. FOSDEM & ELC + we have reserved time for a multimedia meeting on the Thursday + before FOSDEM, but given the lack of contracts, and thus the lack + of topics to discuss, I don't plan to organize such a meeting + [17:38] + I will be in Brussels the whole week before the FOSDEM, so if any + of you happens to be there and wants to schedule an ad-hoc + meeting, I'll be available [17:39] + I believe Kieran will be there from Wednesday as well [17:40] + ACK. + Was not Q2 contract proposals a topic for that meeting? [17:41] + neg: it was, but Magnus won't be there, and we don't have Q1 + contracts yet + Ahh I though Magnus would be there, my mistake [17:42] + when will everybody be available in Brussels ? Kieran, you'll be + there from Feb the 1st to the 6th, right ? how about Niklas and + Ulrich ? + i won't be there. i've fallen ill every single time i have attended + fosdem, and this time i just won't go. no kidding at all. + [17:43] + come back when it's in june + I was planing to arrive on Wed evening to be aviable for Multimedia + meeting, but if that is off I think I move my arrival date to Thu + evening + ok [17:44] + Morimoto-san wanted to know more about our ELC plans [17:45] + Yes. Do we have MM meeting ? + and yes also leving in the morning the 6th. But if there are plans or + suspicions of plans for meetings please let me know and I can adjust my + schedule + nothing has currently been scheduled, as everything regarding + multimedia planning has been on hold since end of December and the + lack of contracts [17:46] + officially, right now there's no multimedia team anymore + so before scheduling a meeting, we should sort that out + pinchartl: scheduling a meeting = ELC meeting ? or FOSDEM meeting ? + [17:47] + both + OK + and MagPeri is the Key guys ? + he seems to be + OK [17:48] + morimoto: which dates do you plan to be at ELC? I think I change my mind + and intend to go if I can find a good flight :-) + at this point, maybe 20th - 24th + so that would leave the 20th and 24th for possible meeting days ? + [17:49] + that the reason why I'm asking about meeting :) [17:50] + If we have meeting, the plan will be changed + I will arrive on the 18th and leave on the 25th + the 19th (Sunday), 20th and 24th are currently free + but I expect a V4L2 meeting to be scheduled, likely on the 20th + pinchartl: Do you think "media-layer" will be discussed on V4L2 + meeting ? [17:52] + what do you mean by media-layer ? + V4L2 + ALSA need media-layer for OF-graph ? + probably not [17:53] + it will likely be focussed on core media controller problems + OK, in order to be able to book flights maybe we can aim to keep the + 24th open for a possible meeting if the contract situation is sorted + out? My understanding is that nither Geert nor Wolfram will attend ELC + so MM is the only possible meeting at that time? [17:54] + the 24th would be nice + if you can be there on both the 20th and the 24th it would give us + some flexibility + and you could join the V4L2 meeting when it will be scheduled :-) + [17:55] + cool then I try to book flight to arrive 19 and leave 25 + cool. I will re-schedule for ELC + yes if possible I would like to attend the V4L2 meeting, without + periperi scheduling collision :-) + last topic [17:56] + Topic 4. Next meeting + I will be on holidays in two weeks from now + so we can schedule a meeting in a week + or in three weeks + one week is likely too short as we have no contract at the moment + 3 weeks seems better + but that might collide with Kieran's travel plans for the FOSDEM + [17:57] + (which would give Kieran a good excuse to not attend the meeting + :-)) + would wednesday 2017-02-01 at 08:00 GMT / 09:00 CET / 10:00 EET / + 17:00 JST work ? + it does cut it close ... but its actually probably just about + do-able ... as long as I book my taxi to pick me up at the end of + the meeting :D [17:58] + :-) + So yes, fine by me. + if you have to skip it's not an issue + does it work for everybody else ? + ok for me + OK for me [17:59] + OK for me too + perfect, it's agreed then + I propose adjourning this meeting [18:00] + does anyone second ? + seconded and running downstairs to make tea :D + :-) + meeting adjourned + thank you everybody for attending + have a nice day/evening [18:01] + Thanks + see you + thanks all -- cgit v1.2.3