From: David Henningsson <david.henningsson@canonical.com>
To: Raymond Yau <superquad.vortex2@gmail.com>
Cc: alsa-devel@alsa-project.org, Kailang <kailang@realtek.com>,
Yuval Levy <ylevy@uwo.ca>, Takashi Iwai <tiwai@suse.de>,
1228689@bugs.launchpad.net, David Chen <david.chen@canonical.com>
Subject: Re: Realtek ALC286 SONY Vaio Pro 13 Ubuntu 13.10
Date: Wed, 02 Oct 2013 08:17:44 +0200 [thread overview]
Message-ID: <524BBA88.9040004@canonical.com> (raw)
In-Reply-To: <CAN8cciZJeEg9dYai5kHFFgKgOeVTBTKAXdPzNUkuYN_V0v067g@mail.gmail.com>
On 10/02/2013 07:09 AM, Raymond Yau wrote:
>>>
>>> I have added this information to the bug report
>>> <https://bugs.launchpad.net/bugs/1228689>
>>> where I also post my comments so that they are more persistent and
>>> available to other users with similar issues.
>>>
>
> http://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/?id=abdd8f510686da0a58e475bc0143d1069e5f53da
>
> ALSA: hda - Apply ALC269 VAIO fix-up to all Sony laptops with ALC269
> We've applied a fix-up for ALC269 VAIO only for two models. But all Sony
> VAIO models with ALC269 codec seem to require the similar fix.
> Let's apply it with vendor-id mask.
>
> Does it mean that the Fixup need to check whether node 0x19 must be valid
> Mic pin if Sony Vaio pro 13 alc286 does not use node 0x19?
Yeah, that's a valid point - we should try different vref values for pin
0x18 to see if any of them works to enable headset mic (and possibly
also get rid of the noise in headphones).
--
David Henningsson, Canonical Ltd.
https://launchpad.net/~diwic
prev parent reply other threads:[~2013-10-02 6:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <524652C0.5040207@uwo.ca>
2013-09-30 7:50 ` Realtek ALC286 SONY Vaio Pro 13 Ubuntu 13.10 David Henningsson
[not found] ` <524A67F1.5020300@uwo.ca>
2013-10-01 6:28 ` David Henningsson
[not found] ` <524B8139.2040309@uwo.ca>
2013-10-02 4:51 ` David Henningsson
2013-10-02 5:09 ` Raymond Yau
2013-10-02 6:17 ` David Henningsson [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=524BBA88.9040004@canonical.com \
--to=david.henningsson@canonical.com \
--cc=1228689@bugs.launchpad.net \
--cc=alsa-devel@alsa-project.org \
--cc=david.chen@canonical.com \
--cc=kailang@realtek.com \
--cc=superquad.vortex2@gmail.com \
--cc=tiwai@suse.de \
--cc=ylevy@uwo.ca \
/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;
as well as URLs for NNTP newsgroup(s).