From: Benjamin Mugnier <benjamin.mugnier@foss.st.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
<libcamera-devel@lists.libcamera.org>
Cc: <linux-media@vger.kernel.org>,
Kieran Bingham <kieran.bingham@ideasonboard.com>
Subject: Re: [ANNOUNCEMENT] libcamera workshop 2025 - Nice, May 16th
Date: Tue, 22 Apr 2025 12:57:37 +0200 [thread overview]
Message-ID: <751ee8b7-8758-4a98-8b3d-eb91f1f90b99@foss.st.com> (raw)
In-Reply-To: <20250325102750.GE20035@pendragon.ideasonboard.com>
Hi Laurent,
On 3/25/25 11:27, 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.
If it's not too late I'd like to attend to the libcamera workshop too :)
Unfortunately I didn't dive in libcamera yet to talk about a specific
topic. We plan to support ST sensors in libcamera, and this is a great
opportunity for me to see libcamera's evolution.
Thanks a lot.
--
Regards,
Benjamin
next prev parent reply other threads:[~2025-04-22 10:58 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
2025-04-22 10:57 ` Benjamin Mugnier [this message]
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=751ee8b7-8758-4a98-8b3d-eb91f1f90b99@foss.st.com \
--to=benjamin.mugnier@foss.st.com \
--cc=kieran.bingham@ideasonboard.com \
--cc=laurent.pinchart@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