From: Lennart Poettering <mznyfn@0pointer.de>
To: alsa-devel@alsa-project.org
Cc: "Aaron J. Grier" <agrier@poofygoof.com>
Subject: Re: Guide to Linux Sound APIs
Date: Thu, 25 Sep 2008 02:23:15 +0200 [thread overview]
Message-ID: <20080925002315.GA16402@tango.0pointer.de> (raw)
In-Reply-To: <20080925001718.GN1107@arwen.poofy.goof.com>
On Wed, 24.09.08 17:17, Aaron J. Grier (agrier@poofygoof.com) wrote:
>
> On Thu, Sep 25, 2008 at 09:05:14AM +1000, Ben Finney wrote:
> > Lennart Poettering <mznyfn@0pointer.de> writes:
> >
> > > http://0pointer.de/blog/projects/guide-to-sound-apis
> > >
> > > I'd be very thankful for comments, especially from you Takashi and
> > > Jaroslav since it contains quite some details about the "safe" subset
> > > of the ALSA API!
> > >
> > > I'm thankful for all kinds of input!
> >
> > I'm very thankful that you've made this positive contribution. It is
> > sorely needed, and I hope it will spur greater collaboration.
>
> how finalized is the "safe ALSA subset" to mention it in the ALSA docs?
> I am an embedded developer new to ALSA and am still a bit bewildered on
> best-practices.
Dunno. This guide is just something I wrote up as someone who knows
the ALSA API quite well I think. However, I am mostly just a developer
*using* the API, not a developer *writing* the API.
If you want some reliable, "official" opinions, then wait until Takashi
and Jaroslav commented on this. They are certainly the ones whose
endorsing or not-endorsing of this guide matters the most.
Lennart
--
Lennart Poettering Red Hat, Inc.
lennart [at] poettering [dot] net ICQ# 11060553
http://0pointer.net/lennart/ GnuPG 0x1A015CC4
next prev parent reply other threads:[~2008-09-25 0:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-24 22:48 Guide to Linux Sound APIs Lennart Poettering
2008-09-24 23:05 ` Ben Finney
2008-09-25 0:17 ` Aaron J. Grier
2008-09-25 0:23 ` Lennart Poettering [this message]
2008-09-25 10:15 ` Takashi Iwai
2008-09-25 19:40 ` Lennart Poettering
2008-09-26 9:44 ` 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=20080925002315.GA16402@tango.0pointer.de \
--to=mznyfn@0pointer.de \
--cc=agrier@poofygoof.com \
--cc=alsa-devel@alsa-project.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 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.