All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Joachim Förster" <mls.JOFT@gmx.de>
To: alsa-devel@alsa-project.org
Subject: Re: embedded sound architecture question
Date: Fri, 11 May 2007 17:21:05 +0200	[thread overview]
Message-ID: <1178896865.5727.18.camel@localhost> (raw)
In-Reply-To: <20070509142044.33de8ba2@jutz-fc6.na.corp.dmxmusic.com>

On Wed, 2007-05-09 at 14:20 -0700, John L. Utz III wrote:
> On Wed, 09 May 2007 22:47:34 +0200
> "Joachim Förster" <mls.JOFT@gmx.de> wrote:
> > My question is: Does the architecture described below make sense/is
> > reasonable with ALSA and Linux?
> 
> i think you might have to answer an earlier question first; 'does it
> make sense to call this an ac97 controller?' I dont recall seeing a
> ring buffer as part of the ac97 standard. i'd suggest that you take the
> time to flesh out completely how the ring buffer is supposed to replace
> dma and ram while still presenting an ac97 set of verbs because i am
> stuck with the gut feeling that you will some important things will
> have to be really different.

Hmmm, well is there a standard document for AC97 controllers, too? So
far, I know about the AC97 Codec standard, only. Anyway, just ignore the
"AC97" in front of "controller" - a custom controller for an AC97 Codec,
which uses the described way of operation and features. The/My question
is, if such a thing is reasonable and fits into ALSA/Linux.

> > I read, that many applications don't work, if MMAP mode is not
> > supported and classic read/write (copy()/silence()) is used, only. Is
> > there a black list of apps, which don't work?
> 
> i doubt seriously that such a thing exists, how could it? new apps are
> written everyday, old apps in binary only form get 'shimmed' forward
> with comaptibility libraries to work in newer operating systems.

So, not using MMAP mode is just a no-go ... ? I don't want to write a
driver which cannot be used with most ALSA applications out there.

 Joachim

  reply	other threads:[~2007-05-11 15:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-09 20:47 embedded sound architecture question Joachim Förster
2007-05-09 21:20 ` John L. Utz III
2007-05-11 15:21   ` Joachim Förster [this message]
2007-05-12 16:40 ` Rask Ingemann Lambertsen
  -- strict thread matches above, loose matches on Subject: below --
2007-05-13 10:02 Lorenz Kolb

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=1178896865.5727.18.camel@localhost \
    --to=mls.joft@gmx.de \
    --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.