From mboxrd@z Thu Jan  1 00:00:00 1970
From: Rene Herman <rene.herman@gmail.com>
Subject: Re: ESI MAYA44 driver status
Date: Sat, 22 Sep 2007 08:23:17 +0200
Message-ID: <46F4B4D5.9080108@gmail.com>
References: <87988a970708260156j3bee456djedcea8c74c54991f@mail.gmail.com>	
	<s5hlkbv3mku.wl%tiwai@suse.de>	
	<87988a970709020103h6b527835hc64d045e22e0346f@mail.gmail.com>	
	<46DAAB0B.8060500@gmail.com>	
	<92a12cdb0709021050w2e4791d8te54ab3c2e68e5110@mail.gmail.com>	
	<46DB0B2D.5090401@gmail.com>	
	<92a12cdb0709030144i26385a85mf2ef4b9ee0611c1b@mail.gmail.com>	
	<46DBE1F9.2000308@gmail.com>
	<965c08610709210117q60a3c2fcg81c8af2cc2d4a587@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-15"
Content-Transfer-Encoding: quoted-printable
Return-path: <alsa-devel-bounces@alsa-project.org>
Received: from smtpq2.groni1.gr.home.nl (smtpq2.groni1.gr.home.nl
	[213.51.130.201])
	by alsa0.perex.cz (Postfix) with ESMTP id 7563924703
	for <alsa-devel@alsa-project.org>;
	Sat, 22 Sep 2007 08:24:40 +0200 (CEST)
In-Reply-To: <965c08610709210117q60a3c2fcg81c8af2cc2d4a587@mail.gmail.com>
List-Unsubscribe: <http://mailman.alsa-project.org/mailman/listinfo/alsa-devel>,
	<mailto:alsa-devel-request@alsa-project.org?subject=unsubscribe>
List-Archive: <http://mailman.alsa-project.org/pipermail/alsa-devel>
List-Post: <mailto:alsa-devel@alsa-project.org>
List-Help: <mailto:alsa-devel-request@alsa-project.org?subject=help>
List-Subscribe: <http://mailman.alsa-project.org/mailman/listinfo/alsa-devel>,
	<mailto:alsa-devel-request@alsa-project.org?subject=subscribe>
Sender: alsa-devel-bounces@alsa-project.org
Errors-To: alsa-devel-bounces@alsa-project.org
To: =?ISO-8859-15?Q?Cl=E9ment_Guedez?= <klem.dev@gmail.com>
Cc: alsa-devel@alsa-project.org
List-Id: alsa-devel@alsa-project.org

On 09/21/2007 10:17 AM, Cl=E9ment Guedez wrote:

> Sorry not have answer before, I check my mails so late.
> Also from the architecture Ctirad explains, making a driver for the =

> Maya44 is 'doable', the VIA envy24ht chip is already support, so it =

> would be easier as with the WT192M. The things to do is to fine the =

> documentation of the codec Wolfson WM8776 (join) and adjust the =

> front-end as I do for the WT192M. It's not much work, but it seems =

> that's only I=B2S bus support on this codec and not I=B2C, and I don't ho=
w =

> I=B2S is actually implemented in linux kernel or alsa.
> Also I have some work to finish on the ESI WT192M (db scale for level, =

> some missing input).
> But if you want any help it's ok.

Thanks much the reply. I'm not actually working on this. I thought Adrian =

was going to take it, but I guess not. There's an offer for hardware and =

developer contact from ESI and you'd be a great candidate. Would get you a =

nice Maya44 card... :-)

Rene.