All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Courtier-Dutton <James@superbug.demon.co.uk>
To: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Way to save DSP resources on the emu10k1
Date: Thu, 09 Oct 2003 16:17:06 +0100	[thread overview]
Message-ID: <3F857BF2.40106@superbug.demon.co.uk> (raw)

Hi,

I have thought of a possible way to save DSP resources on the SB 
Live/Audigy etc.

Instead of having DSP code actually in the emu10k1 source code, have it 
in small user land files on disk.
When the snd-emu10k1 modules is first loaded, it will contain no DSP 
code. When alsa-lib detects an emu10k1 DSP, it would scan the user land 
files, and then present the mixer api/user with a list of switches, to 
enable or disable a feature, then, only the features the user actually 
wants and needs would be loaded into the DSP, and thus save on DSP 
resources.

This would also allow for special extra user designed modules, in much 
the same way that emu-dspmgr works on the oss driver.

Then the user could have an almost unlimited amount of DSP modules to 
choose from, and only be limited by how many modules can be loaded at 
the same time.

I am sure thise sort of feature would also me useful on other sound 
cards that have DSPs on them.

Cheers
James



-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php

             reply	other threads:[~2003-10-09 15:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-09 15:17 James Courtier-Dutton [this message]
2003-10-09 15:26 ` Way to save DSP resources on the emu10k1 Jaroslav Kysela

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=3F857BF2.40106@superbug.demon.co.uk \
    --to=james@superbug.demon.co.uk \
    --cc=alsa-devel@lists.sourceforge.net \
    /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.