All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tehn Yit Chin <tehn-yit.chin@greyinnovation.com>
To: Philip Prindeville <philipp_subx@redfish-solutions.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: Skinny (and very skinny) digital packaging
Date: Wed, 10 Aug 2005 09:09:13 +1000	[thread overview]
Message-ID: <42F93799.4080401@greyinnovation.com> (raw)
In-Reply-To: <42F929AE.3010703@redfish-solutions.com>

Hi Philip,

I would be interested in something like this in ALSA. As an example, 
most of our embedded devices only have a PCM playback at one volume 
setting, so I only really need the PCM playback, none of the mixing or 
capturing or analogue partions etc of ALSA.

Also our embedded devices are usually resource limited, so smaller is 
better for us.

I understand that your idea surrounds only the digital portion of ALSA, 
but I think that the idea can be extended to the rest of ALSA's components.

cheers,
Tehn Yit Chin

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.
>
> 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?
>
> Thanks,
>
> -Philip
>
>
>
> -------------------------------------------------------
> 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
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/alsa-devel
>


-- 
Tehn Yit Chin
Software Engineer, Grey Innovation Pty. Ltd.



-------------------------------------------------------
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

  reply	other threads:[~2005-08-09 23:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-09 22:09 Skinny (and very skinny) digital packaging Philip Prindeville
2005-08-09 23:09 ` Tehn Yit Chin [this message]
2005-08-10  9:56   ` Takashi Iwai
2005-08-10 10:05 ` Takashi Iwai

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=42F93799.4080401@greyinnovation.com \
    --to=tehn-yit.chin@greyinnovation.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=philipp_subx@redfish-solutions.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.