Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: mAdVax <madvax@free.fr>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: emu10k1 TRAM access ?
Date: Fri, 15 May 2009 22:56:44 +0200	[thread overview]
Message-ID: <4A0DD70C.8050109@free.fr> (raw)
In-Reply-To: <s5hskj6a2rl.wl%tiwai@suse.de>

Takashi Iwai a écrit :
> At Thu, 14 May 2009 14:41:02 +0200,
> mAdVax wrote:
>> Hello
>>
>> I would like to send some data to a DSP patch. I can use alsa controls
>> (easy) but I need more : TRAM and lookup table. I read many lines of
>> code, but all this is still quite obscure...
>> Here are 3 questions :
>>
>> How can I fill the TRAM ? (from user space)
>> How can I know which TRAM area has been allocated to a given patch ?
>> Do 'lookup tables' work ?
>>
>> Some code samples will be greatly appreciated  :)
> 
> Well, it got into already my dark place of memory, and my cache is too
> small to fetch soon.  But, I recommend you to take a look at
> alsa-tools/ld10k1.  It's the central place to access the emu10k1 DSP.

Done ;)
Either I missed something, either lookup tables are not implemented.

The client part (liblo*) uses different struct for delay-lines and for
lookup tables, the server part (ld*) contains only minor references to
tram type, but the driver part does not make _any_ difference (AFAI
understand).

In the old as10k1 documentation at sourceforge, it is said :
> Note, lookup tables currently don't work
> (because we don't understand how to)
But the Alsa documentation does not say anything.

Don't you (anyone) only remember if lookup table has been implemented ?

Thanks again

Xavier


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

  reply	other threads:[~2009-05-15 20:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-14 12:41 emu10k1 TRAM access ? mAdVax
2009-05-14 12:47 ` mAdVax
2009-05-15 13:56 ` Takashi Iwai
2009-05-15 20:56   ` mAdVax [this message]
2009-05-16 10:32     ` mAdVax
2009-05-16 15:09       ` Takashi Iwai
2009-05-16 21:28         ` mAdVax
2009-05-17 15:48           ` Alex Austin
2009-05-17 21:05             ` mAdVax
2009-05-18 19:34               ` Alex Austin
2009-05-18 22:28                 ` mAdVax
  -- strict thread matches above, loose matches on Subject: below --
2009-05-13 12:53 mAdVax

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=4A0DD70C.8050109@free.fr \
    --to=madvax@free.fr \
    --cc=alsa-devel@alsa-project.org \
    --cc=tiwai@suse.de \
    /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