From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: Nicolas Dufresne <nicolas@ndufresne.ca>,
Maxime Ripard <maxime.ripard@free-electrons.com>,
Ezequiel Garcia <ezequiel@collabora.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: [RFC] Informal meeting during ELCE to discuss userspace support for stateless codecs
Date: Wed, 10 Oct 2018 03:41:31 +0300 [thread overview]
Message-ID: <1742364.KYHYimKmd3@avalon> (raw)
In-Reply-To: <b9b2f5ea-8593-d1bf-6d4f-c2efddaa7002@xs4all.nl>
Hi Hans,
On Monday, 8 October 2018 14:53:29 EEST Hans Verkuil wrote:
> Hi all,
>
> I would like to meet up somewhere during the ELCE to discuss userspace
> support for stateless (and perhaps stateful as well?) codecs.
>
> It is also planned as a topic during the summit, but I would prefer to
> prepare for that in advance, esp. since I myself do not have any experience
> writing userspace SW for such devices.
>
> Nicolas, it would be really great if you can participate in this meeting
> since you probably have the most experience with this by far.
>
> Looking through the ELCE program I found two timeslots that are likely to
> work for most of us (because the topics in the program appear to be boring
> for us media types!):
>
> Tuesday from 10:50-15:50
>
> or:
>
> Monday from 15:45 onward
On Tuesday I would prefer 12:20 onward. Monday works for me.
> My guess is that we need 2-3 hours or so. Hard to predict.
>
> The basic question that I would like to have answered is what the userspace
> component should look like? libv4l-like plugin or a library that userspace
> can link with? Do we want more general support for stateful codecs as well
> that deals with resolution changes and the more complex parts of the codec
> API?
>
> I've mailed this directly to those that I expect are most interested in
> this, but if someone want to join in let me know.
>
> I want to keep the group small though, so you need to bring relevant
> experience to the table.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2018-10-10 8:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-08 11:53 [RFC] Informal meeting during ELCE to discuss userspace support for stateless codecs Hans Verkuil
2018-10-08 20:18 ` Kieran Bingham
2018-10-09 9:09 ` Maxime Ripard
2018-10-09 10:29 ` Mauro Carvalho Chehab
2018-10-09 13:59 ` Víctor Jáquez
2018-10-09 12:15 ` Ezequiel Garcia
2018-10-10 0:41 ` Laurent Pinchart [this message]
2018-10-10 1:29 ` Nicolas Dufresne
2018-10-10 4:01 ` Tomasz Figa
2018-10-10 6:55 ` Hans Verkuil
2018-10-15 8:33 ` Tomasz Figa
2018-10-22 21:17 ` Hans Verkuil
2018-10-22 21:21 ` Hans Verkuil
2018-10-23 10:05 ` Mauro Carvalho Chehab
2018-10-23 8:57 ` Sakari Ailus
2018-10-23 10:05 ` Tomasz Figa
2018-10-11 8:27 ` Philipp Zabel
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=1742364.KYHYimKmd3@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=ezequiel@collabora.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=maxime.ripard@free-electrons.com \
--cc=mchehab@kernel.org \
--cc=nicolas@ndufresne.ca \
/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.