From: Takashi Iwai Subject: Re: Skinny (and very skinny) digital packaging Date: Wed, 10 Aug 2005 12:05:39 +0200 Message-ID: References: <42F929AE.3010703@redfish-solutions.com> Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Return-path: Received: from mx2.suse.de (mx2.suse.de [195.135.220.15]) by alsa.jcu.cz (ALSA's E-mail Delivery System) with ESMTP id 3869616C for ; Wed, 10 Aug 2005 12:05:40 +0200 (MEST) In-Reply-To: <42F929AE.3010703@redfish-solutions.com> Sender: alsa-devel-admin@lists.sourceforge.net Errors-To: alsa-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: Philip Prindeville Cc: alsa-devel@alsa-project.org List-Id: alsa-devel@alsa-project.org At Tue, 09 Aug 2005 16:09:50 -0600, Philip Prindeville wrote: > > As more and more hardware supports digital input and/or output > (more often output than input), I was wondering if it makes sense > to offer a build/packaging option of "skinny digital", which would > entail omitting all of the analogue portions of the driver, the > config files, and the various utilities (or the utilities could detect that > no analogue hardware support is present and simply disable it). > > The idea being that if someone wanted to have a bare bones (pardon > the pun) installation that supported digital output only (or digital > input and output) with no need for analogue mixing or analogue > source routing, then they could do so with a minimum configuration. > Why? Well, the less there is to configure, the less that can go wrong... > and since all digital media (CD, DVD, digital satellite tuners, ATSC, > etc) is more and more common, people probably have little or no need > for analogue functionality these days. I don't think the analog will go away at all but I understand your proposal. > So the installer portions of the makefiles would need to be changed > to understand a digital only install, the source configuration files > could be tweaked to allow preprocessing via m4 or cpp, and the > drivers and libraries could be made conditional to omit the code > that handles analogue functionality. > > Initialization too might need to change the default settings to be > digital... > > What does everyone think? Comments? Am I off in left field? My idea is different. We may provide presets of PCM/mixer/whatever runtime configurations rather than compile-time one. It's just like defining your own ~/.asoundrc but in the system-wide way. The requirement for embedded systems is of course different. We need to do more diet. But, only for usability, the runtime configuration would be a better choice, I guess. Takashi ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf