diff options
Diffstat (limited to 'wiki/Chat_log/20180712-mm-chatlog')
| -rw-r--r-- | wiki/Chat_log/20180712-mm-chatlog | 414 |
1 files changed, 414 insertions, 0 deletions
diff --git a/wiki/Chat_log/20180712-mm-chatlog b/wiki/Chat_log/20180712-mm-chatlog new file mode 100644 index 0000000..67c5e28 --- /dev/null +++ b/wiki/Chat_log/20180712-mm-chatlog @@ -0,0 +1,414 @@ +Multimedia-chat-meeting-2018-07-12 + +10:25 < pinchartl> welcome to the multimedia meeting +10:25 < pinchartl> Topic 1. Status Check for the Multimedia Tasks +10:25 < pinchartl> * Jacopo +10:25 < pinchartl> Since last meeting: +10:25 < pinchartl> - MT9V111 and GR-Peach audiocamera shield +10:25 < pinchartl> [PATCH 0/2] media: i2c: mt9v111 sensor driver +10:25 < pinchartl> [PATCH] ARM: dts: gr-peach: Add GR-Peach audiocamerashield support +10:25 < pinchartl> - Respin of iommu patches that got lost +10:25 < pinchartl> [RESEND 0/6] iommu: ipmmu-vmsa: Add more Gen3 SoCs support +10:25 < pinchartl> - Got parallel input support for VIN merged +10:25 < pinchartl> - New iteration of VIN endpoint properties refreshing +10:25 < pinchartl> - Attend OSS-J and meet periperi people in Tokyo +10:25 < pinchartl> - Complex Camera Workshop in Tokyo +10:25 < pinchartl> Until next meeting: TBD +10:25 < pinchartl> Issues and Blockers: None +10:25 < pinchartl> jmondi: TBD stands for To Be Decided +10:25 < pinchartl> you provided a long list of items you could work on +10:26 < pinchartl> I propose discussing them after the status update +10:26 < pinchartl> any comment ? +10:26 < kbingham> pinchartl, (I believe Jacopo is on a plane) +10:26 < pinchartl> oh, OK +10:27 < pinchartl> indeed, he wrote that he wouldn't be able to attend in his e-mail +10:27 < pinchartl> * Kieran +10:27 < pinchartl> Since last meeting: +10:27 < pinchartl> - Japan OSS/ALS +10:27 < pinchartl> - Gave GMSL Talk +10:27 < pinchartl> https://www.slideshare.net/KieranBingham/gmsl-in-linux +10:27 < pinchartl> - Complex Camera Workshop in Tokyo +10:27 < pinchartl> - ATF build and update for qemu-kvm +10:27 < pinchartl> - Proposed GMSL talk for ELCE +10:27 < pinchartl> - Proposed Fault Tolerant V4L2 for ELCE +10:27 < pinchartl> Until next meeting: +10:27 < pinchartl> - DU/Interlaced review actions +10:27 < pinchartl> - Submit GMSL for Renesas-drivers +10:27 < pinchartl> Issues and blockers: None +10:27 < pinchartl> kbingham: any comment ? +10:27 < kbingham> Aha - you've added the complex camera workshop :) thanks :) +10:28 < kbingham> That looks good for me +10:28 < pinchartl> you're welcome +10:29 < pinchartl> * Laurent +10:29 < pinchartl> Since last meeting: +10:29 < pinchartl> - Display virtualization +10:29 < pinchartl> - Japan OSS/ALS +10:29 < pinchartl> - Gave talk about display virtualization at ALS +10:29 < pinchartl> https://schd.ws/hosted_files/ossalsjp18/27/20180622-ossj.pdf +10:29 < pinchartl> - Complex Camera Workshop in Tokyo +10:29 < pinchartl> - Patch review +10:29 < pinchartl> Until next meeting: +10:29 < pinchartl> - Patch review +10:29 < pinchartl> - Additional tasks preparation +10:29 < pinchartl> - Revive the GMSL efforts +10:29 < pinchartl> - Part-time vacation +10:29 < pinchartl> Issues and blockers: +10:29 < pinchartl> - No additional tasks scheduled yet for Q3. +10:29 < pinchartl> any comment from anyone? +10:29 < pinchartl> * Magnus: +10:29 < pinchartl> Since last meeting: None +10:29 < pinchartl> Until next meeting: None +10:29 < pinchartl> Issues and blockers: None +10:29 < pinchartl> * Morimoto-san +10:29 < pinchartl> Since last meeting: None +10:29 < pinchartl> Until next meeting: None +10:29 < pinchartl> Issues and Blockers: None +10:30 < pinchartl> dammsan: morimoto: any comment ? +10:30 < morimoto> no +10:31 < dammsan> ditto +10:32 < pinchartl> * Niklas +10:32 < pinchartl> Since last meeting: +10:32 < pinchartl> - Summer VIN cleaning +10:32 < pinchartl> Dug out and prepared batch test of patches held back until VIN was accepted. Will post in before next meeting. Mostly related to VIN SEQ_TB/BT support, additional formats and fixes to the ADV7180. +10:32 < pinchartl> - Working on V4L subdev STD handling for MC-centric devices. +10:32 < pinchartl> - Complex Camera Workshop in Tokyo. +10:32 < pinchartl> Until next meeting: +10:32 < pinchartl> - Keep testing and getting the held back patches out +10:32 < pinchartl> - Try to work with Mauro and have him accept the subdev STD patch +10:32 < pinchartl> - If GMSL efforts are stepped up by the team keep phusing for the VC patch set +10:32 < pinchartl> Issues and blockers: +10:32 < pinchartl> - Mauro refuse to understand the MC-centric use-cases +10:32 < pinchartl> Please MM members read and respond to the thread '[PATCH v2 0/2] v4l: Add support for STD ioctls on subdev nodes'. We need this on Gen3 to be able to control the video standard of CVBS capture. +10:32 < pinchartl> neg: any comment ? +10:33 < neg> pinchartl: can you please step-up as MC maintainer ? ;-) +10:33 < neg> other than thet no comment +10:33 < pinchartl> neg: I would if Mauro let me. feel free to propose that :-) +10:34 < pinchartl> * Ulrich +10:34 < pinchartl> Since last meeting: +10:34 < pinchartl> - Sent revised D3 DU support +10:34 < pinchartl> Until next meeting: None +10:34 < pinchartl> Issues and blockers: None +10:34 < pinchartl> uli___: any comment ? +10:34 < uli___> one thing about the d3 du +10:34 < uli___> it does not support interlacing +10:35 < uli___> no difference in the register layouts etc, so as long as it is not used +10:35 < uli___> we're fine +10:35 < uli___> but how can i make sure of that? +10:35 < kbingham> uli___, As interlacing is not yet supported, I don't think it's an issue for you +10:35 < uli___> that's good to hear :) +10:35 < kbingham> But I will consider that on my DU/Interlacig series +10:35 < uli___> nothing else from me +10:35 < kbingham> (I plan to work through laurent's review comments on that this week) +10:36 < pinchartl> thank you +10:37 < pinchartl> anything to add before moving to the next topic (additional tasks) ? +10:38 < neg> nothing from me +10:39 < kbingham> nor me +10:39 < pinchartl> Topic 2. Additional Multimedia Tasks for Q3 +10:39 < pinchartl> two additional tasks have been accepted for Q3 +10:39 < pinchartl> - R-Car Gen3 display output limitations +10:40 < pinchartl> - D3/E3 LVDS PLL support +10:40 < pinchartl> we now need to split them between all of us, and schedule them +10:41 < pinchartl> Renesas has requested us to reduce the budget +10:41 < pinchartl> by a 15, 20 or 25% amount depending on the phase of the moon +10:42 < pinchartl> the latest information I've been given is that we should prepare for a 15-20% reduction +10:42 < kbingham> I'm ok reducing some budget at the moment. +10:42 < uli___> is that a grand total, or for add. tasks only? +10:42 < dammsan> former +10:42 < pinchartl> grant total, but it seems OK to apply the reduction to additional tasks only +10:43 < pinchartl> that is, if you have 30 base + 30 additional, a 15% reduction is 9 days +10:43 < pinchartl> so you would end up with 30 base + 21 additional +10:43 < uli___> ok +10:44 < horms> I am happy to donate time other than that required for LTSI +10:44 < pinchartl> here are the current projections +10:44 < pinchartl> Member | Base + Add. | 15% | 20% | 25% +10:44 < pinchartl> -------------------------------------------------------------------- +10:44 < pinchartl> Jacopo | 33 + 15 | - 7.2 -> 5 | - 9.6 -> 10 | - 12 -> 10 +10:44 < pinchartl> Kieran | 20 + 25 | - 6.75 -> 5 | - 9 -> 10 | - 11.25 -> 10 +10:44 < pinchartl> Laurent | 35 + 25 | - 9 -> 10 | - 12 -> 10 | - 15 -> 15 +10:44 < pinchartl> Niklas | 20 + 10 | - 4.5 -> 5 | - 6 -> 5 | - 7.5 -> 10 +10:44 < pinchartl> Ulrich | 35 + 25 | - 9 -> 10 | - 12 -> 10 | - 15 -> 15 +10:45 < pinchartl> with the number of days rounded to the nearest multiple of 5 +10:45 < geertu> ;-) +10:46 < geertu> (about rounding) +10:46 < pinchartl> I know :-) +10:46 < pinchartl> if we prepare for 20%, we will be left with the following number of additional task days +10:46 < pinchartl> Jacopo: 5 +10:46 < pinchartl> Kieran: 15 +10:46 < pinchartl> Laurent: 15 +10:46 < pinchartl> Niklas: 5 +10:46 < pinchartl> Ulrich: 15 +10:47 < pinchartl> total: 55 +10:48 < pinchartl> who has or plan to have additional tasks scheduled for the core and I/O groups ? +10:48 < neg> My only plan is to have the 5 days I have for additional to happen in the second batch of Q3 if possible +10:49 < pinchartl> s/plan/plans/ +10:49 < pinchartl> I plan to ask for scheduling everything for the second batch (unless someone insists on having to deliver earlier) +10:49 < dammsan> seems good to me +10:50 < pinchartl> uli___: do you have additional tasks planned for Q3 for core ? I think I recall memory autodetection ? +10:50 < uli___> i intend to do that, but no talks about making that an add. task yet +10:51 < kbingham> pinchartl, for me, if there is not enough work to go around in MM, I could go back to looking at virt-topics with core ... but I'd want to make sure I've got a good understanding of the task requirements for that ;) +10:54 < pinchartl> sorry, I lost my internet connection +10:54 < pinchartl> kbingham: I think we'll have enough work on the multimedia side :-) +10:54 < pinchartl> uli___: geertu: how much time do you think will be needed by that ? +10:56 < uli___> 10 days, if i can get an atf upstreaming waiver (that's unknown territory for me) +10:56 < pinchartl> that would leave 5 days for multimedia then +10:57 < pinchartl> I should get an E3 board which has the sasme LVDS PLL +10:57 < pinchartl> so we could share the work between you and me +10:58 < uli___> do you have an idea how to split that? +10:58 < pinchartl> an easy way would be prototype + upstreaming +10:58 < pinchartl> 5 days fits a prototype better than an upstreaming task +10:58 < uli___> i would say +10:59 < pinchartl> do you think that makes sense, or would you prefer a different arrangement ? +10:59 < uli___> i think that could work +11:00 < pinchartl> would you be able to schedule that for mid-August ? otherwise I'd have trouble finishing it for mid-September, as my work would depend on yours +11:00 < uli___> would be ok +11:01 < pinchartl> thank you. I'll write task proposals then +11:01 < uli___> ok, thanks +11:01 < pinchartl> so that covers us +11:01 < pinchartl> for Jacopo, Kieran and Niklas, there are 25 days in total +11:02 < pinchartl> I think that can be covered by the "R-Car Gen3 display output limitations" task +11:02 < pinchartl> any opinion ? +11:03 < neg> I'm not sure what's included by the output limitation task +11:03 < kbingham> Are we thus going to just submit that as a task, and each work on it ? +11:04 < pinchartl> kbingham: more or less, but as we need to split the work anyway, I think we should include that information in the task description +11:04 < pinchartl> neg: +11:04 < pinchartl> - R-Car Gen3 display output limitations +11:04 < pinchartl> Display output on Gen3 platforms are subject to various resolution, pixel +11:04 < pinchartl> fomat and clock rate limitations depending on the SoC (or rather on the VSP, +11:04 < pinchartl> DU and internal encoders) and board. Few of these limitations are properly +11:04 < pinchartl> taken into account, which leads to random display output stability issues. For +11:04 < pinchartl> instance, 4k output isn't working properly, and parallel output (for VGA) +11:04 < pinchartl> pixel frequency limitations are not taken into account. +11:04 < pinchartl> I would like to propose an additional task to fix all this. The goal is to go +11:04 < pinchartl> through the documentation for each SoC and board we support, as well as +11:04 < pinchartl> through the contents of the BSP, to identify limitations for each platform and +11:04 < pinchartl> make sure they are all taken into account in the appropriate drivers. The work +11:04 < pinchartl> isn't extremely difficult, but in some cases we will need to implement +11:04 < pinchartl> currently unimplemented operations (in particular in the DU driver to take +11:04 < pinchartl> pixel rate limits into account), or possibly to even extend frameworks +11:04 < pinchartl> (although I don't think that should be needed, but I haven't double-checked). +11:06 < neg> pinchartl: thanks +11:06 < pinchartl> another option would be to find a 5 days additional task related to VIN for you, and have Jacopo and Kieran handle the display side. there's plenty of work in VIN, that's not an issue, but I don't know if that could be accepted as an additional task +11:06 < pinchartl> dammsan: any comment ? +11:06 < dammsan> fine with me +11:06 < neg> Only VIN task I see which is fit for add task is a UDS scaler prototype +11:07 < pinchartl> dammsan: which option is fine with you ? :-) everybody working on display, or proposing a VIN additional task ? +11:07 < pinchartl> neg: I'd like to move forward with the scaler too +11:07 < pinchartl> I think it's important to prototype that in the not too distant future +11:07 < dammsan> i'm ok either way, niklas working on vin makes sense to me +11:07 < pinchartl> in order to plan for proper upstreaming +11:07 < pinchartl> dammsan: thanks. it makes sense to me too +11:08 < pinchartl> so should we go for a VIN scaler prototype task ? +11:08 < neg> I would be fine working on the scaler +11:09 < pinchartl> I'll propose that then, thanks +11:09 < pinchartl> and split the DU work between Kieran and Jacopo +11:09 < neg> thank you +11:09 < pinchartl> (who can't disagree as he's not here :-)) +11:09 < kbingham> Well I'll handle the 4k work as I have already bought the 4K TV :) +11:10 < pinchartl> :-) +11:10 < pinchartl> we'll decide how to split the work when Jacopo will be available +11:10 < kbingham> What's the VGA issue? +11:11 < neg> kbingham: that's selfish, I thin Jacopo who do not yet own a 4k tv should handle that ;-) +11:11 < kbingham> (agreed, we can take further planning offline until Jacopo is here) +11:11 < pinchartl> various SoCs have different maximum pixel clock limits, this affects VGA and should be taken into account when reporting supported modes to userspace +11:11 < kbingham> neg, Well he could certainly test any patches if he needs a reason to expense a 4kTV :) +11:12 < neg> kbingham: :-) +11:12 < kbingham> pinchartl, Aha - ok I think I understand yes ;) +11:14 < pinchartl> so I think this covers additional tasks for Q3 +11:14 < pinchartl> any question or comment ? +11:14 < morimoto> quick question from me +11:14 < morimoto> wsa_: pinchartl: About tool, are you OK v2 style ? It is assuming you uses your own editor. I don't want to re-work script many times. It still doesn't have bsp upport and report features +11:14 < pinchartl> morimoto: is that an additional task ? :-) +11:14 < morimoto> but you can see its behavior +11:14 < morimoto> hehe :) +11:14 < morimoto> Just question +11:15 < pinchartl> I'll reply to your e-mails today or tomorrow. I'm sorry for the delay, I've been traveling a lot after our meeting in Tokyo +11:15 < morimoto> OK +11:15 < morimoto> but, your "I will do it in next week" never worked for me :) +11:15 < morimoto> +1. do you think it will be useful if new tool can handle base/additional task days ? +11:15 < wsa_> morimoto: I wanted to have a look later today +11:15 < pinchartl> I know, that's why I said today or tomorrow, not next week :-) +11:15 < morimoto> wsa_: thanks +11:15 < pinchartl> I haven't had time to read the latest mails in the thread yet +11:15 < morimoto> pinchartl: OK, thanks +11:16 < morimoto> OK, no problem. +11:16 < morimoto> I'm looking forward to see you respoce +11:16 < morimoto> thanks, thats all from me +11:16 < pinchartl> thank you +11:16 < pinchartl> this leads us to +11:16 < pinchartl> Topic 3. Q3 Development Schedule +11:17 < pinchartl> Kieran and Jacopo have proposed tasks in their biweekly e-mail reports +11:17 < pinchartl> for Kieran +11:17 < pinchartl> s/for/from/ +11:17 < pinchartl> * Media +11:17 < pinchartl> - GMSL prototype continuation +11:17 < pinchartl> - RDACM21 +11:17 < pinchartl> - Fault redundant V4L2 +11:17 < pinchartl> - DU +11:17 < pinchartl> - 4K support +11:17 < pinchartl> - VSP1 +11:17 < pinchartl> - YUV420M formats support +11:17 < pinchartl> the DU and VSP1 work is included in additional tasks +11:18 * morimoto need to go back to my home +11:18 < pinchartl> morimoto: thank you for attending +11:18 < morimoto> thanks, bye +11:18 < pinchartl> from Jacopo +11:18 < pinchartl> - GMSL +11:18 < pinchartl> - Is there interest in RDACM21 which has a different image sensor? There's +11:18 < pinchartl> plenty of work there. +11:18 < pinchartl> - The kingfisher boards has GMSL and TI concurrent solution for remote +11:18 < pinchartl> camera/displays. Having one would be sweet but it is hardly available and +11:18 < pinchartl> expensive. +11:18 < pinchartl> - Driver sent upstream but not yet received feedback +11:19 < pinchartl> - From the periperi upport list +11:19 < pinchartl> (All commit reference from https://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas-bsp.git/) +11:19 < pinchartl> - EBISU needs VIN and display output support +11:19 < pinchartl> commit/?id=5ee0043347b63d40cf088740fb07285d4178f82c +11:19 < pinchartl> commit/?id=51b12d070f3ddc9bbf7232028e5d1571c95eb473 +11:19 < pinchartl> - M3-W ULCB fixes: Z clock support, CPU idle +11:19 < pinchartl> commit/?id=9c21d6d3ebacf11cb241e086902a2ecfe6e779d6 +11:19 < pinchartl> commit/?id=22fa2b4b9dd0f78e02f8d890a9cf98fda8757ad4 +11:19 < pinchartl> commit/?id=fe16e454b991dbd280a95ebe48aa595915d4610b +11:19 < pinchartl> - There is an LVDS panel driver, which I'm not sure in which board/expansion +11:19 < pinchartl> is. Does periperi Japan knows what's that for? +11:19 < pinchartl> commit/?id=4e3cc360666b5c8cc52c47b5eb7b16a8ef80bd40 +11:19 < pinchartl> - VIN: support for ARGB and NV12 +11:19 < pinchartl> commit/?id=9fb2f061c046d530adacd73946d00febf6027a81 +11:19 < pinchartl> commit/?id=1196884f275fb0f1a1cec04ce56a92453798292b +11:19 < pinchartl> - VIN and CSI-2 power management: +11:19 < pinchartl> commit/?id=1b1b3b1445fd5479cf0d8a43d69690dec5ecd854 +11:19 < pinchartl> - CEU related work +11:19 < pinchartl> - CEU interlaced support (need an analogue source connected to remote Migo-R) +11:19 < pinchartl> - Fabrizio Castro and Chris Patterson sent patches to add support for BT656 on OV7725, found on iWave platform. The board is expensive (1000€) so buying it is not an option. The patches can still be upstreamed if Chris and Fabrizio can test the rebased version. +11:19 < pinchartl> - MT9T112: this chip is integrated in some old SH boards with CEU. Jacopo has a camera module that can be connected to a Peach to board test the driver. He hasn't been able to capture any image yet. +11:19 < pinchartl> - RZ/N pincontrol has been sent upstream and then abandoned. Is there interest in those chips ? +11:19 < pinchartl> I'm not sure why Z clock support and CPU idle is there, it's not multimedia +11:20 < pinchartl> so I'll remove that +11:20 < kbingham> I would like to start some pressure on the fault redundant V4L2 topic, so if it's ok - I'll try to formulate a RFC patch / and or email thread to bring the topic up with Hans as base work. +11:20 < pinchartl> I think that make sense +11:21 < pinchartl> CEU is more or less unfunded +11:21 < pinchartl> Jacopo seems to like it though +11:21 < pinchartl> so if he can find a bit of time to spend on it, I have no issue +11:21 < pinchartl> but I'd like to concentrate on two topics for the base time +11:21 < pinchartl> - backlog reduction +11:21 < pinchartl> this includes both our own backlog and the BSP patches +11:21 < pinchartl> - GMSL +11:22 < pinchartl> fault-tolerant V4L2 is part of that +11:22 < pinchartl> any comment ? +11:22 < geertu> FWIW, Armadillo also has an MT9T112. So if it works on Peach, I can test CEU on Armadillo. +11:22 < geertu> s/CEU/the new CEU/ +11:22 < neg> I think the two focus areas for base are good +11:23 < kbingham> Yes, I think having directed focus is definitely a postive +11:23 < pinchartl> geertu: thanks for the offer +11:23 < neg> kbingham: as a first step now that parallel input support is in media-tree would be to move the vl42 video device registration to VIN probe(), I'm sure Hans will react to that :-) +11:24 < kbingham> neg, I think getting an initial reaction is a good starting point for the dicussion :) +11:28 < pinchartl> regarding backlog reduction and GMSL, I propose to discuss tasks over e-mail as this meeting is already running late. I'll initiate the discussion +11:28 < pinchartl> is that ok ? +11:28 < kbingham> Yes. +11:28 < neg> ok for me +11:28 < pinchartl> thanks +11:29 < pinchartl> next topic +11:29 < pinchartl> Topic 4. Periperi Annual Meeting +11:30 < pinchartl> lots of locations have been proposed since our last meeting in San Sebastian +11:30 < pinchartl> it's now time to decide +11:30 < pinchartl> Wolfram has proposed meeting in Paris right before or after Kernel Recipes +11:31 < pinchartl> while a week under the sun in southern Europe would have been more tempting for me, I think his proposal makes +11:31 < pinchartl> sense +11:31 < pinchartl> Paris isn't as horrible as the Belgian countryside :-) +11:31 < pinchartl> Magnus already mentioned he won't be able to attend due to a personal additional task +11:32 < pinchartl> the real question, of course, is whether we'll have budget to organize this +11:32 < pinchartl> while it hasn't been confirmed, I have repeatedly been told that we should move forward with planning +11:32 < pinchartl> dammsan: is my understanding correct ? +11:32 < dammsan> i think so +11:33 < pinchartl> thank you +11:33 < pinchartl> what's everybody's opinion about the proposed location and time ? +11:34 < pinchartl> KR is Sep 26-28 +11:34 < dammsan> it is about time for me to wrap up, may i be excused? +11:34 < Marex> pinchartl: I'll be speaking at ER, vaishali at KR I think +11:34 < Marex> pinchartl: how does one register to KR , are the tickets available already ? +11:34 < Marex> pinchartl: it'd suck to have to wait it out +11:34 < kbingham> Marex, no I don't think tickets are available yet. +11:35 < kbingham> But they go pretty fast - so it's best to register on the day they come out;. +11:35 < Marex> kbingham: which is ... when ? :) +11:35 < Marex> kbingham: happened to me last time, yeah +11:35 < kbingham> Marex, Exactly. +11:35 < kbingham> When :) +11:36 < kbingham> The time I went - the release date was announced on twitter. +11:36 < pinchartl> there's usually about 100 seats available +11:36 < Marex> bleh +11:36 < pinchartl> I'm not sure it would be fair taking 10% of that for our team... +11:37 < pinchartl> I mean, if people want to attend, sure, but I don't think we should push everybody to attend just because we would meet before or after the conference +11:37 < Marex> pinchartl: except I think many people do want to attend anyway +11:37 < wsa_> I am only available before KR +11:38 < pinchartl> Marex: has the schedule been decided already, or is it still worth proposing a talk ? +11:38 < pinchartl> ER is Sep 24-25 +11:38 < Marex> pinchartl: they are announcing speakers +11:39 < Marex> pinchartl: you can always try +11:39 < pinchartl> so the best option would likely be to meet the week before the conference +11:39 < pinchartl> Sep 17-21 +11:39 < pinchartl> is everybody available ? +11:40 < kbingham> Yes here. +11:40 < pinchartl> Marex: just for my information, when did you submit your talk proposal ? +11:40 < geertu> I think it's doable +11:40 < pinchartl> wsa_: how about you ? +11:41 < wsa_> that week works for me +11:41 < wsa_> we have a meeting scheduled on 20th anyhow ;) +11:41 < pinchartl> :-) +11:41 < neg> 17-21 looks OK in my calendar +11:41 < uli___> good for me, too +11:43 < Marex> pinchartl: they polled me for a talk in Feb or so +11:43 < Marex> pinchartl: then I heard nothing for a long time, then they asked me for abstract a few days ago +11:43 < Marex> 17-21 is I think OK for me +11:43 < pinchartl> Marex: thanks +11:43 < pinchartl> ok, please block those dates +11:43 < pinchartl> and submit a travel plan to secure budget +11:44 < pinchartl> with cost estimates for travel and accommodation +11:44 < uli___> to whom? +11:44 < wsa_> I assume we are going for the huge appartment thing again? +11:44 < Marex> in Paris ? :) +11:44 < Marex> I thought there were only small romantic apartments there +11:44 < pinchartl> dammsan: as Morimoto-san isn't here, should he volunteer to handle this ? :-) +11:45 < pinchartl> I think we can send him the travel plans +11:45 < pinchartl> wsa_: I think it would make sense, both from a cost point of view and from a meeting infrastructure point of view +11:45 < wsa_> Marex: if that's the case, I might have no time to work +11:45 < wsa_> ;) +11:45 < pinchartl> we will need two or three apartments I assume +11:45 < Marex> pinchartl: +1 +11:46 < dammsan> good idea +11:46 < dammsan> =) +11:47 * vaishali wonders what happens in periperi annual meeting and if she is supposed to attend it. +11:47 < geertu> wsa_: How many small romantic apartments do you need? ;-) +11:47 < pinchartl> 3 apartments = one per group leader ? +11:49 < geertu> 162€ for the train to/from Paris +11:49 < pinchartl> dammsan: could you be so kind to explain to vaishali what the annual meetings are ? +11:49 < wsa_> geertu: depends a bit on how widespread polyamory is in Paris :) +11:49 < neg> 3 group leaders, 3 apartments ... is this one of these TV realtiy shows where we compete and vote ppl to exile? +11:50 < dammsan> i think neg summed it up pretty well =) +11:50 < kbingham> Lol :) +11:50 < geertu> vaishali: Pinchartl may ask you to bring a spoon... +11:51 < marex-cloud> geertu: whatever happens in periperi annual meeting, stays in the meeting ... it's like Vegas ;-) +11:51 < geertu> marex-cloud: Can you get married with Elvis? +11:51 < pinchartl> vaishali: in a nutshell, we spend a week together to discuss yearly planning +11:51 < marex-cloud> geertu: sssssssssssh +11:51 < wsa_> We have something like a mixture of a co-working space and a hotel near where I live. Maybe something like this exists in Paris as well? I'll check +11:51 < pinchartl> and possibly organize code camps on the side if time permits +11:53 < neg> I think more code camp time is a good idea, the FOSDEM one was productive IMHO +11:54 < pinchartl> neg: I agree with you +11:54 < vaishali> pinchartl: Ok, code camps sounds like fun. As I'm coming for KR anyway, I think I can come a week early. +11:54 < pinchartl> vaishali: perfect :-) +11:54 < pinchartl> let's try to close the meeting, it's getting late +11:54 < pinchartl> Topic 5. Next Meeting +11:54 < pinchartl> two weeks from now +11:54 < pinchartl> it has been agreed on already, so that's easy +11:55 < pinchartl> that's all for me. is there anything else that anyone would like to discuss ? +11:55 < kbingham> All good here! +11:55 < neg> not from me, thanks all +11:55 < marex-cloud> uli___: I've got to step out for a bit, but please recheck the ATF U-Boot dram thing +11:55 < marex-cloud> All good here +11:55 < wsa_> all fine here +11:56 < pinchartl> uli___: dammsan: anything else for you ? +11:56 < uli___> nope +11:56 < marex-cloud> uli___: I'm happy to discuss that over IRC +11:56 < pinchartl> in that case +11:57 < pinchartl> I declare the meeting adjourned +11:57 < pinchartl> thank you all for attending +11:57 < pinchartl> have a nice day |