From: Tobin Davis <tdavis@dsl-only.net>
To: Vinod Koul <vinod.koul@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: ALSA Debugging
Date: Fri, 21 Mar 2008 09:15:41 -0700 [thread overview]
Message-ID: <1206116141.4863.127.camel@razman.gruemaster.com> (raw)
In-Reply-To: <b29ed9aa0803210815g43bd5741i81ee7e5d0a04e612@mail.gmail.com>
First, verify that you are working with the correct driver. lsmod will
tell you which sound drivers are loaded. If this is a newer system,
you're probably using the snd-hda-intel driver, which is a whole lot
different.
Tobin
On Fri, 2008-03-21 at 20:45 +0530, Vinod Koul wrote:
> Hello,
> I am new to ALSA and Linux. I was trying to understand the ALSA
> architecture.
>
> I have Linux Box with Intel sound card. with Suse 10.1 on it.
> I launched the audio player (Real player) and audio plays fine.
>
> Then, I built the kernel and installed it. I put some printk's in intel8x0.cand
> control.c. (could see the my code was complied)
> Even though I changed volume muted etc couldn't see any of my printk in
> dmesg. One default printk in intel8x0.c was there, so I have put my print
> before that line as well, but couldn't see anything.
>
> Apologies If my problem is very basic. I read on forums that best way to
> learn is to put printk's.
>
> Can anyone help me with where I am doing incorrectly, Am I supposed to do it
> this way or some other way?
>
> Thanks in advance
> -Vinod
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
--
Tobin Davis
The man on tops walks a lonely street; the "chain" of command is often a noose.
next prev parent reply other threads:[~2008-03-21 16:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-21 15:15 ALSA Debugging Vinod Koul
2008-03-21 16:15 ` Tobin Davis [this message]
2008-03-24 3:22 ` Vinod Koul
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=1206116141.4863.127.camel@razman.gruemaster.com \
--to=tdavis@dsl-only.net \
--cc=alsa-devel@alsa-project.org \
--cc=vinod.koul@gmail.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