From: draco <draco31.fr@free.fr>
To: alsa-devel@alsa-project.org
Subject: ALSA: HDA VIA VT2020 support
Date: Sun, 27 Dec 2009 17:59:45 +0100 [thread overview]
Message-ID: <4B379281.7040401@free.fr> (raw)
Hello,
I saw in the devel archive that the support for VIA VT2020 chipset have
been added and merged to 1.0.22 released.
(cf.
http://mailman.alsa-project.org/pipermail/alsa-devel/2009-October/022183.html
and http://www.alsa-project.org/main/index.php/Changes_v1.0.21_v1.0.22 )
Unfortunately, despite all was OK from the 1.0.21+git devel snapshot few
month ago, the alsa-driver v1.0.22 doesn't work.
I tried different snapshot from 1.0.22, and sent a bug report here :
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=4857
I don't know what I can do more to resolve the bug, but I can make some
other tests and give you more log if needed.
NB : I don't subscribe the devel mailing list, but I am "monitoring" the
above bug report.
Thank's in advance.
Best Regards,
draco
next reply other threads:[~2009-12-27 16:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-27 16:59 draco [this message]
2009-12-28 10:33 ` ALSA: HDA VIA VT2020 support Daniel Chen
2009-12-30 15:26 ` draco
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=4B379281.7040401@free.fr \
--to=draco31.fr@free.fr \
--cc=alsa-devel@alsa-project.org \
/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