From: Takashi Iwai Subject: Re: how to detect big/little endian in a driver module? Date: Thu, 02 May 2002 11:25:37 +0200 Sender: alsa-devel-admin@lists.sourceforge.net Message-ID: References: <200205010113.g411DZ913510@op.net> Mime-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII Return-path: Received: from Cantor.suse.de (ns.suse.de [213.95.15.193]) by alsa.alsa-project.org (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id LAA09193 for ; Thu, 2 May 2002 11:25:47 +0200 Received: from Hermes.suse.de (Charybdis.suse.de [213.95.15.201]) by Cantor.suse.de (Postfix) with ESMTP id 2D29C1EABA for ; Thu, 2 May 2002 11:25:41 +0200 (MEST) In-Reply-To: <200205010113.g411DZ913510@op.net> Errors-To: alsa-devel-admin@lists.sourceforge.net List-Help: List-Post: List-Subscribe: , List-Unsubscribe: , List-Archive: To: alsa-devel@alsa-project.org List-Id: alsa-devel@alsa-project.org At Tue, 30 Apr 2002 21:13:35 -0400, Paul Davis wrote: > > whats the preferred macro/method for discovering if we are on > a big or little-endian system from within driver code? SNDRV_{LITTLE|BIG}_ENDIAN defined in asound.h. Takashi _______________________________________________________________ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: bandwidth@sourceforge.net