public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: David Plowman <david.plowman@raspberrypi.com>
Cc: libcamera-devel@lists.libcamera.org, linux-media@vger.kernel.org,
	Kieran Bingham <kieran.bingham@ideasonboard.com>
Subject: Re: [ANNOUNCEMENT] libcamera workshop 2025 - Nice, May 16th
Date: Tue, 15 Apr 2025 10:18:20 +0300	[thread overview]
Message-ID: <20250415071820.GH15367@pendragon.ideasonboard.com> (raw)
In-Reply-To: <CAHW6GYK2o8G=ANe8H=Mpx08gF39otqrtwzKbHW+vXaQcPjuUAA@mail.gmail.com>

Hi David,

On Tue, Mar 25, 2025 at 01:46:58PM +0000, David Plowman wrote:
> Hi Laurent
> 
> Thanks for the announcement and yes, Naush and I are planning to attend. I
> certainly fancy a couple of days in Nice, soaking up the atmosphere on the
> Promenade des Anglais! (don't tell my employer)

I realized I haven't replied to acknowledge your registration, so here's
the official confirmation. We will be happy to see you and Naush in
Nice. Thank you for submitting discussion topics, we will publish the
agenda draft close to the event.

> Some topics we'd like to cover:
> 
> 1. Bayer re-processing.
> 
> Yes, we've talked about this a number of times before. On this occasion I'd
> like to agree an outline approach that is sufficient for us to go away and
> implement something. It doesn't have to be perfect and complete, but it has
> to be enough to produce some working code that we broadly think is in the
> right direction. It should take us significantly closer to having some code
> that we can consider rolling out to Pi users.
> 
> 2. Startup frames.
> 
> Another old chestnut! I'm not really sure why it got stuck, it doesn't even
> seem to me like it should be all that controversial. It would be nice to be
> able to help Pi users on lower-spec devices by not allocating memory
> buffers that they don't have space for!
> 
> (For those who aren't familiar with this topic, the problem is that
> pipelines, ours included, may want to "swallow" a few frames when they
> start, and need to allocate extra camera buffers to do this. We'd rather
> the application buffers were used for this purpose, but it means those
> early requests would have to be flagged as "startup" aka. "do not use
> me" frames.)
> 
> 3. Per-frame controls.
> 
> We did a complete implementation for the Pi platform back in 2022, I'm sure
> some of you will recall. We'd really like to advance this again with a view
> to having something that we can give to Raspberry Pi users. I realise it
> may interact with work that was going on to split out the controls from the
> request queue, is that a topic that needs addressing?
> 
> Looking forward to seeing everyone there!
> 
> Thanks
> David
> 
> 
> On Tue, 25 Mar 2025 at 10:28, Laurent Pinchart wrote:
> 
> > Hello everybody,
> >
> > Another year, another libcamera workshop. After the previous editions in
> > Paris, Brussels and Vienna, we will organize the next workshop in Nice
> > on Friday the 16th of May. The event will be hosted by Embedded Recipes
> > ([1]) as part of their workshops day ([2]).
> >
> > This year, our workshop will be colocated with the Pipewire workshop on
> > the same day and at the same venue (but a different room), to facilitate
> > discussions about topics that span libcamera and Pipewire. The Linux
> > Media Summit will also be organized in a nearby location on Tuesday the
> > 13th ([3]).
> >
> > If you would like to attend, please register your interest by replying
> > to this e-mail, and indicate if you have any discussion topics you would
> > like to include in the schedule. We will draft and circulate an agenda
> > in the next few weeks after receiving topic proposals. If registrations
> > exceed our capacity, priority will be given based on topic submissions.
> >
> > The event will be free of charge for attendees.
> >
> > [1] https://embedded-recipes.org/2025/
> > [2] https://embedded-recipes.org/2025/workshops/
> > [3] https://lore.kernel.org/r/044f2fa6-a245-4ae5-b9de-7a2e8831ccd6@xs4all.nl

-- 
Regards,

Laurent Pinchart

  parent reply	other threads:[~2025-04-15  7:18 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-25 10:27 [ANNOUNCEMENT] libcamera workshop 2025 - Nice, May 16th Laurent Pinchart
2025-03-25 12:03 ` Hans de Goede
2025-04-15  7:17   ` Laurent Pinchart
2025-03-25 12:20 ` Hu, Jerry W
2025-03-25 12:37   ` Laurent Pinchart
2025-03-25 12:43     ` Hu, Jerry W
2025-04-15  7:23     ` Laurent Pinchart
2025-03-25 18:12 ` Nicolas Dufresne
2025-03-26  8:13   ` Jacopo Mondi
2025-03-28 20:10     ` Nicolas Dufresne
2025-04-15  7:20   ` Laurent Pinchart
2025-04-08  5:31 ` Niklas Söderlund
2025-04-15  7:15   ` Laurent Pinchart
     [not found] ` <2ff6c67b-7a1a-463a-8f57-8886fc66fbae@ti>
2025-04-15  7:04   ` Devarsh Thakkar
2025-04-15  7:14     ` Laurent Pinchart
     [not found] ` <CAHW6GYK2o8G=ANe8H=Mpx08gF39otqrtwzKbHW+vXaQcPjuUAA@mail.gmail.com>
2025-04-15  7:18   ` Laurent Pinchart [this message]
2025-04-22 10:57 ` Benjamin Mugnier
2025-04-22 11:39   ` Laurent Pinchart
2025-04-22 11:12 ` Kieran Bingham
2025-04-22 14:10 ` Josuah Demangeon
2025-04-22 14:40   ` Laurent Pinchart
2025-04-22 14:42   ` Laurent Pinchart
2025-05-05 14:36 ` Mattijs Korpershoek
2025-05-05 16:57   ` Laurent Pinchart
2025-05-07  8:28 ` Mauro Carvalho Chehab
2025-05-07  9:19   ` Laurent Pinchart
2025-05-07 10:33     ` Ricardo Ribalda Delgado
2025-05-07 11:43       ` Laurent Pinchart
  -- strict thread matches above, loose matches on Subject: below --
2025-04-14  9:16 Andrej Gardijan
2025-04-14 12:38 ` Laurent Pinchart
2025-04-14 13:12   ` Andrej Gardijan
2025-05-14 19:20 Mario Bergeron
2025-05-14 21:33 ` 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:
  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=20250415071820.GH15367@pendragon.ideasonboard.com \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=david.plowman@raspberrypi.com \
    --cc=kieran.bingham@ideasonboard.com \
    --cc=libcamera-devel@lists.libcamera.org \
    --cc=linux-media@vger.kernel.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