Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: ljp <ljp@llornkcor.com>
Cc: Thierry Vignaud <tvignaud@mandrakesoft.com>,
	alsa devel <alsa-devel@lists.sourceforge.net>
Subject: Re: porting oss app to alsa
Date: Thu, 30 Jan 2003 15:41:36 +0100	[thread overview]
Message-ID: <s5hy952k8db.wl@alsa2.suse.de> (raw)
In-Reply-To: <200301300717.36415.ljp@llornkcor.com>

At Thu, 30 Jan 2003 07:17:36 -0700,
ljp wrote:
> 
> > this is portable but limited (open/closing mixer/device, setting mix ,
> > output samples, ...)
> >
> > for high level usage, look at html doc in libalsa2.
> 
> ya, I was asking if there is a document that explains how to port OSS apps.
> Such as:
> 
> OSS						ALSA
> -------------------------------------------------------
> SNDCTL_DSP_GETOSPACE	 something_or_another
> MIXER_READ				 some_mixer_function	
 
this would be a nice tutorial, but i've never known, unfortunately.

i hope someone can start working on such a document.


> I am asking this, as the ALSA OSS compat. seems to be getting depreaciated (I 
> dont blame it), and stuck on rc1.

not deprecated, but the version is stopped just because no changes are
necessary.  (doesn't mean it's enough stable, though :)


Takashi


-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com

  parent reply	other threads:[~2003-01-30 14:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-30  3:18 porting oss app to alsa ljp
2003-01-30 10:31 ` Thierry Vignaud
2003-01-30 14:17   ` ljp
2003-01-30 14:29     ` Paul Davis
2003-01-30 14:41     ` Takashi Iwai [this message]
     [not found] <200301301423.h0UENsG12061@charon.host4u.net>
2003-01-30 14:46 ` ljp
2003-01-30 15:08   ` Paul Davis

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=s5hy952k8db.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=ljp@llornkcor.com \
    --cc=tvignaud@mandrakesoft.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