Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: fmoraes@nc.rr.com
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: emu10k1x/AudigyLS period table
Date: Tue, 29 Jun 2004 18:21:55 +0200	[thread overview]
Message-ID: <s5hr7rybaho.wl@alsa2.suse.de> (raw)
In-Reply-To: <1e6ff561e6a898.1e6a8981e6ff56@southeast.rr.com>

At Mon, 28 Jun 2004 22:49:43 -0400,
fmoraes@nc.rr.com wrote:
> 
> This the information that James Courtier-Dutton found about the AudigyLS that also works for the emu10k1x:
> 
> #define PLAYBACK_LIST_ADDR	0x00		/* Base DMA address of a list of pointers to each period/size */
> 						/* One list entry: 4 bytes for DMA address, 
> 						 * 4 bytes for period_size << 16.
> 						 * One list entry is 8 bytes long.
> 						 * One list entry for each period in the buffer.
> 						 */
> #define PLAYBACK_LIST_SIZE	0x01		/* Size of list in bytes << 16. E.g. 8 periods -> 0x00380000  */
> #define PLAYBACK_LIST_PTR	0x02		/* Pointer to the current period being played */
> 
> Is this in anyway similar to the emu10k1 PTB scatter-gather? Just wondering if they reused the design.

No, it looks rather similar with the buffer descriptors used in
via82xx or intel8x0 to me.  You can take a look at via82xx code for
supporting SG-buffer.  It's a bit complicated because the period size
isn't always aligned to the page size.


Takashi


-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com

      reply	other threads:[~2004-06-29 16:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-29  2:49 emu10k1x/AudigyLS period table fmoraes
2004-06-29 16:21 ` Takashi Iwai [this message]

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=s5hr7rybaho.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=fmoraes@nc.rr.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