From: Takashi Iwai <tiwai@suse.de>
To: Gabriele Martino <g.martino@gmx.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: Intel HDA / ca0132: support for Alienware 15 Creative Sound Core3D-EX
Date: Mon, 27 Apr 2015 20:51:29 +0200 [thread overview]
Message-ID: <s5h4mo14d72.wl-tiwai@suse.de> (raw)
In-Reply-To: <553E7B34.2080501@gmx.com>
At Mon, 27 Apr 2015 20:08:52 +0200,
Gabriele Martino wrote:
>
> On 27/04/2015 11:09, Takashi Iwai wrote:
> > In general, we check either PCI or codec SSID to identify the model
> > and applies the quirk accordingly. Does your board have also a unique
> > SSID?
> Good question. How do I find it? I can't see any in alsa-info.
>
> !!Advanced information - PCI Vendor/Device/Subsystem ID's
> !!-------------------------------------------------------
>
> 00:03.0 0403: 8086:0c0c (rev 06)
> Subsystem: 1028:0685
> --
> 00:1b.0 0403: 8086:8c20 (rev 05)
> Subsystem: 1028:0685
PCI SSID is 1028:0685.
> Codec: Creative CA0132
> Address: 0
> AFG Function Id: 0x1 (unsol 1)
> Vendor Id: 0x11020011
> Subsystem Id: 0x10280685
Codec SSID is also 1028:0685.
Takashi
next prev parent reply other threads:[~2015-04-27 18:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-25 0:50 Intel HDA / ca0132: support for Alienware 15 Creative Sound Core3D-EX Gabriele Martino
2015-04-27 9:09 ` Takashi Iwai
2015-04-27 18:08 ` Gabriele Martino
2015-04-27 18:51 ` Takashi Iwai [this message]
2015-04-27 22:17 ` Gabriele Martino
2015-04-28 6:15 ` Takashi Iwai
2015-04-28 22:47 ` Gabriele Martino
2015-04-29 13:38 ` Takashi Iwai
2015-04-29 15:42 ` Gabriele Martino
2015-04-29 18:42 ` Takashi Iwai
2015-04-29 23:40 ` Gabriele Martino
2015-04-30 5:51 ` Takashi Iwai
2015-05-01 0:36 ` Gabriele Martino
2015-05-03 23:53 ` Gabriele Martino
2015-05-04 12:30 ` Takashi Iwai
2015-05-04 23:28 ` Gabriele Martino
2015-05-11 20:17 ` Gabriele Martino
2015-05-18 9:39 ` Takashi Iwai
2015-05-18 19:15 ` Gabriele Martino
2015-05-19 4:59 ` Takashi Iwai
2015-04-29 13:40 ` Takashi Iwai
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=s5h4mo14d72.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=g.martino@gmx.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 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).