From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Austin, Brian" Subject: Re: Audio mini conference 2014? Date: Tue, 26 Aug 2014 01:47:22 +0000 Message-ID: References: <20140813165517.GB17528@sirena.org.uk> <20140817231021.GQ14537@sirena.org.uk> <20140819172948.GX13288@intel.com> <20140820042109.GY13288@intel.com> <20140820070236.GC13288@intel.com> <20140820084106.GD13288@intel.com> <20140820170100.GD24407@sirena.org.uk> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6972484523817119576==" Return-path: Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1lp0141.outbound.protection.outlook.com [207.46.163.141]) by alsa0.perex.cz (Postfix) with ESMTP id BAA132608EC for ; Tue, 26 Aug 2014 03:47:28 +0200 (CEST) In-Reply-To: <20140820170100.GD24407@sirena.org.uk> Content-Language: en-US List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: alsa-devel-bounces@alsa-project.org Sender: alsa-devel-bounces@alsa-project.org To: Mark Brown Cc: "alsa-devel@alsa-project.org" , Vinod Koul , Tanu Kaskinen , "Handrigan, Paul" , Takashi Iwai , David Henningsson , Daniel Mack List-Id: alsa-devel@alsa-project.org --===============6972484523817119576== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_88454661-E860-48A4-A1EB-250E1C4FA7AC"; protocol="application/pgp-signature"; micalg=pgp-sha512 --Apple-Mail=_88454661-E860-48A4-A1EB-250E1C4FA7AC Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 On Aug 20, 2014, at 12:01 PM, Mark Brown wrote: > On Wed, Aug 20, 2014 at 02:11:07PM +0530, Vinod Koul wrote: >> On Wed, Aug 20, 2014 at 09:33:05AM +0200, Takashi Iwai wrote: >=20 >>> I thought UCM was targeted to this, but not widely used as expected? >=20 >> Chrome uses t but not Android due to licensing issues. What happend = to >> tinyucm? >=20 > The latest Google reference designs use something which is essentially > tinyucm - the configuration is mostly stored in an XML configuration > file which is read at runtime. It's not consistent with what anyone > else uses. Those must be the qcom designs. They use a =93tinyucm" that is xml = based. I would like to see if we could get a consistent UCM for = Android/Chrome/etc. Has this made it into the topics list?=20 --Apple-Mail=_88454661-E860-48A4-A1EB-250E1C4FA7AC Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="signature.asc" Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQEcBAEBCgAGBQJT++cpAAoJEHdXZdGWfiO7P9YH/167TYnBFjVY3ka8xicNPXa6 yQHGnqTn235z9beW4r7eSoZ2UTDONAenVkVzI+Bz2N1rJ3/UkN+p4u83pnnUq7wA 0i2lfWnU575JfKsWXUqSJ2tSjuoOKcbpwu8QnJQYUejIEqlONxd5A0mYOHUXMMh2 yTdEfM7oB0RN7rjSO1S/BILuI87fD/C+jffe4+rNWNmrxtZqdB3lAvCa+8JmFbLO h6gb6YxRMZPo1NaL7QEQIO4M9tDoT/gtPU9yQb8B77Rr0wt0eosyOokt+/1CPI1S l+s2qCDl3g22w8XBCJYKDd2n8bYFEPAvENG8xRDeGBULbHt50dp4096MMlKQEks= =n5WR -----END PGP SIGNATURE----- --Apple-Mail=_88454661-E860-48A4-A1EB-250E1C4FA7AC-- --===============6972484523817119576== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline --===============6972484523817119576==--