From: Richard Knutsson <ricknu-0@student.ltu.se>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Adrian Bunk <bunk@stusta.de>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [2.6.22 patch] more scheduled OSS driver removal
Date: Mon, 26 Mar 2007 09:30:58 +0200 [thread overview]
Message-ID: <460776B2.3070404@student.ltu.se> (raw)
In-Reply-To: <75b66ecd0703252116m5216ec8dy78528f512ae63747@mail.gmail.com>
Lee Revell wrote:
> On 3/25/07, Richard Knutsson <ricknu-0@student.ltu.se> 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
> mature?
Good! I forward that info to him.
BTW, I did not mean to suggest we keep the OSS instead of ALSA. Just
voiced if it is _ready_ to be replaced. But since there is no regression
report filed (believed he already made one) I will pipe down :)
>
>> 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.
<rant_mode=on>
Isn't this quite a basic feature?! Is there somewhere to monitor the
progress on this?
<rant_mode=off>
Thanks for your help!
Richard Knutsson
next prev parent reply other threads:[~2007-03-26 7:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-24 13:06 [2.6.22 patch] more scheduled OSS driver removal 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
2007-03-26 7:30 ` Richard Knutsson [this message]
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:
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=460776B2.3070404@student.ltu.se \
--to=ricknu-0@student.ltu.se \
--cc=akpm@linux-foundation.org \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.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.