All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: Wren Turkal <wt@penguintechs.org>,
	linux-media <linux-media@vger.kernel.org>
Subject: Re: v4l2loopback and v4l2-mem2mem framework
Date: Thu, 4 Mar 2021 16:34:44 -0300	[thread overview]
Message-ID: <CAAEAJfAGq=YvXZcBD_-w8OdZB1ZX_P3VB1y3CQSoazjzNSqGVQ@mail.gmail.com> (raw)
In-Reply-To: <20210304201055.78145b04@coco.lan>

On Thu, 4 Mar 2021 at 16:11, Mauro Carvalho Chehab
<mchehab+huawei@kernel.org> wrote:
>
> Em Tue, 2 Mar 2021 05:01:16 -0300
> Ezequiel Garcia <ezequiel@vanguardiasur.com.ar> escreveu:
>
> > Hi Wren,
> >
> > How about you submit the loopback driver for integration in mainline?
> > We can review the driver, give feedback and help you get it merged.
>
> Please, don't top post.
>
> The loopback driver is not something that could be merged. It was
> already submitted a few times.
>
> One of the main issues is that userspace may sleep, and this could cause
> some bad effects and even hangups due to V4L2 core and VB2 mutex and
> spin locks.
>

Can you elaborate on this?

I always felt that it's a shame for something so popular as the loopback
to be out-of-tree and unsupported.

Thanks,
Ezequiel

  reply	other threads:[~2021-03-04 19:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-28 22:07 v4l2loopback and v4l2-mem2mem framework Wren Turkal
2021-03-01 20:27 ` Wren Turkal
2021-03-02  8:01   ` Ezequiel Garcia
2021-03-04 19:10     ` Mauro Carvalho Chehab
2021-03-04 19:34       ` Ezequiel Garcia [this message]
2021-03-04 22:19       ` Wren Turkal
     [not found]   ` <CAAEAJfCSfwxv5NyaH05Dfiw4wm6vGxL_ajoFup6r-GKx_VymJA@mail.gmail.com>
     [not found]     ` <86f1dd6b-7593-adba-b5a6-abf4f8e35d8b@penguintechs.org>
2021-03-02 22:08       ` Wren Turkal
2021-03-03 22:41         ` Nicolas Dufresne
2021-03-03 23:41           ` Wren Turkal
2021-03-04  9:58             ` Hans Verkuil
2021-03-04 22:17               ` Wren Turkal

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='CAAEAJfAGq=YvXZcBD_-w8OdZB1ZX_P3VB1y3CQSoazjzNSqGVQ@mail.gmail.com' \
    --to=ezequiel@vanguardiasur.com.ar \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab+huawei@kernel.org \
    --cc=wt@penguintechs.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 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.