All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: David Henningsson <david.henningsson@canonical.com>
Cc: ALSA Development Mailing List <alsa-devel@alsa-project.org>,
	kailang@realtek.com
Subject: Re: [PATCH] ALSA: HDA: Add new revision for ALC662
Date: Mon, 24 Oct 2011 13:24:06 +0200	[thread overview]
Message-ID: <s5hfwiivdih.wl%tiwai@suse.de> (raw)
In-Reply-To: <4E9E9D53.1030502@canonical.com>

At Wed, 19 Oct 2011 11:50:11 +0200,
David Henningsson wrote:
> 
> We found a new chip, with Vendor Id: 0x10ec0662 and Revision Id: 
> 0x100300. It seems to work well with patch_alc662, but I don't know if 
> patch_alc882 had been better, and actually, I don't know if there's much 
> of a difference between the two patch functions these days anyway.
> 
> I'm cc:ing Kailang in case there's more to it (codec renaming, 
> processing coefficients etc) that we don't know of.

OK, now I committed with the ack by Kailang.


thanks,

Takashi

      reply	other threads:[~2011-10-24 11:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-19  9:50 [PATCH] ALSA: HDA: Add new revision for ALC662 David Henningsson
2011-10-24 11:24 ` 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=s5hfwiivdih.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=david.henningsson@canonical.com \
    --cc=kailang@realtek.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.