From: Thierry Vignaud <tvignaud@mandrakesoft.com>
To: Lee Revell <rlrevell@joe-job.com>, Takashi Iwai <tiwai@suse.de>
Cc: Brice.Goglin@ens-lyon.org, alsa-devel@lists.sourceforge.net
Subject: Re: support for PCI_DEVICE_ID_INTEL_ICH6_15
Date: Tue, 23 Nov 2004 12:50:14 +0100 [thread overview]
Message-ID: <m2zn18vl6x.fsf@vador.mandrakesoft.com> (raw)
In-Reply-To: <1100975509.6879.31.camel@krustophenia.net> (Lee Revell's message of "Sat, 20 Nov 2004 13:31:48 -0500")
Lee Revell <rlrevell@joe-job.com> writes:
> Sorry I missed the 'HD Audio' part. I think you want the 'azx' driver:
>
> http://sourceforge.net/mailarchive/message.php?msg_id=8912810
>
> AFAIK Intel posted this driver and it was committed to CVS but we have
> no user feedback yet. So it should be considered experimental, though
> it should work. It would be good to know how it works...
no it didn't.
from my locally cvs2cl-generated changelog:
(...)
2004-07-28 16:55 tiwai
* doc/azx.txt, pci/Kconfig, pci/Makefile: Added Intel ICH6 HD Audio
(Azalia) driver.
(...)
the actual driver is currently missing from CVS...
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
next prev parent reply other threads:[~2004-11-23 11:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-20 17:27 support for PCI_DEVICE_ID_INTEL_ICH6_15 Brice Goglin
2004-11-20 17:48 ` Lee Revell
2004-11-20 18:31 ` Lee Revell
2004-11-20 19:37 ` Lee Revell
2004-11-22 10:58 ` Takashi Iwai
2004-11-22 22:24 ` azx and PCI_DEVICE_ID_INTEL_ICH6_15 Brice Goglin
2004-11-23 11:50 ` Thierry Vignaud [this message]
2004-11-23 11:52 ` support for PCI_DEVICE_ID_INTEL_ICH6_15 Thierry Vignaud
[not found] <92C0412E07F63549B2A2F2345D3DB515F7D583@cm-msg-02.cmedia.com.tw>
[not found] ` <419FAAE7.5080208@ens-lyon.fr>
2004-11-20 20:38 ` Lee Revell
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=m2zn18vl6x.fsf@vador.mandrakesoft.com \
--to=tvignaud@mandrakesoft.com \
--cc=Brice.Goglin@ens-lyon.org \
--cc=alsa-devel@lists.sourceforge.net \
--cc=rlrevell@joe-job.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox