From: Smilen Dimitrov <sd@imi.aau.dk>
To: alsa-devel@alsa-project.org
Cc: Eliot Blennerhassett <eblennerhassett@audioscience.com>
Subject: Re: Help with dummy.c (where/how to write?)
Date: Tue, 06 Jul 2010 06:46:49 +0200 [thread overview]
Message-ID: <4C32B539.30801@imi.aau.dk> (raw)
In-Reply-To: <4C32518B.6000505@audioscience.com>
Hi Eliot,
Thanks so much for your response:
>>
>> I am trying to work on dummy.c:
>>
>> http://lxr.linux.no/#linux+v2.6.32/sound/drivers/dummy.c
>>
>> as an exercise, and I'd like to modify it so it behaves as an
>> 'oscillator'; [snip]
>>
>
> You are better to look at the loopback driver in alsa-driver repo:
>
> http://git.alsa-project.org/?p=alsa-driver.git;a=blob_plain;f=drivers/aloop-kernel.c;hb=HEAD
>
> You would put your generation code in clear_capture_buf()
>
Fantastic info - that is exactly what I needed :)
(Don't know why your response hasn't shown in the alsa-devel archives
yet, hopefully my reply will bump it up there)
Cheers!
prev parent reply other threads:[~2010-07-06 4:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-05 20:46 Help with dummy.c (where/how to write?) Smilen Dimitrov
[not found] ` <4C32518B.6000505@audioscience.com>
2010-07-06 4:46 ` Smilen Dimitrov [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=4C32B539.30801@imi.aau.dk \
--to=sd@imi.aau.dk \
--cc=alsa-devel@alsa-project.org \
--cc=eblennerhassett@audioscience.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;
as well as URLs for NNTP newsgroup(s).