From: Andrei Tanas <andrei@tanas.ca>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, Wu Fengguang <wfg@linux.intel.com>
Subject: Re: Asus P5QL-EM motherboard (ALC1200 codec) - no sound through S/PDIF
Date: Thu, 13 Nov 2008 10:59:42 -0500 [thread overview]
Message-ID: <cd166d9b036685894baef8cc5eb86b8d@localhost> (raw)
In-Reply-To: <s5habc3hcyy.wl%tiwai@suse.de>
>> Is there some "official" method of debugging this: is it possible to see
>> what the driver is doing with the data stream fed to it (other than
>> inserting a bunch of printk's in the code)?
>
> You can use hda-verb program to access the codec verbs directly.
> Also you can use the hda-emulator for debugging. But you have the real
> hardware, so it's maybe better to use your own hardware.
>
> The programs can be found in
> ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/misc/
My /dev/snd only has these:
controlC0 pcmC0D0c pcmC0D0p pcmC0D1c pcmC0D1p pcmC0D2c timer
Should there be hw* nodes?
next prev parent reply other threads:[~2008-11-13 15:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-13 2:51 Asus P5QL-EM motherboard (ALC1200 codec) - no sound through S/PDIF Andrei Tanas
2008-11-13 8:16 ` Wu Fengguang
2008-11-13 8:25 ` Takashi Iwai
2008-11-13 14:26 ` Andrei Tanas
2008-11-13 14:27 ` Takashi Iwai
2008-11-13 14:38 ` Andrei Tanas
2008-11-13 14:40 ` Takashi Iwai
2008-11-13 14:48 ` Andrei Tanas
2008-11-13 15:09 ` Takashi Iwai
2008-11-13 14:52 ` Andrei Tanas
2008-11-13 15:17 ` Takashi Iwai
2008-11-13 15:59 ` Andrei Tanas [this message]
2008-11-13 16:02 ` Takashi Iwai
2008-11-13 17:15 ` Takashi Iwai
2008-11-13 18:23 ` Andrei Tanas
[not found] ` <9b7acddf9b27fdc3fea4444c2db912cf@localhost>
2008-11-13 14:22 ` Andrei Tanas
2008-11-13 14:25 ` Takashi Iwai
2008-11-13 14:35 ` Andrei Tanas
2008-11-14 4:58 ` Wu Fengguang
2008-11-14 16:06 ` Andrei Tanas
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=cd166d9b036685894baef8cc5eb86b8d@localhost \
--to=andrei@tanas.ca \
--cc=alsa-devel@alsa-project.org \
--cc=tiwai@suse.de \
--cc=wfg@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.