All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Knutsson <ricknu-0@student.ltu.se>
To: Adrian Bunk <bunk@stusta.de>
Cc: 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:16:40 +0200	[thread overview]
Message-ID: <46077358.70006@student.ltu.se> (raw)
In-Reply-To: <20070326014819.GS16477@stusta.de>

Adrian Bunk wrote:
> On Mon, Mar 26, 2007 at 03:26:19AM +0200, 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). 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.
>>     

> Current number of regressions in the ALSA emu10k1 driver people gave me 
> numbers of open ALSA bugs for:
>   0
>   
Oh ok, I will let him know that. Thanks

Richard Knutsson


  reply	other threads:[~2007-03-26  7:23 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 [this message]
2007-03-26  4:16   ` Lee Revell
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:
  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=46077358.70006@student.ltu.se \
    --to=ricknu-0@student.ltu.se \
    --cc=akpm@linux-foundation.org \
    --cc=bunk@stusta.de \
    --cc=linux-kernel@vger.kernel.org \
    /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.