From: John Graham <johngavingraham@googlemail.com>
To: alsa-devel@alsa-project.org
Subject: Access to bytes from the raw audio stream? (AC'97)
Date: Wed, 3 Feb 2010 16:08:38 +0000 [thread overview]
Message-ID: <94cf76f1002030808t1d54dc08oab179673e814f016@mail.gmail.com> (raw)
Hi there,
I'm new to ALSA, and working on a project where I need to find out
where I can see/modify the raw bytes coming in from/going out to a
device. The device is an AC'97 codec (a philips UCB1400, if it makes
any difference...) on an embedded board.
I tried looking on the web, and found the tutorial at
http://www.alsa-project.org/~tiwai/writing-an-alsa-driver/, but that
seems to be more about device management and configuration.
So, can anybody tell me what functions and files in the sound/
directory of the linux kernel I need to look at to see/modify the raw
data stream coming in? Am I just missing something in the tutorial?
I'd appreciate any suggestions very much.
Thanks,
John Graham
next reply other threads:[~2010-02-03 16:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-03 16:08 John Graham [this message]
2010-02-03 16:17 ` Access to bytes from the raw audio stream? (AC'97) Mark Brown
2010-02-03 16:27 ` John Graham
2010-02-03 16:59 ` Mark Brown
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=94cf76f1002030808t1d54dc08oab179673e814f016@mail.gmail.com \
--to=johngavingraham@googlemail.com \
--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).