From: Takashi Iwai <tiwai@suse.de>
To: randall <rlrathbun@roadrunner.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: Nvida HDA MCP61 - Realtek ALC622 question
Date: Thu, 19 Jun 2008 11:49:33 +0200 [thread overview]
Message-ID: <s5hlk1192ky.wl%tiwai@suse.de> (raw)
In-Reply-To: <200806160923.40663.rlrathbun@roadrunner.com>
At Mon, 16 Jun 2008 09:23:40 -0700,
randall wrote:
>
> Andy:
>
> Who works on the snd-hda-intel sound module? I have been unable to get the
> codec working on my Athlon 64 3200+ processor (64 bit libs) despite gradually
> working my way up from Alsa 1.0.14 to 1.0.17.git and fighting YaST2 issues
> with Suse 10.3
>
> Since I do software development, I'd like to add my $0.02 worth of coding to
> get the Alsa code working for my ECS EliteGroup motherboard as I have seen
> others posting to the web frustrated by the same problem (indeed openSuse has
> a web site devoted to soundcard issues, but no one has yet fixed this
> problem)
Better to report it to bugzilla.novell.com for openSUSE problems.
At least, I didn't know of this problem at all.
Takashi
prev parent reply other threads:[~2008-06-19 9:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-16 16:23 Nvida HDA MCP61 - Realtek ALC622 question randall
2008-06-19 9:49 ` Takashi Iwai [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=s5hlk1192ky.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=rlrathbun@roadrunner.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.