public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: Ricardo Cerqueira <v4l@cerqueira.org>,
	mchehab@brturbo.com.br, video4linux-list@redhat.com,
	linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] VIDEO_SAA7134_ALSA shouldn't select SND_PCM_OSS
Date: Mon, 09 Jan 2006 23:43:58 -0500	[thread overview]
Message-ID: <1136868239.2007.58.camel@mindpipe> (raw)
In-Reply-To: <20060110043308.GC3911@stusta.de>

On Tue, 2006-01-10 at 05:33 +0100, Adrian Bunk wrote:
> On Mon, Jan 09, 2006 at 11:14:05PM -0500, Lee Revell wrote:
> > On Tue, 2006-01-10 at 05:06 +0100, Adrian Bunk wrote:
> > > There's no reason for an ALSA driver to select an OSS legacy userspace 
> > > interface.
> > 
> > Actually there is a reason.  While OSS may be deprecated the OSS API is
> > not - ALSA is committed to supporting it for the forseeable future.  And
> > as broken an interface as it is, a lot of people consider the sound
> > system broken if you can't just write() to /dev/dsp and have sound come
> > out.
> 
> No disagreement, but that's not the point.
> 
> SND_PCM_OSS gives an OSS API interface for userspace on top of ALSA.
> ALSA drivers shouldn't care whether they are controlled directly 
> through ALSA or through a legacy OSS API on top of ALSA.
> 
> If someone wants to use SND_PCM_OSS that is fine, but the ALSA interface 
> to my saa7134 card is working fine, so why does it force me to compile a 
> legacy OSS API interface into the kernel?

OK, makes sense.

Lee


  reply	other threads:[~2006-01-10  4:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-10  4:06 [2.6 patch] VIDEO_SAA7134_ALSA shouldn't select SND_PCM_OSS Adrian Bunk
2006-01-10  4:14 ` Lee Revell
2006-01-10  4:33   ` Adrian Bunk
2006-01-10  4:43     ` Lee Revell [this message]
2006-01-10 18:56 ` Mauro Carvalho Chehab

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=1136868239.2007.58.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=bunk@stusta.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@brturbo.com.br \
    --cc=v4l@cerqueira.org \
    --cc=video4linux-list@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox