From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: John Graham <johngavingraham@googlemail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: Access to bytes from the raw audio stream? (AC'97)
Date: Wed, 3 Feb 2010 16:17:37 +0000 [thread overview]
Message-ID: <20100203161737.GC12034@sirena.org.uk> (raw)
In-Reply-To: <94cf76f1002030808t1d54dc08oab179673e814f016@mail.gmail.com>
On Wed, Feb 03, 2010 at 04:08:38PM +0000, John Graham wrote:
> 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.
With a lot of AC97 controllers the hardware won't allow you direct
access to the cooked wire data, you'll only be able to see decoded audio
streams. What is it that you're actually trying to do?
For embedded platforms you mostly want to look under sound/soc though
there are a few platforms outside of there.
next prev parent reply other threads:[~2010-02-03 16:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-03 16:08 Access to bytes from the raw audio stream? (AC'97) John Graham
2010-02-03 16:17 ` Mark Brown [this message]
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=20100203161737.GC12034@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=johngavingraham@googlemail.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).