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: install bluez-hardware.conf
Date: Fri, 14 Feb 2025 10:02:09 +0100	[thread overview]
Message-ID: <20250214090209.2797642-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20250129151219.2235308-1-m.tretter@pengutronix.de>

Thanks, applied as e762021f1dfea36e37df22dde38a848a3e15168a.

Michael

[sent from post-receive hook]

On Fri, 14 Feb 2025 10:02:09 +0100, Michael Tretter <m.tretter@pengutronix.de> wrote:
> The bluez-hardware.conf contains some device quirks which will be
> applied by the bluez plugin.
> 
> Install bluez-hardware.conf if the plugin is installed.
> 
> Signed-off-by: Michael Tretter <m.tretter@pengutronix.de>
> Message-Id: <20250129151219.2235308-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 a0db62facbe0..29d209720336 100644
> --- a/rules/pipewire.make
> +++ b/rules/pipewire.make
> @@ -262,6 +262,9 @@ endif
>  ifdef PTXCONF_PIPEWIRE_PULSEAUDIO
>  	@$(call install_alternative, pipewire, 0, 0, 644, /usr/share/pipewire/pipewire-pulse.conf)
>  endif
> +ifdef PTXCONF_PIPEWIRE_BLUETOOTH
> +	@$(call install_alternative, pipewire, 0, 0, 644, /usr/share/spa-0.2/bluez5/bluez-hardware.conf)
> +endif
>  
>  ifdef PTXCONF_PIPEWIRE_GSTREAMER
>  	@$(call install_lib, pipewire, 0, 0, 644, gstreamer-1.0/libgstpipewire)



      reply	other threads:[~2025-02-14  9:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-29 15:12 [ptxdist] [PATCH] " Michael Tretter
2025-02-14  9:02 ` 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=20250214090209.2797642-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