LKML Archive on
help / color / mirror / Atom feed
From: "Lee Revell" <>
To: "Richard Knutsson" <>
Cc: "Adrian Bunk" <>,
	"Andrew Morton" <>,
Subject: Re: [2.6.22 patch] more scheduled OSS driver removal
Date: Mon, 26 Mar 2007 00:16:09 -0400	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 3/25/07, Richard Knutsson <> wrote:
> Adrian Bunk wrote:
> > This patch contains the scheduled removal of OSS drivers that:
> > - have ALSA drivers for the same hardware without known regressions and
> > - whose Kconfig options have been removed in 2.6.20.
> >
> Sorry for this late respond
> Is sound/oss/emu10k1/ really ready to be replaced? According to a friend
> of mine, who got the hardware, the ALSA still lacks feature provided by
> the OSS-driver. He mentioned some sort of programmable memory (forgot
> the name for that) with whom you can run small programs to manipulate
> the sounds (adding echo and such).

He's referring to EMU DSP manager.  (emudspmgr I think it's called).
The ALSA equivalent is ld10k1.  It might not be as mature as the OSS
equivalent, but are we really going to keep obsolete drivers in the
kernel just because the userspace tools for the old driver are more

> Also, he got problems with getting
> more accurate control of the volume (guess this is more a userland issue).
> He seems to have done his homework but only got to pages where other
> peoples had the same problem.

I guess he's referring to the well known "Master volume only controls
front output" problem.  This really does need to be resolved, as many
other ALSA drivers are effected.


  parent reply	other threads:[~2007-03-26  4:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-24 13:06 Adrian Bunk
2007-03-26  1:26 ` Richard Knutsson
2007-03-26  1:48   ` Adrian Bunk
2007-03-26  7:16     ` Richard Knutsson
2007-03-26  4:16   ` Lee Revell [this message]
2007-03-26  7:30     ` Richard Knutsson
2007-03-26 15:45       ` Lee Revell
2007-03-26 12:43     ` Jan Engelhardt

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:

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

  git send-email \ \ \ \ \ \ \
    --subject='Re: [2.6.22 patch] more scheduled OSS driver removal' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).