From alsa-devel-owner@alsa.jcu.cz  Mon Mar  8 20:04:13 1999
Received: from sunu450.rz.ruhr-uni-bochum.de (sunu450.rz.ruhr-uni-bochum.de [134.147.222.33])
	by marvin.jcu.cz (8.9.1a/8.9.1) with SMTP id UAA15749
	for <alsa-devel@alsa.jcu.cz>; Mon, 8 Mar 1999 20:03:26 +0100
Received: (qmail 959 invoked from network); 8 Mar 1999 19:03:25 -0000
Received: from dialppp-7-142.rz.ruhr-uni-bochum.de (HELO localhost) (mail@134.147.7.142)
  by mailhost.rz.ruhr-uni-bochum.de with SMTP; 8 Mar 1999 19:03:25 -0000
Received: from brinkmds by localhost with local (Exim 2.11 #1 (Debian))
	id 10K5M0-0000JN-00; Mon, 8 Mar 1999 20:06:16 +0100
Message-ID: <19990308200616.F391@ruhr-uni-bochum.de>
Date: Mon, 8 Mar 1999 20:06:16 +0100
From: Marcus Brinkmann <Marcus.Brinkmann@ruhr-uni-bochum.de>
To: alsa-devel@alsa.jcu.cz
Subject: non-i386 architecture support?
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Reply-To: alsa-devel@alsa.jcu.cz
Sender: alsa-devel-owner@alsa.jcu.cz
Precedence: list


Hello,

one concerned user of a different architecture asked me if sufficient
considerations have been made for support of non-i386 architectures in Alsa
design.

Are non-i386 people working on Alsa? Should you ask non-i386 people to join
and encourage them to revise the code for i386-ism's?

I am not worried about driver stuff, as the kernel driver/library layer
concept is rock solid, but what about endianess and bits (32/64)?

Thanks,
Marcus

-- 
`Rhubarb is no Egyptian god.' Debian http://www.debian.org   finger brinkmd@ 
Marcus Brinkmann              GNU    http://www.gnu.org     master.debian.org
Marcus.Brinkmann@ruhr-uni-bochum.de                        for public  PGP Key
http://homepage.ruhr-uni-bochum.de/Marcus.Brinkmann/       PGP Key ID 36E7CD09

