From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: KS2012 <ksummit-2012-discuss@lists.linux-foundation.org>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
media workshop ML <workshop-2011@linuxtv.org>
Subject: [MINI SUMMIT] media mini-summit at KS/2012
Date: Wed, 01 Aug 2012 16:17:07 -0300 [thread overview]
Message-ID: <501980B3.8040809@redhat.com> (raw)
After the discussions around the media mini-summit, this is the
consolidated list of topics.
We tried to give a fair time for each topic.
With regards to the proposed topic "Intel media SDK", nobody
volunteered to give such a talk. So, if there is anyone interested
to talk about it, it can either be part of SoC vendor's feedback
(if it won't take too long), or it could be handled as a topic
during LPC. So, let's put this one in the fridge.
Topics for the media mini-summit
================================
- morning:
V4L2 API ambiguities + v4l2 compliance tool: 60 min
Media Controller library: 30 min
ALSA and V4L/Media Controller: 30 min
ARM and needed features for V4L/DVB: 30 min
- after lunch:
SoC Vendors feedback – how to help them to go upstream: 45 min
V4L2/DVB issues from userspace perspective: 45 min
Android's V4L2 cam library: 30 min
HDMI CEC: 30 min
Synchronization, shared resource and optimizations: 30 min
The DT discussions will likely require more time and maybe a different
audience. So, it seems better to handle it as either as a separate/LPC
section or at DT mini-summit:
Common device tree bindings for media devices: 45 min
Attendants
==========
Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Hans Verkuil <hans.verkuil@xs4all.nl>
Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Mauro Carvalho Chehab <mchehab@redhat.com>
Michael Krufky <mkrufky@linuxtv.org>
Naveen Krishnamurthy <naveen.krishnamurthy@st.com>
Palash Bandyopadhyay <Palash.Bandyopadhyay@conexant.com>
Pawel Osciak <pawel@osciak.com>
Rémi Denis-Courmont <remi@remlab.net>
Sakari Ailus <sakari.ailus@iki.fi>
Sri Deevi <Srinivasa.Deevi@conexant.com>
Steven Toth <stoth@kernellabs.com>
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Marek Szyprowski <m.szyprowski@samsung.com>
Kamil Debski <k.debski@samsung.com>
Naveen also asked another seat for ST, but didn't provide us yet
the name of the other interested party.
For the cross-system topics, it is important to have people from the
other subsystems there. So, we're proposing to have some people
there, but we need to double-check if they can really be there for
the discussions. Of course, other Kernel developers from KS/LPC
that work on those subsystems are welcome.
The names that came up during our discussions for those panels are:
Rob Clark <rob.clark@linaro.org> (HDMI CEC, ALSA, ARM)
Takashi Iwai <tiwai@suse.de> (ALSA)
Catalin Marinas <catalin.marinas@arm.com> (ARM)
Mark Brown <broonie@opensource.wolfsonmicro.com> (DT)
Not sure if they all will be there or if they'll have some time
to discuss those things with us. We hope they will ;)
Thanks,
Mauro Carvalho Chehab
Hans Verkuil
next reply other threads:[~2012-08-01 19:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-01 19:17 Mauro Carvalho Chehab [this message]
2012-08-01 19:42 ` [Ksummit-2012-discuss] [MINI SUMMIT] media mini-summit at KS/2012 Mark Brown
2012-08-02 8:01 ` Takashi Iwai
2012-08-02 15:55 ` Pawel Osciak
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=501980B3.8040809@redhat.com \
--to=mchehab@redhat.com \
--cc=ksummit-2012-discuss@lists.linux-foundation.org \
--cc=linux-media@vger.kernel.org \
--cc=workshop-2011@linuxtv.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.