Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Adrian Bunk <bunk@stusta.de>
Cc: linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org,
	perex@suse.cz, linux-mips@linux-mips.org
Subject: Re: RFC: OSS driver removal, a slightly different approach
Date: Sat, 21 Jan 2006 21:05:11 +0000	[thread overview]
Message-ID: <20060121210511.GD3456@linux-mips.org> (raw)
In-Reply-To: <20060119174600.GT19398@stusta.de>

On Thu, Jan 19, 2006 at 06:46:00PM +0100, Adrian Bunk wrote:

> 3. no ALSA drivers for the same hardware
[...]
> SOUND_AU1550_AC97
[...]
> SOUND_IT8172
[...]
> SOUND_VRC5477

I'm already hammering the responsible people to rewrite the drivers for
ALSA since a while but slow progress.  The latter two platforms have no
active maintainers so I don't expect to see ALSA drivers.

  Ralf

       reply	other threads:[~2006-01-23 12:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20060119174600.GT19398@stusta.de>
2006-01-21 21:05 ` Ralf Baechle [this message]
2006-01-23 14:11   ` RFC: OSS driver removal, a slightly different approach Dan Malek
2006-01-23 15:06     ` Jordan Crouse

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=20060121210511.GD3456@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=bunk@stusta.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=perex@suse.cz \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox