From: Takashi Iwai Subject: Re: Sizeof int in Alsa Date: Thu, 10 May 2012 07:42:42 +0200 Message-ID: References: <201205092234.20375.gineera@aspect135.co.uk> Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mx2.suse.de (cantor2.suse.de [195.135.220.15]) by alsa0.perex.cz (Postfix) with ESMTP id C8E4210B99E for ; Thu, 10 May 2012 07:42:42 +0200 (CEST) In-Reply-To: <201205092234.20375.gineera@aspect135.co.uk> 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: Alan Horstmann Cc: alsa-devel@alsa-project.org List-Id: alsa-devel@alsa-project.org At Wed, 9 May 2012 22:34:20 +0100, Alan Horstmann wrote: > > Hi, > > I have often wondered whether Alsa had an intrinsic requirement that an int > would always be at least 32-bit, but been unable to find a clear statement > with web searches. > > Looking recently at snd_pcm_hw_params_set_rate(), for example, the rate value > parameter is unsigned int, which suggests to me that it would be broken with > 16-bit ints; is it correct then to deduce that Alsa does not support 16-bit > int platforms? Right. Linux itself doesn't support 16bit int, so neither ALSA does. Takashi