Alsa-Devel Archive on lore.kernel.org
 help / color / Atom feed
From: Curtis Malainey <cujomalainey@google.com>
To: Jaroslav Kysela <perex@perex.cz>
Cc: ALSA development <alsa-devel@alsa-project.org>,
	Dylan Reid <dgreid@google.com>, Takashi Iwai <tiwai@suse.com>,
	Jimmy Cheng-Yi Chiang <cychiang@google.com>
Subject: Re: [alsa-devel] alsa-ucm-conf via portage on arm
Date: Fri, 14 Feb 2020 10:45:06 -0800
Message-ID: <CAOReqxgK3BPnm3ds0fvMjc4q0mUnDgK5E1X2tV2nXz3uYwymLA@mail.gmail.com> (raw)
In-Reply-To: <23daf96d-f854-f01f-bc4e-2afc47299c0a@perex.cz>

Not yet, that was going to be my follow up. I just wanted to make sure
there is not ALSA restriction first. I assumed there wasn't but
figured better safe than sorry. I will follow up with Lars.

On Fri, Feb 14, 2020 at 10:39 AM Jaroslav Kysela <perex@perex.cz> wrote:
>
> Dne 14. 02. 20 v 19:23 Curtis Malainey napsal(a):
> > Hello Takashi and Jaroslav,
> >
> > There appears to be a upstream package issue for alsa-ucm-conf in that
> > portage seems to have it restricted to x86 and amd64 platforms. Given
> > the nature of the ucms I figure this is an error and was hoping you
> > know who to speak to in order to resolve this. If this isn't an error
> > what can I do to help get the repo to state in which it is supported
> > on arm/arm64?
> >
> > See https://gitweb.gentoo.org/repo/gentoo.git/commit/media-libs/alsa-ucm-conf/alsa-ucm-conf-1.2.1.2.ebuild?id=dd3e0570e2465639431709bce0410b787d312bbe
> >
> > Curtis
>
> It's Gentoo specific and you see signed-off-by in this commit.
>
> Did you contact this person (Lars Wendler) from Gentoo?
>
>                                         Jaroslav
>
> --
> Jaroslav Kysela <perex@perex.cz>
> Linux Sound Maintainer; ALSA Project; Red Hat, Inc.
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel

      reply index

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-14 18:23 Curtis Malainey
2020-02-14 18:38 ` Jaroslav Kysela
2020-02-14 18:45   ` Curtis Malainey [this message]

Reply instructions:

You may reply publically 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=CAOReqxgK3BPnm3ds0fvMjc4q0mUnDgK5E1X2tV2nXz3uYwymLA@mail.gmail.com \
    --to=cujomalainey@google.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=cychiang@google.com \
    --cc=dgreid@google.com \
    --cc=perex@perex.cz \
    --cc=tiwai@suse.com \
    /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

Alsa-Devel Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/alsa-devel/0 alsa-devel/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 alsa-devel alsa-devel/ https://lore.kernel.org/alsa-devel \
		alsa-devel@alsa-project.org
	public-inbox-index alsa-devel

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.alsa-project.alsa-devel


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git