alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Smilen Dimitrov <sd@imi.aau.dk>
To: ALSA Development Mailing List <alsa-devel@alsa-project.org>
Subject: Re: Questions about virtual ALSA driver (dummy), PortAudio and full-duplex drops (playback)
Date: Fri, 16 Aug 2013 07:20:08 +0200	[thread overview]
Message-ID: <520DB688.3050205@imi.aau.dk> (raw)
In-Reply-To: <CAN8cciZd5s-XQRehE4LDQ=mY5X1HrAiy+c=QG7VYUx9ykjQoqQ@mail.gmail.com>

Hi Raymond,

Many thanks for your response!


>>
>> While I have learned that modern cards do not have on-board buffers,
>
> Take a look at Intel® High Definition Audio Specification Document Change
> Notification
> 4.6 Energy Efficient HD Audio (EEAudio) Mechanism
>
> There is controller (HW) buffer <local fifo> in the Figure 14 HD Audio DMA
> and buffering

Thanks for spotting that - wasn't aware of this document. I had a bit of trouble tracking it down using those terms - ended up finding it on a page entitled "Intel® High Definition Audio Energy Efficient Buffering: Spec".

Now, that comment of mine, stems from this:

>>> I'm assuming that the card has it's own intern capture buffer memory
>>> on board;
>>
>> No modern card has this.  All data is immediately read from/written to
>> main memory.
>>
>
> Thanks for noting this - I wish I knew better :) [...]

... and come to think of it, I did start the discussion referring to "capture" there. Reading the Intel spec DCN, "capture" is never mentioned, while "played" is mentioned once. Does this mean that the referred FIFO for hda-intel is just for playback, while there is no such counterpart for capture? Or is it that for hda-intel on-board cards, they have FIFO's in both direction, but other modern cards don't necessarily? Or maybe I introduced the problem, by carelessly referring to "buffer memory", which might mean true random access memory - while modern cards may have FIFO's (which I'd guess are electrically simpler)?


Thanks for any clarifications,
Cheers!

_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  reply	other threads:[~2013-08-16  5:20 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-24  2:54 Questions about virtual ALSA driver (dummy), PortAudio and full-duplex drops Smilen Dimitrov
2013-07-24 13:03 ` Alan Horstmann
2013-07-25  0:29   ` Smilen Dimitrov
2013-07-25  8:37     ` Clemens Ladisch
2013-08-04  0:05       ` Smilen Dimitrov
2013-08-06 10:59         ` Clemens Ladisch
2013-08-06 11:41           ` David Henningsson
2013-08-06 13:04             ` Clemens Ladisch
2013-08-08  2:50           ` Smilen Dimitrov
2013-08-14 14:30       ` Questions about virtual ALSA driver (dummy), PortAudio and full-duplex drops (playback) Smilen Dimitrov
2013-08-15  4:17         ` Raymond Yau
2013-08-16  5:20           ` Smilen Dimitrov [this message]
2013-09-13  6:23       ` Questions about virtual ALSA driver (dummy), PortAudio and full-duplex drops (full-duplex: latency.c) Smilen Dimitrov
2013-09-17 16:07         ` Smilen Dimitrov
2013-10-21 14:48       ` [Solved] Questions about virtual ALSA driver (dummy), PortAudio and full-duplex Smilen Dimitrov
2013-07-24 18:30 ` [Audacity-devel] Questions about virtual ALSA driver (dummy), PortAudio and full-duplex drops Richard Ash

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=520DB688.3050205@imi.aau.dk \
    --to=sd@imi.aau.dk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).