mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Michael Tretter <m.tretter@pengutronix.de>
Subject: Re: [ptxdist] [APPLIED] pipewire: disable v4l2 integration
Date: Fri, 22 Apr 2022 12:00:58 +0200	[thread overview]
Message-ID: <20220422100058.3831749-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20220421151942.342129-1-m.tretter@pengutronix.de>

Thanks, applied as 3cef96ff21ac02a7eba7e69e784539ced938eb70.

Michael

[sent from post-receive hook]

On Fri, 22 Apr 2022 12:00:58 +0200, Michael Tretter <m.tretter@pengutronix.de> wrote:
> PipeWire allows to emulate V4L2 devices by intercepting the device
> ioctls and handling them in PipeWire. This is unrelated to the V4L2
> backend, which allows to use V4L2 devices in PipeWire.
> 
> Disable the integration, because applications should use PipeWire
> directly instead of using the V4L2 API.
> 
> Signed-off-by: Michael Tretter <m.tretter@pengutronix.de>
> Message-Id: <20220421151942.342129-1-m.tretter@pengutronix.de>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
> 
> diff --git a/rules/pipewire.make b/rules/pipewire.make
> index 9fd3d4d40658..495c5188687c 100644
> --- a/rules/pipewire.make
> +++ b/rules/pipewire.make
> @@ -75,7 +75,7 @@ PIPEWIRE_CONF_OPT	:= \
>  	-Dman=disabled \
>  	-Dpipewire-alsa=enabled \
>  	-Dpipewire-jack=disabled \
> -	-Dpipewire-v4l2=enabled \
> +	-Dpipewire-v4l2=disabled \
>  	-Dpw-cat=enabled \
>  	-Draop=$(call ptx/endis,PTXCONF_PIPEWIRE_RAOP)d \
>  	-Droc=disabled \
> @@ -176,7 +176,6 @@ endif
>  ifdef PTXCONF_PIPEWIRE_PW_TOP
>  	@$(call install_copy, pipewire, 0, 0, 755, -, /usr/bin/pw-top)
>  endif
> -	@$(call install_copy, pipewire, 0, 0, 755, -, /usr/bin/pw-v4l2)
>  	@$(call install_copy, pipewire, 0, 0, 755, -, /usr/bin/spa-acp-tool)
>  	@$(call install_copy, pipewire, 0, 0, 755, -, /usr/bin/spa-inspect)
>  	@$(call install_copy, pipewire, 0, 0, 755, -, /usr/bin/spa-json-dump)
> @@ -193,8 +192,6 @@ endif
>  		$(call install_lib, pipewire, 0, 0, 644, \
>  			pipewire-0.3/libpipewire-module-$(module))$(ptx/nl))
>  
> -	@$(call install_lib, pipewire, 0, 0, 644, pipewire-0.3/v4l2/libpw-v4l2)
> -
>  	@$(foreach module, $(PIPEWIRE_SPA_MODULES), \
>  		$(call install_lib, pipewire, 0, 0, 644, \
>  			spa-0.2/$(module))$(ptx/nl))

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de


      reply	other threads:[~2022-04-22 10:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-21 15:19 [ptxdist] [PATCH] " Michael Tretter
2022-04-22 10:00 ` Michael Olbrich [this message]

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=20220422100058.3831749-1-m.olbrich@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=m.tretter@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    /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