Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Jaroslav Kysela <perex@suse.cz>
To: linux-sound@vger.kernel.org
Subject: Re: Support not in Linux, but in ALSA
Date: Mon, 17 Jul 2000 15:21:11 +0000	[thread overview]
Message-ID: <marc-linux-sound-96384766630613@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-96384685629051@msgid-missing>

On Mon, 17 Jul 2000, Peter Rasmussen wrote:

> I have never before *had* to use an external driver to a sound card, but this
> weekend it appeared to me that I had to. I bought a [cheap] PCI sound card that
> I needed to be non-SB because it would interfere with the mobo-SBVibra that I
> have. It is a ForteMedia FM801 soundcard with no information on the chips, and
> failing attempts to use just about every driver in Linux, I had to look 
> elsewhere and found that ALSA supports it, just like that. It even has OSS
> emulation so I could continue where I left with the SB driver.
> 
> As ALSA is also GPL, does anyone here know why it hasn't been included into
> the Linux sound subsystem? It looks to me like there is duplicate work going
> on and not necessarily for the benefit of the general Linux user.
> 
> OSS is a commercial company that releases their for profit drivers when they are
> old enough for them not to make any profit anymore (it seems), ergo presently
> the Linux sound system is getting the crums from OSS, when instead we could
> have a very nice looking sound system like ALSA put into the kernel. I know 
> there is more than OSS sound drivers in Linux, but those are pretty scarce and
> the cards pretty expensive :-)
> 
> Is it because of the history of OSS being the first to ever have Linux sound
> drivers, or is it the ALSA team that doesn't want to have their code included
> into Linux proper?

The reason is simple. While we are digging heavy into the new sound APIs,
the OSS API is quite old (and anarchic) but stable. It probably fits more
for the actual sound driver code developers who don't like to change
driver every month because some internal changes occured.

We hope that we will have finished the most of our work for the 2.5 kernel
tree. We are actually co-operating with the Jeff Garzik (Mandrake) to
remove all glitches in our code which could avoid the code merge.

> This is my first encounter ever with ALSA, and I am just wondering if
> there are technical (ALSA doesn't really fit well into Linux proper),
> managerial (somebody has to do the work and nobody can) or political
> (the ALSA team doesn't like the Linux sound guys or vice versa)
> reasons for it?

The primary key is probably time of the interface development (internal &
external). Alan Cox had another opinion at the beginning of this year than
me. I voted to include ALSA drivers into the 2.3 kernel tree to
involve more sound developers for ALSA, but I was not successful.

> At least there has to have been some talk about it, but I have never heard it
> and I have not before seen ALSA mentioned a lot here?

ALSA team hopes that ALSA drivers will be merged to the development 2.5
kernel tree.

						Jaroslav

-----
Jaroslav Kysela <perex@suse.cz>
SuSE Linux    http://www.suse.com
ALSA project  http://www.alsa-project.org

  reply	other threads:[~2000-07-17 15:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-17 15:00 Support not in Linux, but in ALSA Peter Rasmussen
2000-07-17 15:21 ` Jaroslav Kysela [this message]
2000-07-17 17:49 ` Dave Phillips

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=marc-linux-sound-96384766630613@msgid-missing \
    --to=perex@suse.cz \
    --cc=linux-sound@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox