From: Mads Kiilerich <mads@kiilerich.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: Support for ALC662 on FUJITSU SIEMENS AMILO Li3710
Date: Sun, 26 Jul 2009 19:39:28 +0200 [thread overview]
Message-ID: <4A6C94D0.8040705@kiilerich.com> (raw)
In-Reply-To: <s5hskgjddzq.wl%tiwai@suse.de>
Takashi Iwai wrote, On 07/26/2009 10:50 AM:
> At Sun, 26 Jul 2009 00:54:24 +0200,
> Mads Kiilerich wrote:
>
>> On a friends FUJITSU SIEMENS AMILO Li3710 10601011427 sound didn't work
>> with kernel-PAE-2.6.29.6-213.fc11.i686
>>
> How about with the latest alsa-driver snapshot?
> ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz
>
Thanks.
I looked at your sound-2.6.git tree and found no quirk for this card
(AFAICS) and assumed that it hadn't been reported and fixed yet. I
assume that that tree is pretty close to alsa-driver-snapshot?
I am a developer, but for alsa I am a user, no expert, and honestly I
don't plan to become one. Can you give a pointer to a description of how
can I test the snapshot? On Fedora 11?
(http://www.alsa-project.org/main/index.php/Main_Page has a "How do I
install the ALSA driver from source" link, but it just points to the
download page without any explanation.)
> Also, please give alsa-info.sh output. Run with --no-upload and attach
> the generated file.
>
I became aware of that command after having visited my friend. I have
output of dmesg and lshal and lspci - is that sufficient?
/Mads
next prev parent reply other threads:[~2009-07-26 17:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-25 22:54 Support for ALC662 on FUJITSU SIEMENS AMILO Li3710 Mads Kiilerich
2009-07-26 8:50 ` Takashi Iwai
2009-07-26 17:39 ` Mads Kiilerich [this message]
2009-07-27 6:14 ` Takashi Iwai
2009-07-27 10:04 ` Mads Kiilerich
2009-07-27 10:10 ` Takashi Iwai
2009-08-19 22:45 ` Mads Kiilerich
2009-08-20 6:28 ` Takashi Iwai
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=4A6C94D0.8040705@kiilerich.com \
--to=mads@kiilerich.com \
--cc=alsa-devel@alsa-project.org \
--cc=tiwai@suse.de \
/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.