From: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
Alexandre Courbot <acourbot@chromium.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Jacopo Mondi <jacopo+renesas@jmondi.org>,
Tomasz Figa <tfiga@chromium.org>
Subject: Re: [ANN] Topics for a media summit in Lyon in October
Date: Fri, 16 Aug 2019 06:37:27 -0300 [thread overview]
Message-ID: <20190816063727.1d86cd29@coco.lan> (raw)
In-Reply-To: <010ba9ce-bac9-6f0c-f128-4f163a7d8ea7@xs4all.nl>
Em Fri, 16 Aug 2019 10:06:30 +0200
Hans Verkuil <hverkuil@xs4all.nl> escreveu:
> Rather then discussing topics for a meeting under the subject 'Lisbon'
> let's start a new thread referring to the right place :-)
>
> I will try to organize a room, either during the ELCE or (if that doesn't
> work) perhaps on the Thursday afterwards. If that's going to be a problem
> for someone, please let me know.
>
> I do need to know how many people I can expect. I have the following
> confirmed attendees (and please reply if you are not listed!):
I'm not planning to go to ELCE this year.
Regards,
Mauro
>
> Alexandre Courbot <acourbot@chromium.org>
> Tomasz Figa <tfiga@chromium.org>
> Jacopo Mondi <jacopo@jmondi.org>
> Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> Hans Verkuil <hverkuil@xs4all.nl>
>
> I know there were more who mentioned on irc that they would attend,
> but it is easier to keep track if I have it in an email.
>
> Topics posted under the previous thread:
>
> Tomasz:
>
> I would want to discuss various v4l2_buffer improvements, e.g.
> - DMA-buf import with plane offsets,
> - unifying the buffer structs for M and non-M formats,
> - ability to import different FDs with offsets for non-M formats if the
> layout matches driver expectations, etc.
>
> Besides that, I would be interested in the general idea on handling
> complex cameras in the Linux kernel in spite of the remaining V4L2
> limitations, e.g.
> - combinatorial explosion of /dev/video nodes,
> - significant ioctl overhead,
> - huge amount of historical legacy making the driver and userspace
> implementations overly difficult and prone to repetitive mistakes,
> - the above also limiting the flexibility of the API - formats, frame
> rates, etc. set using distinct APIs, not covered by Request API, with
> non-failure "negotiation hell", etc.
> - lack of fences, etc.
>
> Jacopo:
>
> Apart from discussing libcamera and hope we could kickstart a review of
> its API, I would like to re-start discussing multiplexed stream support,
> but that would require Sakari to be there, something I'm not certain
> about. Sakari?
>
> Alexandre:
>
> If Collabora/Bootlin is there, I'd certainly want to discuss stateless
> codecs, in particular m2m codec helpers and finalize the specification
> in general.
>
> Regards,
>
> Hans
Thanks,
Mauro
next prev parent reply other threads:[~2019-08-16 9:37 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-16 8:06 [ANN] Topics for a media summit in Lyon in October Hans Verkuil
2019-08-16 8:10 ` Hans Verkuil
2019-08-16 8:22 ` Tomasz Figa
2019-08-16 8:31 ` Hans Verkuil
2019-08-16 9:37 ` Mauro Carvalho Chehab [this message]
2019-08-19 7:44 ` Hans Verkuil
2019-08-19 14:43 ` Ezequiel Garcia
2019-08-19 15:04 ` Laurent Pinchart
2019-08-19 15:24 ` Eugen.Hristev
2019-08-19 15:51 ` Laurent Pinchart
2019-08-28 10:55 ` Hans Verkuil
2019-08-29 0:56 ` Nicolas Dufresne
2019-08-30 7:53 ` Tomasz Figa
2019-09-03 7:21 ` Hans Verkuil
2019-09-03 7:46 ` Alexandre Courbot
2019-09-03 8:02 ` Tomasz Figa
2019-09-03 9:15 ` Niklas Söderlund
2019-09-03 9:35 ` Laurent Pinchart
2019-09-03 10:03 ` Hans Verkuil
2019-09-12 7:28 ` Michael Tretter
2019-09-13 11:27 ` Hans Verkuil
2019-09-13 12:24 ` Daniel Gomez
2019-09-16 8:40 ` Jose Abreu
2019-09-16 8:48 ` Hans Verkuil
2019-09-16 9:54 ` Laurent Pinchart
2019-09-16 10:39 ` Angelo Ribeiro
2019-09-16 10:51 ` Laurent Pinchart
2019-09-16 12:51 ` Angelo Ribeiro
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=20190816063727.1d86cd29@coco.lan \
--to=mchehab+samsung@kernel.org \
--cc=acourbot@chromium.org \
--cc=hverkuil@xs4all.nl \
--cc=jacopo+renesas@jmondi.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=tfiga@chromium.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).