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
|
h1. MiniPeriCon for MultiMedia 2017-05
| Date | 2017/05/29, 30 (before "OSS Japan":http://events.linuxfoundation.org/events/open-source-summit-japan/) |
| Place | "YUYUTEI":https://www.airbnb.com/rooms/17013981 |
| Member | Laurent, Kieran, Niklas, Magnus, Jacopo, Marek, Morimoto |
!2017-05-miniperi/IMG_201705_1.JPG! !2017-05-miniperi/IMG_201705_2.JPG!
!2017-05-miniperi/IMG_20170530_150006.jpg! !2017-05-miniperi/IMG_20170530_150016.jpg!
!2017-05-miniperi/IMG_20170603_104743.jpg! !2017-05-miniperi/IMG_20170603_105242.jpg! !2017-05-miniperi/IMG_20170603_105902.jpg!
!2017-05-miniperi/IMG_20170603_110553.jpg! !2017-05-miniperi/IMG_20170603_110603.jpg! !2017-05-miniperi/IMG_20170603_105328.jpg!
!2017-05-miniperi/IMG_20170603_110713.jpg! !2017-05-miniperi/IMG_20170603_110723.jpg! !2017-05-miniperi/IMG_20170603_111049.jpg!
!2017-05-miniperi/IMG_20170603_113205.jpg! !2017-05-miniperi/IMG_20170603_111821.jpg! !2017-05-miniperi/IMG_20170603_111826.jpg!
!2017-05-miniperi/IMG_20170603_113214.jpg! !2017-05-miniperi/IMG_20170603_124831.jpg! !2017-05-miniperi/IMG_20170603_114023.jpg!
!2017-05-miniperi/IMG_20170603_132350.jpg! !2017-05-miniperi/IMG_20170603_133957.jpg! !2017-05-miniperi/IMG_20170603_134012.jpg!
!2017-05-miniperi/IMG_20170603_134122.jpg! !2017-05-miniperi/IMG_20170603_161227.jpg! !2017-05-miniperi/IMG_20170603_161211.jpg!
!2017-05-miniperi/IMG_20170603_134244.jpg! !2017-05-miniperi/IMG_20170603_161406.jpg!
PeriPeri Tokyo Meeting - 2017-05-29
h1. V4L2 community status
h2. Maintainership evolutions
Laurent has explained the current maintainership issues in the V4L2 community. No notes have been taken to avoid leaking the content of the conversation, as the topic is very sensitive.
h2. API reboot in 2018
V4L2 grew organically over 15 years. We're now reaching a point where the API is bloated and unclear. We need to rework it extensively, building upon good ideas and mistakes we've done in the past. A 3 days multimedia summit will be proposed for beginning of 2018 to discuss that work.
h2. Community involvement to multimedia team members
V4L2 lacks core developers who can review APIs and drivers. We would like the multimedia team to take a more leading role there, reviewing code posted by other developers (including drivers for non-Renesas platforms). This is useful for Renesas for two main reasons. From a PR point of view, being recognized as a reference for everything multimedia-related in Linux would benefit Renesas (although the effect on attracting customers might be more important for the RZ platforms than the R-Car platforms). From a technical point of view, becoming core developers builds knowledge in the team that can then be put to use for our own development.
The easiest way to expand our community contributions is to handle them as part of base contracts. This implies that less base contract time will be spent on Renesas-related development, so we need Renesas to back us up on that decision. In practice, review of non-Renesas drivers should become acceptable deliverables for base contracts.
We will experiment with adding "ongoing community development of interest" topic in the bi-weekly multimedia meeting during which every team member can report patches they noticed on mailing lists that they find is of interest to the team.
We should also get more involved in the following tasks.
# Contribute to V4L2 documentation. The API reference documentation is pretty extensive, but it lacks walk-through documentation. We should write that using one of the Renesas boards as an example. Unlike existing similar document that just list steps without explaining the rationale behind them, this tutorial-like documentation should be a V4L2 walk-through document that uses a particular board as an example only. Do this at elinux for a start and later it can be made more generic and moved to the kernel documentation.
# Give talks in conferences to share multimedia knowledge. This also expands our visibility towards the community and contributes to positioning ourselves as a reference for Linux mutlimedia development.
# Improve user tooling
It would be helpful to create one or more "reference platforms" with good V4L2 device coverage. Using R-Car Gen3 hardware for this purpose makes sense, for instance cost effective ULCB boards. So we would need to get the out-of-tree V4L2 subsystem and device driver changes into mainline, and document how to use them in some sort of basic fashion. This could for instance be some simple example on how to set up media controller nodes to route video in certain ways on this particular reference platform. Then in detail workshops or talks can be given to show how to make use of various more advanced features of the hardware platform. The state of these probably needs to be continuously updated once the various incremental framework changes get accepted.
h1. Multimedia plan & Additional tasks
We have discussed the multimedia development plan for the next quarter, and drafted additional tasks candidates. Laurent will finalise the plan and additional tasks for end of June.
h1. Video Codecs
Possibly suitable for Q4. Magnus will provide more information/documentation related to use cases if he gets pinged by e-mail.
h1. How to handle "periupport":https://osdg.renesas.com/periperi/periupport on MultiMedia group
|
