From: Mark Brown <broonie@kernel.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: ALSA development <alsa-devel@alsa-project.org>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Subject: Re: [alsa-devel] [PATCH] ASoC: change 'HDMI/DP, pcm=' to 'HDMI/DP, pcm=' Jack control names
Date: Fri, 25 Oct 2019 15:49:52 +0100 [thread overview]
Message-ID: <20191025144952.GF4568@sirena.org.uk> (raw)
In-Reply-To: <s5hwocsucfp.wl-tiwai@suse.de>
[-- Attachment #1.1: Type: text/plain, Size: 1080 bytes --]
On Fri, Oct 25, 2019 at 04:28:26PM +0200, Takashi Iwai wrote:
> Jaroslav Kysela wrote:
> > Dne 25. 10. 19 v 16:06 Takashi Iwai napsal(a):
> > > Well, that's obviously against our dont-breaking-user-space rule.
> > > The UCM profiles have been widely used on Chromebooks, and they can't
> > > upgrade easily.
> > > So, I believe this is a case where we have to live with messes.
> > If we speak about Google's kernels, they can apply a revert (depends
> > on their upgrade/maintenance policy). If users use the standard Linux
> > distributions, then we are fine, don't we?
> No, we can't break the already existing user-space. That's what Linus
> suggested repeatedly over years, too.
I agree. There's some systems where we can get away with
incompatible changes as realistically the users are doing full
system upgrades and don't care but the Chromebooks definitely
aren't one of them, we've had issues reported with breakages on
them due to changes with the x86 DSP firmwares. It's mainly
people sideloading a regular Linux userspace along with the
ChromeOS kernel AIUI.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 161 bytes --]
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2019-10-25 14:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-25 12:30 [alsa-devel] [PATCH] ASoC: change 'HDMI/DP, pcm=' to 'HDMI/DP, pcm=' Jack control names Jaroslav Kysela
2019-10-25 12:38 ` Takashi Iwai
2019-10-25 13:57 ` Jaroslav Kysela
2019-10-25 14:06 ` Takashi Iwai
2019-10-25 14:18 ` Jaroslav Kysela
2019-10-25 14:28 ` Takashi Iwai
2019-10-25 14:39 ` Jaroslav Kysela
2019-10-25 16:11 ` Takashi Iwai
2019-10-25 17:04 ` Jaroslav Kysela
2019-10-25 18:02 ` Kai Vehmanen
2019-10-25 21:03 ` Jaroslav Kysela
2019-10-26 7:37 ` Takashi Iwai
2019-10-26 17:11 ` Jaroslav Kysela
2019-10-28 14:23 ` Takashi Iwai
2019-10-25 14:49 ` Mark Brown [this message]
2019-10-25 12:44 ` Kai Vehmanen
2019-10-25 14:04 ` Jaroslav Kysela
2019-10-25 14:35 ` Pierre-Louis Bossart
2019-10-25 14:43 ` Jaroslav Kysela
2019-10-25 16:27 ` Peter Ujfalusi
2019-10-25 17:48 ` Kai Vehmanen
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=20191025144952.GF4568@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=tiwai@suse.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 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.