From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Mack Subject: Re: [PATCH 2/2] alsa-lib: bring pcm.h and pcm.c in sync with the kernel list Date: Fri, 05 Apr 2013 09:45:09 +0200 Message-ID: <515E8105.9070607@gmail.com> References: <1364427144-30036-1-git-send-email-zonque@gmail.com> <1364427144-30036-2-git-send-email-zonque@gmail.com> <51538493.40309@sonarnerd.net> <7.0.0.16.2.20130327213632.13b07718@akdesigninc.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail-bk0-f46.google.com (mail-bk0-f46.google.com [209.85.214.46]) by alsa0.perex.cz (Postfix) with ESMTP id E5E1E265F5A for ; Fri, 5 Apr 2013 09:45:14 +0200 (CEST) Received: by mail-bk0-f46.google.com with SMTP id je9so1932828bkc.5 for ; Fri, 05 Apr 2013 00:45:14 -0700 (PDT) In-Reply-To: <7.0.0.16.2.20130327213632.13b07718@akdesigninc.com> 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: Andreas Koch Cc: Jussi Laako , tiwai@suse.de, clemens@ladisch.de, alsa-devel@alsa-project.org, demian@auraliti.com, ray@auraliti.com List-Id: alsa-devel@alsa-project.org Hi Andreas, On 28.03.2013 05:58, Andreas Koch wrote: >> Am I right to assume that in your case it's the same as for DoP, >> IOW, oldest in MSB? > > Good point - thanks for bringing it up - another can of worms. > With Windows having a little endian philosophy we started early on > with the first DSD workstation by putting the oldest sample in the > LSB position. ASIO came along and adopted the same thing, but then > extended support for the opposite as well. Rigisystems (offering OEM > modules for USB audio) came along about a year ago and insisted that > there is only their way, i.e. putting the oldest bit in the MSB > position. I tried to explain to them that there are already hundreds > of products out in the market that do it differently, but that didn't > matter to them. The result is that now we have implementations with > both. Up until now that was not a huge issue, because there is no > generic Windows driver and every hardware manufacturer had to have a > custom driver. > Now of course, with your heroic effort in creating a generic driver > that would help everyone, we have a mess. Some DACs expect little > endian (mine and others as well) and others (all that are based on > Rigisystems modules) big endian positions. > > Since the time I had the discussions with Rigisystems I didn't have > any further communication with them. Maybe it is a good idea to touch > base with them again and find out what the latest is. I will try my > contact there and let you know. Did you hear back from them yet? Do you think we should allocate types for Big Endian DOP formats? Thanks, Daniel