Hi Takashi,
It maybe wrong format for verb table of 0x1d. I think the verb table was not create by Realtek AE. EAPD need to high level for this case. But its SSID was not assigned. It didn't use fixup table to support it.
1. Create SVID and SSID 2. Change BIOS verb table of 0x1d
I will check with our AE for the verb table setting.
BR, Kailang
-----Original Message----- From: Takashi Iwai [mailto:tiwai@suse.de] Sent: Monday, October 06, 2014 10:56 PM To: Greg Farrell Cc: alsa-devel@alsa-project.org; Jaroslav Kysela; Kailang Subject: Re: Patch to enable audio on alc888 vendor id 0x10ec0888 revision id 0x100202
At Mon, 06 Oct 2014 15:52:36 +0100, Greg Farrell wrote:
On 06/10/14 15:24, Takashi Iwai wrote:
Is the chip really identified as ALC888 by the driver?
Please give
alsa-info.sh output (run with --no-upload option), just
to be sure.
The same codec ID (10ec:0888) is used by various chips, so we may need to use a different thing to check the validity of alc888_coef_init() application. thanks, Takashi
It is. One other thing of note is that there is a 'SKU not
ready' error.
This message is irrelevant. It means just that the codec SSID isn't set in Realtek-compliant way.
I originally intended to just cut & paste enough content from the alsa-info.sh output file to show it is detected as a ALC888
chip but
figured that I was better giving you everything rather than
filtering
based on what I feel is helpful to you. Apologies for the
size of the email.
Yep, that's more helpful indeed.
I'll wait for Kailang's comment on this issue.
thanks,
Takashi
------Please consider the environment before printing this e-mail.