From mboxrd@z Thu Jan 1 00:00:00 1970 From: stan Subject: Re: Help Date: Thu, 24 Jul 2008 09:53:18 -0700 Message-ID: <4888B37E.7010604@cox.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from fed1rmmtao101.cox.net (fed1rmmtao101.cox.net [68.230.241.45]) by alsa0.perex.cz (Postfix) with ESMTP id 8A0F72493A for ; Thu, 24 Jul 2008 18:53:20 +0200 (CEST) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: alsa-devel-bounces@alsa-project.org Errors-To: alsa-devel-bounces@alsa-project.org To: Sudeept Prusti Cc: alsa-devel@alsa-project.org List-Id: alsa-devel@alsa-project.org Sudeept Prusti wrote: > Hi all, > > As i am working on ALSA for last few weeks.Can anyone guide where can i get > moe informative things on ALSA internals (Internally how alsa works). > Two possibilities: First is the alsa web site, http://www.alsa-project.org There are tutorials and api definitions. I recall seeing an overview like you are asking for, as well as how to write a driver. These are mostly out of date, though substantially correct. For some reason I'm unable to reach it right now, so I can't give the links. Second is the source. You can download the alsa-lib and alsa-driver source archives. That allows you to look at current implementations and see how things are done. > Could anyone suggest what are validation scenario on alsa driver flow. > > Thanks a lot. > > Awaiting for response soon. > > Regards, > Sudeept >