[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20260201202200.GX3374091@killaraus>
Date: Sun, 1 Feb 2026 22:22:00 +0200
From: Laurent Pinchart <laurent.pinchart@...asonboard.com>
To: Oleksandr Natalenko <oleksandr@...alenko.name>
Cc: Jarkko Sakkinen <jarkko@...nel.org>, linux-media@...r.kernel.org,
jani.nikula@...ux.intel.com, anisse@...ier.eu,
Mauro Carvalho Chehab <mchehab@...nel.org>,
Hans Verkuil <hverkuil@...nel.org>,
Sakari Ailus <sakari.ailus@...ux.intel.com>,
Jacopo Mondi <jacopo.mondi@...asonboard.com>,
Ricardo Ribalda <ribalda@...omium.org>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH] media: Virtual camera driver
On Sun, Feb 01, 2026 at 09:14:54PM +0100, Oleksandr Natalenko wrote:
> On neděle 1. února 2026 21:06:49, středoevropský standardní čas Laurent Pinchart wrote:
> > > There is a notable user base for v4l2-loopback. It is the defacto choice
> > > for streaming phone cams.
> >
> > This will then likely face the same hurdles as v4l2-loopback, the main
> > one being that camera support should be upstreamed with proper drivers
> > instead of a closed-source userspace daemon.
> >
> > For phone cameras, the way forward upstream is libcamera. Until kernel
> > drivers for ISPs are available, the soft ISP is a stop-gap solution. It
> > recently gained GPU acceleration support (with work to improve image
> > quality with additional algorithms ongoing).
>
> My use-case for v4l2loopback is to stream a webcam from one machine to
> another (with the help of ffmpeg). Is this covered by something other
> than v4l2loopback now?
On the transmitting side I assume you don't use v4l2loopback. On the
receiving side, the recommened option is PipeWire.
--
Regards,
Laurent Pinchart
Powered by blists - more mailing lists