summaryrefslogtreecommitdiff
path: root/wiki/Chat_log/20170412-mm-chatlog
diff options
context:
space:
mode:
authorKuninori Morimoto <kuninori.morimoto.gx@renesas.com>2019-12-09 15:29:52 +0900
committerKuninori Morimoto <kuninori.morimoto.gx@renesas.com>2019-12-09 16:23:07 +0900
commit55e3b2f45880faaf06f3c660ca9e8a6d9aa14bce (patch)
tree6392fd201a51ff0f6dc0e474803e6f3b20919504 /wiki/Chat_log/20170412-mm-chatlog
parent5d9e1b983faf7645ddc3d45d28e612d2ac4179c0 (diff)
wiki: Porting wiki: Porting Chat Log
Signed-off-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Diffstat (limited to 'wiki/Chat_log/20170412-mm-chatlog')
-rw-r--r--wiki/Chat_log/20170412-mm-chatlog539
1 files changed, 539 insertions, 0 deletions
diff --git a/wiki/Chat_log/20170412-mm-chatlog b/wiki/Chat_log/20170412-mm-chatlog
new file mode 100644
index 0000000..7cffe38
--- /dev/null
+++ b/wiki/Chat_log/20170412-mm-chatlog
@@ -0,0 +1,539 @@
+Multimedia-chat-meeting-2017-04-12
+
+<pinchartl> good morning [15:55]
+<neg> morning
+<morimoto> hi
+<uli___> hello [15:56]
+<pinchartl> let's wait a few minutes for Jacopo and Magnus to join [15:57]
+<kbingham> Morning all
+<jmondi> 'morning
+<pinchartl> now only Magnus is missing :-) [15:58]
+<neg> while we wait [16:00]
+*** dammsan (~dammsan@s214090.ppp.asahi-net.or.jp) has joined channel
+ #periperi [16:01]
+<neg> morimoto: is it enugho infomrmation about 'VIN issues on H3 ES2.0 and M3
+ ES1x/M3W' to talk about it today or should we postpon it?
+* morimoto Renesas talk now
+<pinchartl> hi Magnus
+<pinchartl> neg: I think we should at least mention it
+<pinchartl> let's get started
+<pinchartl> topics for today
+<pinchartl> Topic 1. Status check for the multimedia tasks [16:02]
+<pinchartl> Topic 2. VIN issues on H3 ES2.0 and M3 ES1x/M3W
+<pinchartl> Topic 3. Upstream V4L2 development
+<pinchartl> anything else ?
+<pinchartl> ok, let's start with status updates [16:03]
+<jmondi> maybe a check up on travel plans for OSS?
+<pinchartl> jmondi: good point
+<neg> Stamp of approvel for Tokyo dates, the mail thread is dead and time to
+ buy tickets ;-)
+<kbingham> Ack with those :) ^
+<pinchartl> Kieran has to run away in the middle of the meeting, so he will
+ get started
+<pinchartl> kbingham: the stage is yours
+<kbingham> Why thankyou maestro :-)
+* morimoto back [16:04]
+<kbingham> So I'm now back on RCar developments and I've commenced looking at
+ the ADV7482 work
+<kbingham> I have had some difficulty capturing frames through VIN so far,
+ getting the links set up to capture.
+<morimoto> neg: we have no W/A at this point, so, nothing to discuss today. it
+ is just information sharing [16:05]
+<kbingham> (I have tried to capture using the existing code base, using HDMI
+ in ) - and a RPi to generate HDMI data
+<kbingham> But the issue is getting the formats to propogate - checking the
+ formats shows 'unknown' in the FMT field .. and things aren't
+ propogating through media ctl. [16:06]
+<pinchartl> kbingham: do you have further things to try, or are you completely
+ blocked ?
+<pinchartl> if it's a format propagation issue I assume you can try to debug
+ it
+<kbingham> I'll have more things to try - like getting some prints in to see
+ why the formats aren't there [16:07]
+<kbingham> yes - It's just a debug issue really.
+<kbingham> But will help me walk the code base anyway
+<pinchartl> ok
+<neg> kbingham: did you try h3-compliance.sh from vin-tests?
+<kbingham> neg: Yup ! Same issue
+<kbingham> neg: And I set my RPi dev to 640x480 as you suggested - still no
+ avail - so I just need to dig and understand the issue
+<neg> hum that is strange, guess I need to buy a RPI today :-)
+<kbingham> If needed, I'll talk to (neg) later about that if possible. [16:08]
+<pinchartl> you can also ask me
+<pinchartl> not that I have tried it
+<pinchartl> but I can guide you through the format propagation process and
+ code
+<kbingham> pinchartl: Thankyou :D Anyway - otherwise- Once that issue is
+ resolved, I have started looking at how to create the subdevs, as
+ per our disucussions
+<kbingham> and once I have established a baseline - I should be comfortable
+ hacking away at that. [16:09]
+<pinchartl> ok, thank you
+<neg> first guess is it's EDID related since the ADV7482 have no EDID support
+ I do all my testing using a Xbox as source so I assume it fallback to
+ something the ADV7482 likes
+<neg> that is the ADV7482 driver have no EDID support
+<kbingham> By default, the source is coming up as [fmt:unknown/1920x1080
+ field:none] [16:10]
+<kbingham> Anyway, we can go through that later :D [16:11]
+<neg> kbingham: the ADV7482 prototype should autodetect the formats, I would
+ like to see the fill media graphyou get if possible, but maybe you and I
+ can hash this out after the meeting :-)
+<pinchartl> jmondi: you're next in resumed alpbabetical order :-)
+<kbingham> I agree - we'll go through this after the meeting rather than in
+ the meeting :)
+<jmondi> fine... [16:12]
+<jmondi> so, I started looking at moving the CEU driver away from soc_camera
+<jmondi> I'm still evaluating if it is better to rewrite it or patch the
+ existing
+<pinchartl> what's your opinion at this point ? [16:13]
+<jmondi> I'm a bit more inclined to patch the existing, because at the moment
+ it seems to me the driver could be implemented without sub-devices,
+ just with a single video device
+<jmondi> also, I saw there is a VEU driver, which seems simple enough to use
+ as "inspiration" [16:14]
+<jmondi> even if it is a mem2mem device
+<pinchartl> that sounds good to me
+<pinchartl> you need a subdev for the camera sensor
+<pinchartl> but you don't need to expose it to userspace [16:15]
+<jmondi> yeah, camera sensor apart...
+<jmondi> because the CEU has a format conversion unit, that can be modeled as
+ sub-device visibile to userspace
+<pinchartl> the atmel/atmel-isc.c driver seems to be a good example
+<jmondi> but I guess it can be left out for now [16:16]
+<pinchartl> you don't need to, you can implement format conversion internally
+<pinchartl> yes, also
+<jmondi> pinchartl: thanks, I would have asked you suggestions on which driver
+ to look at
+<jmondi> and that's all
+<jmondi> I would have to clarify if OF support only is enough
+<jmondi> because the remote mingor board we should start with, has no OF
+ support if I'm not wrong, right Magnus? [16:17]
+<pinchartl> pxa_camera should also be an option
+<jmondi> pinchartl: I gave a look at pxa camera, mostly for OF parsing
+<pinchartl> correct, no OF support in Migor [16:18]
+<pinchartl> you need to use platform data :-/
+<jmondi> that's bad, it means I have to implement both :/
+<pinchartl> you can start with platform data, and implement OF support later
+ [16:19]
+<jmondi> we should also discuss about hw setup.. but it can be post-poned
+ after mingor has been made at least booting mainline
+<pinchartl> sounds good to me [16:20]
+<pinchartl> how about the next two weeks ? do you plan to continue working on
+ this ?
+<jmondi> I'm still intrigued byt the idea of starting with an RZ device from
+ day 0
+<jmondi> pinchartl: yes, now that my other 2 tasks for IO/core are almost
+ done, I'll be fully on multimedia
+<pinchartl> ok [16:21]
+<jmondi> I'll stop here, not to steal the stage to all the others :)
+<pinchartl> one more thing, could you please remember to send your status
+ report by e-mail before the meeting next time ? [16:22]
+<dammsan> jmondi: yes there is no OF support for migor
+<jmondi> pinchartl: uh, I'll do this right away
+<jmondi> sorry about that
+<pinchartl> jmondi: no need to for today, I'll include it in the report
+<pinchartl> but it helps if I get them in advance
+<jmondi> and, pinchartl, I'll ping you a bit more often in next days, hope you
+ won't mind ;)
+<pinchartl> no problem with that :-) [16:23]
+<jmondi> (I'll be away from tomorrow to Tues. since we're speaking)
+<jmondi> ok, done with me
+<pinchartl> next, me
+<pinchartl> I've mostly worked on code review and various discussions,
+ internally and upstream
+<pinchartl> as well as additional tasks negotiation [16:24]
+<pinchartl> from a code point of view, I've tried to get the VSP rotation and
+ histogram support merged upstream in v4.12
+<pinchartl> it resulted in yet another fight with Mauro
+<pinchartl> up to a point where I can't take his abusive behaviour anymore
+ [16:25]
+<pinchartl> I took a few days to think this over
+<pinchartl> among the various options most of them seemed unreasonable to me
+<pinchartl> such as challenging him publicly for V4L2 maintainership for
+ instance
+<pinchartl> Hans Verkuil proposed to me to act as an interface between Mauro
+ and me [16:26]
+<pinchartl> to avoid all direct interactions
+<pinchartl> I don't really think this would work, but I might give it a try
+<pinchartl> in any case, I saw no other option that stepping out from upstream
+ V4L2 development, at least temporarily
+<pinchartl> I will reconsider that decision if the situation changes [16:27]
+<pinchartl> (or if I find a better idea)
+<pinchartl> in effect, this means I can continue reviewing code and driving
+ discussions internally
+<pinchartl> including architecture discussions
+<pinchartl> but I'll remain silent publicly for now
+<pinchartl> it also means I will likely need to refrain to author any V4L2
+ patch [16:28]
+<pinchartl> I still need to discuss this with Hans today, after this meeting
+<dammsan> sounds good to me
+<pinchartl> for the next two weeks, I plan to work on the multi-camera setup
+ and try to get it working
+<pinchartl> VSP fences support is effectively on hold, I can't work on that
+ [16:29]
+<dammsan> you can also consider putting mauro on fire
+<pinchartl> I've considered that, but I don't think it will help
+<pinchartl> he will fight back, and it would just create a bit mess, most
+ likely without any concrete improvement
+<dammsan> he looks like he may burn well
+<dammsan> probably
+<pinchartl> dammsan: let's not resort to personal non-technical attacks
+ [16:30]
+<pinchartl> that's it for me for today
+<pinchartl> if any of you wants to discuss this further let's do so after the
+ status updates [16:31]
+<pinchartl> next, dammsan
+<neg> quick question, 'reviewing code internally' means no public review of
+ patches?
+<dammsan> no update from my side, currently installing migor in the remote
+ access rack
+<pinchartl> neg: correct. let's discuss the implications after the status
+ update [16:32]
+<pinchartl> dammsan: thank you
+<pinchartl> I assume you'll now try to get Migor to boot mainline ?
+<dammsan> once it is installed yes [16:33]
+<pinchartl> thank you
+<dammsan> thanks
+<pinchartl> next, Morimoto-san
+<morimoto> A) What have I done since last time
+<morimoto> continue OF-graph posting. I got response from Rob, but he mentions
+ small details which is related to ALSA SoC, not to OF-graph.
+<morimoto> BSP team reported Sound issue. Almost all bugs are fixed. But some
+ noise issue was not yet solved. I'm thinking this is related to
+ board specific clk issue (L/R clock gets interference from Bit
+ clock)
+<morimoto> 8ch camera datasheet export paper work
+<morimoto> created periupport script
+<morimoto> shared H3/M3 VIN issue to you guys ;P
+<morimoto> B) What I plan to do till next time [16:34]
+<morimoto> continue OF-graph posting
+<morimoto> continue sound noise issue fix
+<morimoto> 8ch camera board check by using demo program with BSP team
+<morimoto> C) Problems I have currently
+<morimoto> OF-graph stalling
+<morimoto> --EOT--
+<pinchartl> thank you
+<pinchartl> when do you think you will be able to verify the multi-camera
+ setup with the demo program ? [16:35]
+<morimoto> According to BSP team, I and Magnus will check it on this Fri
+<dammsan> huh, good to know
+<dammsan> =) [16:36]
+<pinchartl> :-D
+<morimoto> dammsan: this means you need to bring it to Renesas Office on Fri
+ :P
+<pinchartl> I'll wait until this weekend before working on it then
+<pinchartl> could you post a status update when you will be done on Friday ?
+ [16:37]
+<morimoto> Of course I will check 2 board which will be ship to Laurent/Niklas
+ after May
+<pinchartl> and Magnus, will you be able to reinstall it in your remote access
+ setup after your done, to allow me to work on it during the
+ weekend ?
+<morimoto> pinchartl: sure
+<pinchartl> thank you [16:39]
+<dammsan> pinchartl: not sure about when i will get time to do that
+<morimoto> I think all needed 8ch camera datasheet/information exist on Wiki
+ now. do we still missing something ?
+<pinchartl> dammsan: could you at least send me an e-mail when you will be
+ done ? and also notify me if you get delayed ?
+<dammsan> it depends on how long time is needed in the renesas office [16:40]
+<pinchartl> morimoto: I still don't know what the small microcontroller inside
+ the cameras does exactly. do you have any information about that ?
+ it's connected to the I2C control bus, and controls the sensor
+ power down signal
+<dammsan> once it is working i will reinstall it in the remote access rack
+ [16:41]
+<pinchartl> dammsan: you don't have to work around the clock obviously :-) but
+ for planning purposes, it would help if you could let me know at
+ the end of Friday if there will be delays
+<morimoto> pinchartl: do you mean U402 ? and I think you are asking it to IMI
+ guys ? [16:42]
+<pinchartl> morimoto: yes, U402. I've asked the IMI person who sent me the
+ schematics, but haven't received any answer
+<dammsan> i highly doubt things will start workin on friday
+<morimoto> OK, I will push him
+<dammsan> and we have meetings most of the afternoon
+<dammsan> so i think you can assume you will not get it this weekend [16:43]
+<pinchartl> dammsan: ok. let me know if that changes then
+<dammsan> will let you know once it is reinstalled
+<dammsan> thanks
+<pinchartl> morimoto: I see your e-mail report contains a list of patches. do
+ I need to include them in the meeting report, or will they be
+ picked up by your scripts ? [16:44]
+<pinchartl> while waiting for that answer [16:45]
+<pinchartl> neg: your turn
+<neg> a)
+<neg> - Fixed up some small CSI-2 stuff, patches pending waiting further
+<neg> work before I post them.
+<neg> - Had discussions with Laurent, Kieran and Sakari about V4L2
+<neg> extensions needed to support ADV7482.
+<neg> - Took a stab at at extending the of graph framework to be able to
+<neg> iterate over all DT nodes in a graph connected by endpoints. But
+<neg> ceased work after the talk above since the core issue can
+<neg> hopefully be solved in a better way and then there would be no
+<neg> users of this. [16:46]
+<neg> - Tried to help out as much as possible with the 8-channel VIN
+<neg> prototype Ulrich and Laurent are working on.
+<neg> b)
+<neg> - Respin CSI-2 and VIN patches with my new found knowledge of V4L2
+<neg> async framework.
+<neg> - Keep supporting 8-channel VIN if needed.
+<neg> - Address any review comments on VIN and CSI-2 patches.
+<neg> c)
+<neg> - No review or other activity on VIN patches, the series [PATCH
+<neg> 00/16] rcar-vin: fix issues with format and capturing' IMHO ready
+<neg> to be picked up upstream but needs reviews.
+<neg> Also Friday 14/4 and Monday 17/4 are holidays in Sweden and I will be
+ out of town at least on Friday, so my response times are reduced between
+ those dates.
+<pinchartl> thanks for letting us know
+<morimoto> pinchartl: I think bugfix patches of D) ? it will be pickuped
+ automatically by our script. you can drop it. thanks [16:47]
+<pinchartl> those two days are public holidays in Finland too
+<pinchartl> morimoto: thank you
+<pinchartl> regarding the rcar-vin series
+<pinchartl> I can review it internally [16:48]
+<pinchartl> again, let's discuss that after the status updates
+<pinchartl> uli___: your turn
+<uli___> so the csi purports to capture frames from the max9286, but it
+ doesn't really
+<uli___> i tried turning off integrity checks, but to no avail
+<uli___> i guess the data is not valid; maybe the virtual channel setup is
+ wrong? [16:49]
+<uli___> that's pretty much it. two suggestions for friday:
+<uli___> 1. dump the registers of the max92* and ov10635, if it works
+<uli___> 2. dump the microcontroller, if you have an isp programmer lying
+ around
+<uli___> it has 8k of rom, and most of it will be ov10635 register settings
+<uli___> should be easy to reverse-engineer... [16:50]
+<pinchartl> uli___: do you think that U402 is an I2C master ?
+<pinchartl> I thought it was a slave
+<uli___> the driver code suggests so
+<pinchartl> ouch
+<uli___> it says that linux doesn't support multi-master busses
+<uli___> and that it has to wait for the attiny to finish because of that
+<pinchartl> that would require opening the camera, I'm not sure if that's
+ feasible [16:51]
+<uli___> oh, i see...
+<pinchartl> but if the microcontroller indeed configures the sensor by itself,
+ we might have issues, yes
+<uli___> well, that's it from me [16:53]
+<pinchartl> thank you for the suggestions
+<pinchartl> that's it for the status updates
+<pinchartl> Topic 2. VIN issues on H3 ES2.0 and M3 ES1x/M3W [16:54]
+<pinchartl> Morimoto-san has reported VIN-related issues in the wiki
+<pinchartl>
+ (https://osdr.renesas.com/projects/linux-kernel-development/wiki/R-Car-Gen3#VIN-issue)
+<pinchartl> we don't have much information at this point though
+<pinchartl> so there isn't much to discuss
+<pinchartl> but I have a question [16:55]
+<morimoto> Yes. but it is just information, and no W/A at this point.
+<pinchartl> morimoto: do those issues impact the multi-camera setup we're
+ trying to get working ?
+<neg> morimoto: W/A == Wanted Action?
+<pinchartl> neg: Work Around
+<pinchartl> (I assume)
+<morimoto> yes Work Around, sorry [16:56]
+<neg> thanks :-)
+<morimoto> pinchartl: According to BSP team, upstream is supporting 2 Lane ?
+<morimoto> 1 lane, and 4 lane have no issue
+<morimoto> but 2 lane has issue on M3
+<morimoto> BSP team is using H3 [16:57]
+<morimoto> and our remote access is using M3
+<pinchartl> dammsan: would it be possible to switch the remote access setup to
+ H3 ?
+<morimoto> pinchartl: 1 question. are multimedia people tring to 8ch directly
+ ? [16:58]
+<morimoto> I though 1ch camera as fist step [16:59]
+<pinchartl> morimoto: no, we're trying to capture from a single camera first
+<morimoto> OK
+<morimoto> So then it is using 1lane ? maybe M3
+<morimoto> s/mabe M3//
+<uli___> 4 lane [17:00]
+<dammsan> pinchartl: i can attach the camera board to H3 instead [17:01]
+<dammsan> but then our ground might become more stable
+<dammsan> i mean more unstable since it is changing
+<pinchartl> I think this can wait until Friday
+<morimoto> sorry I was wrong. CSI40's 1lane and 2lane are NG. CSI40 4lane is
+ OK. CSI20 is all OK
+<dammsan> after the hardware has been verified in the renesas office i will
+ use the same one for the remote access
+<pinchartl> if you get it to work on H3 on Friday but can't on M3, then we'll
+ switch to H3 :-) [17:02]
+<dammsan> of course if you have any special preference then we will follow
+ that
+<pinchartl> I think we're done with status updates [17:03]
+<pinchartl> sorry, with VIN :-)
+<pinchartl> Topic 3. OSS Japan trip
+<pinchartl> (FYI, my talk at OSS Japan has been approved) [17:04]
+<pinchartl> we need to start booking planes and hotels
+<pinchartl> morimoto: can we proceed with Renesas' blessing ?
+<morimoto> blessing = trip cost ? [17:05]
+<morimoto> or meeting ?
+<pinchartl> blessing as in getting authorisation to book the trip, and
+ invoicing it to Jinso [17:06]
+<morimoto> Maybe it is OK unless you enjoyed party like Oil tycoon ;P
+<pinchartl> damn, my cunning plan has been understood :-) [17:07]
+<pinchartl> we'll keep the costs down as usual [17:08]
+<pinchartl> no champagne, we'll just drink nihonshu :-)
+<pinchartl> jmondi: kbingham: neg: you can proceed booking tickets
+<pinchartl> uli___: you could too, but you mentioned you won't be able to
+ join, right ?
+<uli___> no, i won't. sorry. [17:09]
+<morimoto> Renesas will pay up to Economy class for flight. Of course you can
+ upgrade, but it is your cost ;P
+<neg> I assume ppl will book the conference hotel even for code camp days?
+<dammsan> "up to Economy class" - makes it sound ike there is something
+ lower? =) [17:10]
+<neg> dammsan: United?
+<dammsan> haha, if you prefer to be dragged out
+<neg> haha :-)
+<jmondi> what days we said again? 26th to the 2nd? [17:11]
+<pinchartl> jmondi: 29th to 3rd
+<pinchartl> (Monday to Saturday)
+<pinchartl> I suggest arriving on the 28th at the latest
+<pinchartl> (that's what I'll do, in the morning)
+<pinchartl> and leaving on the Sunday, or later if you want to take some time
+ to visit Tokyo [17:12]
+<pinchartl> please be careful about the jetlag though
+<pinchartl> flights from Europe often land early in the morning
+<pinchartl> if you have trouble sleeping in the plane, the next day is very
+ painful
+<pinchartl> you might want to arrive on the 27th to have more time to recover
+ [17:13]
+<jmondi> looking at flights now
+<pinchartl> neg: I've booked the conference hotel for the first two days too
+<pinchartl> the rate allows changes
+<morimoto> And we will have multimedia F2F meeting on 29th 30th ?
+<pinchartl> so I might move to a different location after we decide on the
+ meeting location
+<pinchartl> morimoto: correct. we still haven't decided where to host that
+ [17:14]
+<morimoto> OK
+<pinchartl> I would appreciate if our valued Japanese and Japanese resident
+ team members could advise on appropriate meetings locations
+<morimoto> OK, I and Magnus will try it. dammsan: please say YES [17:15]
+<dammsan> YEESS
+<pinchartl> thank you :-)
+<morimoto> How many member ? [17:16]
+<pinchartl> it should be 4 from Europe [17:17]
+<pinchartl> Jacopo, Kieran, Niklas and me
+<pinchartl> I assume Magnus and you will join too
+<pinchartl> I don't know who else would like to attend from Japan
+<pinchartl> we will have a multimedia team meeting, but I also want to use
+ this opportunity to work on the multi-camera setup with local
+ access to the hardware [17:18]
+<pinchartl> so I'd like part of those two days to be a code camp
+<pinchartl> next topic, upstream V4L2 development [17:19]
+<neg> If I understnad the mail thread corretly Wolfram won't be there so no IO
+ meeting to conflict with, but can't see any feedback from Geert. Anyone
+ know if extra days will be needed for Core meeting?
+<pinchartl> neg: I don't know. let's ask geertu [17:20]
+<neg> geertu: ^ :-)
+<pinchartl> I've already explained the situation briefly. I assume some of you
+ may have questions
+<pinchartl> (suggestions will be appreciated too, feel free to speak your mind
+ honestly)
+<jmondi> pinchartl: is the discussion you had with Mauro on linux-media list?
+ [17:21]
+<pinchartl> no, it was an IRC discussion on #v4l
+<jmondi> oh, that's why :) [17:22]
+<pinchartl> it's not that discussion as such that prompted me to reconsider my
+ involvement, but all the interactions I've had with Mauro over the
+ past 12 months (at least)
+<pinchartl> this was just the last straw
+<neg> First off. I think it's problematic that you step away from V4L2, even
+ for a while. But I understand why you do it and support it. [17:23]
+<pinchartl> neg: thank you. for the record, when I said you're free to state
+ your mind, I could totally understand if you (or anyone else)
+ couldn't understand my decision, and thought it was a very bad
+ idea [17:24]
+<jmondi> how can you really step away, involved as you are (saying this from
+ the point of view of someone outside the v4l2 community)?
+<pinchartl> jmondi: but stopping all my involvement
+<pinchartl> not sending any patch anymore
+<pinchartl> not participating in any public discussion (mailingl list, irc,
+ face to face meetings) [17:25]
+<pinchartl> not reviewing any code anymore
+<pinchartl> (at least publicly)
+<jmondi> I mean, everything you guys have discussed here has been shared to
+ other v4l2 members (and that's great)... will you drop everything?
+<pinchartl> I plan to continue supporting the multimedia team and every member
+ who works on V4L2 through internal discussions and code reviews
+ [17:26]
+<pinchartl> but that might be the most I will be able to do
+<pinchartl> as mentioned earlier, I will discuss this with Hans Verkuil after
+ this meeting [17:27]
+<neg> This creates voids since you is a big part when the media group interact
+ with the V4L2 community, I feel at least I would need to ask you from
+ time to time how to best proceed with things like that even if you won't
+ be a part of it
+<pinchartl> he proposed acting as middleman between Mauro and me
+<pinchartl> while I don't think it would work, I could still give it a try
+<pinchartl> neg: I'll answer all questions from the team and will help as much
+ as I can [17:28]
+<neg> The thing closest to my heart is to get the VIN Gen3 patches upstream
+ and my interpretation of the situation have been that Hans have waited
+ for you to review the patches, and now that you can't public review/ack
+ those patches I feel worried on how to proceed to get those patches
+ upstream.
+<pinchartl> but you would need to be the one taking up the fight against Mauro
+ publicly
+<pinchartl> I won't be able to support you when it comes to defending your
+ work in public
+<jmondi> v4l3? :p
+<pinchartl> jmondi: that's also an option I've considered, but I don't think
+ it's feasible. I might be wrong though
+<pinchartl> ah, another point, for the record [17:30]
+<pinchartl> Google will likely continue the work on the request API
+<pinchartl> (in particular Alexandre Courbot and Tomasz Figa from the chromeos
+ team)
+<pinchartl> I have a meeting scheduled tomorrow with them to explain how I
+ would like them to proceed
+<pinchartl> but their main use case is video codecs
+<pinchartl> they have no performance-related use case like we do [17:31]
+<jmondi> and no android stupid HAL libraries to make happy
+<pinchartl> so I fear this means that whatever will be merged upstream will
+ not support our use cases
+<pinchartl> we might be left with no way to get decent performances from the
+ VSP with upstream APIs
+<pinchartl> that would be a big gap that the BSP would need to cover
+<pinchartl> I might be painting the situation blacker than it is really, but
+ it's a risk [17:32]
+<pinchartl> dammsan: morimoto: you're silent, any comment or question about
+ all this ?
+<pinchartl> I guess not [17:35]
+<pinchartl> if there's no other question or comment, the next topic is the
+ next meeting [17:36]
+<pinchartl> I propose two weeks from now, same time
+<pinchartl> Wednesday 2017-04-26 at
+<pinchartl> 08:00 GMT / 09:00 CEST / 10:00 EEST / 16:00 JST
+<neg> works for me [17:37]
+<uli___> ok [17:38]
+<pinchartl> jmondi: does it work for you too ?
+<pinchartl> I think we've lost Morimoto-san and Magnus. I'll assume it works
+ for them too
+<neg> pinchartl: maybe we can have a short chat after you talked to Hans about
+ who I can best procced with getting attention on the VIN patches?
+<dammsan> it is fine =)
+<pinchartl> neg: sure
+<neg> thanks
+<jmondi> isn't there IO meeting on the 26th? [17:39]
+<jmondi> no, it's the 18th sorry about that!
+<jmondi> pinchartl: works for me then
+<pinchartl> ok, it's settled then [17:40]
+<pinchartl> if there's no other question, I propose adjourning this
+ meeting. you can always talk to me here or in private later today
+ or at any other time if there's something you'd like to discuss
+<pinchartl> does anyone second ?
+<neg> second [17:41]
+<pinchartl> thank you all for attending, and have a nice day
+<jmondi> second!
+<neg> thanks all, have a nice day
+<jmondi> can I send an email to periperi to discuss about OSS trip
+ organization? [17:43]
+<pinchartl> jmondi: sure [17:44]
+<dammsan> jmondi: yes, we said at 19:00 [17:54]
+* morimoto I'm back from Renesas talk [18:17]
+<morimoto> pinchartl: I will share about Request API topic to BSP team. Thanks