From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from bombadil.infradead.org ([198.137.202.133]:57340 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726103AbeJIRpt (ORCPT ); Tue, 9 Oct 2018 13:45:49 -0400 Date: Tue, 9 Oct 2018 07:29:23 -0300 From: Mauro Carvalho Chehab To: Hans Verkuil Cc: Nicolas Dufresne , Maxime Ripard , Ezequiel Garcia , Mauro Carvalho Chehab , Linux Media Mailing List Subject: Re: [RFC] Informal meeting during ELCE to discuss userspace support for stateless codecs Message-ID: <20181009072904.19a7a8f2@coco.lan> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-media-owner@vger.kernel.org List-ID: Em Mon, 8 Oct 2018 13:53:29 +0200 Hans Verkuil escreveu: > 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 Should work. There's an speech from Julia that could be interesting, related to the usage of AI for improving the quality of patches that could be interesting. > > or: > > Monday from 15:45 onward I won't be able to attend on Monday. > > 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 Thanks, Mauro