Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: ljp <ljp@llornkcor.com>
To: Paul Davis <paul@linuxaudiosystems.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 07:46:43 -0700	[thread overview]
Message-ID: <200301300746.43506.ljp@llornkcor.com> (raw)
In-Reply-To: <200301301423.h0UENsG12061@charon.host4u.net>

On Thursday January 30 2003 07:29 am, Paul Davis wrote:
> >I am asking this, as the ALSA OSS compat. seems to be getting depreaciated
> > (I dont blame it), and stuck on rc1.
>
> its not deprecated, though many of us would actively discourage anyone
> from writing new applications that use the OSS API. its very important
> for ALSA that it fully and properly supports the OSS API. if it did
> not, it would have been very hard to get linus to accept ALSA as the
> default/standard audio API in the 2.5/2.6 kernel series.
>
> --p
>
> ps. of course, some of us would discourage people from using ALSA
>     as the API too :)))

Well, the reason I asked, is that I am involved with porting Helix stuff to 
arm linux. And someone pointed out yeasterday, that there was no OSS compat 
for his soundcard. So, since I am waiting for stuff to get working again in 
respect to gcc 2.95, I took it upon myself (thinking this was almost trival 
to change a few fucntions from OSS to ALSA) to write some ALSA native device 
functions to give users a choice. This is my first time really digging into 
ALSA API, and I must say, I like what I see. :D

And instead of bothering people with silly questions, 'how do I perform x OSS 
function", I went looking at the docs. The tutroials are very good, but don't 
touch upon some of the more compilcated aspects. It seems maybe there is a 
glossary or something needed for people more familiar with OSS terminology. 

Such as, whats a poll ? The docs state, in a not very clear way, for example, 
for snd_timer_poll_descriptors, 'gets poll descriptors'.. hmm, ok, whats a 
poll descriptor? :D


Although I am thankful for the docs, I think it might be useful to have a one 
page doc outlining the OSS calls..

thanks-
ljp


-- 
My cat's a debugger....

Potter, Lorn, "ljp"
core member / Web Administrator
Project OPIE- the Open Palmtop Integrated Environment
http://opie.handhelds.org 
IRC: irc.freenode.net #opie #opie.de

llornkcor@handhelds.org
llornkcor@helixcommunity.org



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

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

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

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=200301300746.43506.ljp@llornkcor.com \
    --to=ljp@llornkcor.com \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=paul@linuxaudiosystems.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