public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
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>,
	"Laurent Pinchart" <laurent.pinchart@ideasonboard.com>,
	"Tomasz Figa" <tfiga@chromium.org>,
	"Víctor Jáquez" <vjaquez@igalia.com>,
	"Alexandre Courbot" <acourbot@chromium.org>,
	"Philipp Zabel" <p.zabel@pengutronix.de>
Subject: Re: [RFC] Informal meeting during ELCE to discuss userspace support for stateless codecs
Date: Tue, 23 Oct 2018 11:05:14 +0100	[thread overview]
Message-ID: <20181023110514.55b10594@silica.lan> (raw)
In-Reply-To: <e4f73bea-67a2-2020-bb5a-e4355af6fe70@xs4all.nl>

Em Mon, 22 Oct 2018 22:21:04 +0100
Hans Verkuil <hverkuil@xs4all.nl> escreveu:

> On 10/22/2018 10:17 PM, Hans Verkuil wrote:
> > A quick update:
> > 
> > As said in my previous email: we'll meet at 11 am at the registration desk.
> > From there we go to the Platform 5 Cafe. If that's too crowded/noisy, then
> > we'll try the Sheraton hotel.
> > 
> > Tomasz, I'll ping you on irc when we found a good spot and we can setup the
> > Hangouts meeting.

I'll be a little late to the meeting.

Still at hotel finishing my today's presentation.

Should be heading to EICC soon.

> 
> I forgot to mention: the spec with the Request API and the stateful+stateless
> codec API specification (latest patches from Tomasz and Alexandre) are available
> here:
> 
> https://hverkuil.home.xs4all.nl/request-api/
> 
> Also CC-ed Alexandre and Phillip.
> 
> Regards,
> 
> 	Hans
> 
> > 
> > Hope to see you all tomorrow,
> > 
> > Regards,
> > 
> > 	Hans
> > 
> > On 10/10/2018 07:55 AM, Hans Verkuil wrote:
> >> On 10/08/2018 01:53 PM, 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
> >>
> >> Let's do this Tuesday. Let's meet at the Linux Foundation Registration
> >> Desk at 11:00. I'll try to figure out where we can sit the day before.
> >> Please check your email Tuesday morning for any last minute changes.
> >>
> >> Tomasz, it would be nice indeed if we can get you and Paul in as well
> >> using Hangouts on my laptop.
> >>
> >> I would very much appreciate it if those who have experience with the
> >> userspace support think about this beforehand and make some requirements
> >> list of what you would like to see.
> >>
> >> Regards,
> >>
> >> 	Hans
> >>
> >>>
> >>> or:
> >>>
> >>> Monday from 15:45 onward
> >>>
> >>> 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,
> >>>
> >>> 	Hans
> >>>
> >>
> > 
> 




Cheers,
Mauro

  reply	other threads:[~2018-10-23 18:28 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
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 [this message]
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=20181023110514.55b10594@silica.lan \
    --to=mchehab+samsung@kernel.org \
    --cc=acourbot@chromium.org \
    --cc=ezequiel@collabora.com \
    --cc=hverkuil@xs4all.nl \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=maxime.ripard@free-electrons.com \
    --cc=mchehab@kernel.org \
    --cc=nicolas@ndufresne.ca \
    --cc=p.zabel@pengutronix.de \
    --cc=tfiga@chromium.org \
    --cc=vjaquez@igalia.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox