All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Richard Cochran <cochran@cs.umass.edu>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: documentation - yeah right!
Date: Thu, 22 May 2003 17:33:12 +0200	[thread overview]
Message-ID: <s5hhe7nq9mv.wl@alsa2.suse.de> (raw)
In-Reply-To: <20030522101823.B29826@loki.cs.umass.edu>

At Thu, 22 May 2003 10:18:23 -0400,
Richard Cochran wrote:
> 
> I have two additional questions:
> 
> On Thu, May 22, 2003 at 02:47:27PM +0200, Takashi Iwai wrote:
> > - ALSA is not only the driver.
> > - ALSA model is still Unix style (somehow).
> > - ALSA library is the low-level library.
> 
> Are the calls snd_pcm_* kernel calls or library calls?

they are library calls.

> If the latter,
> where is the library-kernel API?
 
this is not documented.
and you should not communicate directly with the drivers.

the kernel API might be changed in future because of further
extensions.  in that case, the alsa-lib will absorb the change of
kernel API, so that the ALSA library API keeps unchanged.

hence, it's not necessary for audio application programmers to know
the kernel API (except for the curiosity :)


btw, i forgot to mention that there are some slides of my talk in LAD
meeting:
	http://www.alsa-project.org/~iwai/lad2003/lad.html


> When using the Alsa OSS compatibility layer, is there a performace
> penalty in terms of latency?

usually, no.

> Will OSS support likely be dropped in kernel 2.6?

no.  very unlikely.

> How are the OSS drivers "thread unsafe", or rather, what are the
> thready safety issues that Alsa addresses?

well, i don't think the OSS drivers are "thread unsafe" but might be
SMP unsafe or ineffective.  some OSS drivers are written on the
assumption of UP (and some are not).

ALSA has the common middle layer, and it is written carefuly to
support SMP systems.


ciao,

Takashi


-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a
relational database is painful, don't do it! Check out ObjectStore.
Now part of Progress Software. http://www.objectstore.net/sourceforge

  reply	other threads:[~2003-05-22 15:33 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-20 20:10 documentation - yeah right! Cliff Bradshaw
2003-05-20 20:16 ` Jaroslav Kysela
2003-05-20 20:31 ` Josh Green
2003-05-20 20:52 ` Kai Vehmanen
2003-05-20 22:11   ` David Stuart
2003-05-20 22:08 ` Paul Davis
2003-05-20 23:53 ` Drake Wilson
2003-05-21  5:02   ` Patrick Shirkey
2003-05-21  7:34 ` Giuliano Pochini
2003-05-21 14:43   ` Richard Cochran
2003-05-21 15:24     ` Paul Davis
2003-05-21 15:50       ` Paul Davis
     [not found]     ` <200305211518.h4LFI2jE027163@mail.cs.umass.edu>
2003-05-21 15:59       ` Richard Cochran
2003-05-21 16:52         ` Kai Vehmanen
2003-05-21 17:16           ` Richard Cochran
2003-05-21 17:36             ` Kai Vehmanen
2003-05-21 17:39             ` Jaroslav Kysela
2003-05-21 17:49             ` Paul Davis
2003-05-21 17:03         ` Paul Davis
     [not found]         ` <200305211657.h4LGvKjE024721@mail.cs.umass.edu>
2003-05-21 18:08           ` Richard Cochran
2003-05-22  1:28             ` Patrick Shirkey
2003-05-21 16:09       ` Richard Cochran
2003-05-21 16:44         ` Paul Davis
2003-05-22 13:16           ` PCI write barrier Giuliano Pochini
2003-05-23 10:30             ` Takashi Iwai
2003-05-22 12:47         ` documentation - yeah right! Takashi Iwai
2003-05-22 13:39           ` Jaroslav Kysela
2003-05-22 14:51             ` Pieter Palmers
2003-05-22 14:18           ` Richard Cochran
2003-05-22 15:33             ` Takashi Iwai [this message]
2003-05-22 16:57               ` Jack O'Quin
2003-05-22 17:03               ` Patrick Shirkey
2003-05-22 17:08               ` Richard Cochran
2003-07-11  0:23     ` i810 - no sound from cvs snapshot Richard Cochran

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=s5hhe7nq9mv.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=cochran@cs.umass.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.