All of
 help / color / mirror / Atom feed
From: Laurent Pinchart <>
To: Hans Verkuil <>
Cc: "Linux Media Mailing List" <>,
	"Alexandre Courbot" <>,
	"Tomasz Figa" <>,
	"Ezequiel Garcia" <>,
	"Daniel Gomez" <>,
	"Eugen Hristev" <>,
	"Dafna Hirschfeld" <>,
	"Helen Koike" <>,
	"Jacopo Mondi" <>,
	"Niklas Söderlund" <>,
	"Nicolas Dufresne" <>,
	"Dave Stevenson" <>
Subject: Re: [ANN v2] Media sessions in Lyon in October: libcamera
Date: Sun, 20 Oct 2019 14:10:14 +0300	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Hi Hans,

Thank you for handling the announcement.

On Thu, Oct 17, 2019 at 01:16:20PM +0200, Hans Verkuil wrote:
> (Just updated the attendee list for this meeting, no other changes)
> Hi all,
> Since we have three separate half-day sessions for different topics I decided
> to split the announcement for this in three emails as well, so these things
> can be discussed in separate threads.
> All sessions are in room Terreaux VIP Lounge - Level 0.
> There is a maximum of 15 people.
> The second session deals with libcamera and is on Wednesday morning
> from 9:00 to 13:00.
> Attendees for this session:
> Nicolas Dufresne <>
> Tomasz Figa <>
> Ezequiel Garcia <>
> Dafna Hirschfeld <>
> Eugen Hristev <>
> Jacopo Mondi <>
> Laurent Pinchart <>
> Niklas Söderlund <>
> Dave Stevenson <>
> Hans Verkuil <>
> That's 10 people.
> Planning to use libcamera, but willing to give up their seat if needed:
> Daniel Gomez <>
> Helen Koike <>
> Just interested:
> Boris Brezillon <>
> Alexandre Courbot <>
> If I missed someone, or you are on the list but won't attend after all, then
> please let me know.
> Attendees: it is probably useful if you let us know whether you have to
> join this meeting because you plan to use libcamera, or if you are 'just
> interested'. After the libcamera presentation on Tuesday afternoon we
> should know how many of the 'just interested' list can join.
> Agenda:
> TBD by Laurent.

The two main items we would like to discuss are:

API review

Following Jacopo's talk on Tuesday that will kickstart the public API
review, we would like to receive feedback from all attendees on the
libcamera APIs. This includes the public API towards applications and
the API toward the Image Processing Algorithms (IPA, also known as 3A).
The internal APIs between libcamera components and helpers, as well as
the Android camera HAL implementation, can also be discussed given
interest from the audience if time permits.

The libcamera API is documented in the source code using doxygen. A
nightly build of the documentation can be found at Please note that the built
documentation covers all libcamera classes, making it a bit difficult to
tell the public API apart from the internal APIs. We will try to address
this problem this week.

Use cases sharing

The libcamera project aims at supporting a wide range of use cases, even
if we need to limit the scope of the first release. Our experience with
camera support in Linux systems give us a good but still restricted view
of the uses, and we would like to discuss additional use cases with the
audience. If you have camera-related needs, from simple to crazy, we
want to hear about them.

Please all feel free to propose other topics that you would find of
interest. We will finalise the agenda this week.


Laurent Pinchart

  reply	other threads:[~2019-10-20 11:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-17 11:16 [ANN v2] Media sessions in Lyon in October: libcamera Hans Verkuil
2019-10-20 11:10 ` Laurent Pinchart [this message]
2019-10-20 20:13 ` Ezequiel Garcia
2019-10-21  6:36   ` Helen Koike
2019-10-28 22:03     ` Daniel Gomez
2019-10-28 22:18       ` Hans Verkuil
2019-10-29 14:20       ` Laurent Pinchart

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \

* 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.