From: Benoit Parrot <bparrot@ti.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: [ANN] Agenda (v1) for the media mini-summit on Friday Oct 27 in Prague
Date: Fri, 13 Oct 2017 07:02:07 -0500 [thread overview]
Message-ID: <20171013120207.GD25400@ti.com> (raw)
In-Reply-To: <807d66bb-87c6-542e-01e6-f7ebba9301e1@xs4all.nl>
Hans,
Just to confirm that I will be attending the media mini-summit.
Regards,
Benoit
Hans Verkuil <hverkuil@xs4all.nl> wrote on Fri [2017-Oct-13 10:02:53 +0200]:
> Hi all,
>
> We are organizing a media mini-summit on Friday October 27 in Prague, co-located
> with the ELCE conference:
>
> http://events.linuxfoundation.org/events/embedded-linux-conference-europe
>
> If you plan to attend, please let me know. It is open for all, but it is
> nice if we know beforehand who we can expect.
>
> Location: Mauro, do you have this information?
>
> Attendees:
>
> Sakari Ailus <sakari.ailus@iki.fi>
> Mauro Carvalho Chehab <mchehab@s-opensource.com>
> Alexandre Courbot <acourbot@chromium.org>
> Michael Ira Krufky <mkrufky@linuxtv.org>
> Gustavo Padovan <gustavo@padovan.org>
> Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com>
> Hans Verkuil <hverkuil@xs4all.nl>
>
> Agenda
> ======
>
> General remarks: the given start/end times for the various topics are
> approximate since it is always hard to predict how long a discussion will take.
> The Request/Jobs API topic is placed last since I expect that that will take
> most of our time.
>
> Let me know asap if there are problems with this schedule, or if new topics
> are requested.
>
> 8:00-9:00: Continental Breakfast served in the room
>
> 9:00-9:15: Introduction (Hans)
>
> 9:15-9:30: Status of the HDMI CEC kernel support (Hans)
> Give a quick overview of the status: what has been merged, what is still
> pending, what is under development.
>
> 9:30-10:00: V4L2 Explicit Synchronization (Gustavo)
> Quick overview and discussion of the API/direction we are going
> with fences.
>
> 10:00-10:30 Media development process: what works, what doesn't (Hans)
> In the past 6 months or so we tried to improve the media development
> process. This is an overview of what we did and why we did it, what
> works and what doesn't. Feedback is very much appreciated. It is even
> more appreciated if people/companies would be willing to assign
> new developers to help improve the media subsystem!
>
> 10:30-11:00: Morning Break served in the room
>
> 11:00-12:00: Media kAPI and uAPI documentation (Mauro)
> Give the current status of media API documentation and identify possible
> gaps and how to improve it.
>
> 12:00-13:30: Lunch
>
> 13:30-??:??: Request/jobs API (Alexandre)
> Overview of the work based on the request API (proposed new name: jobs API),
> to hopefully converge to something that can be merged soon.
>
> 15:00-15:30: Afternoon Break served in the room
>
> 16:30-17:00 (or earlier if we're lucky): Wrap up (Hans)
> Create action items (and who will take care of them) if needed.
> Summarize and conclude the day.
>
> Regards,
>
> Hans
next prev parent reply other threads:[~2017-10-13 12:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-13 8:02 [ANN] Agenda (v1) for the media mini-summit on Friday Oct 27 in Prague Hans Verkuil
2017-10-13 12:02 ` Benoit Parrot [this message]
2017-10-13 15:59 ` Jasmin J.
2017-10-13 16:02 ` Hans Verkuil
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171013120207.GD25400@ti.com \
--to=bparrot@ti.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.