From: "Ozan Çağlayan" <ozan@pardus.org.tr>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: Model quirks and duplicate device IDs
Date: Tue, 07 Jul 2009 10:47:25 +0300 [thread overview]
Message-ID: <4A52FD8D.90805@pardus.org.tr> (raw)
In-Reply-To: <s5hljn1auaj.wl%tiwai@suse.de>
Takashi Iwai wrote:
>>
>> So how should we act on those situations seen that we can't match against DMI data(which would possibly be crap on those laptops)?
>>
>
> We can check the codec SSID as well. If both PCI and codec SSID are
> identical, it's very likely that these are same models, but just a
> wrong model was chosen, or the model was changed during development
> and doesn't match properly any more.
>
This is the one which is reported to work well with model=toshiba:
PCI SSID: 152d:0763
Codec: Realtek ALC268
Codec SSID: 0x152d0763
More info at:
http://www.alsa-project.org/db/?f=83c7d7cd0beec0ae4c926f162a31e4df430c20b5
This is the one reported at which is mapped to model=acer in 2007:
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=3343
# cat /proc/asound/card0/codec#0
Codec: Realtek ALC268
Address: 0
Vendor Id: 0x10ec0268
Subsystem Id: 0x152d0763
$ lspci -nv
00:00.0 0600: 8086:2a00 (rev 03)
Subsystem: 152d:0763
Flags: bus master, fast devsel, latency 0
Capabilities: <access denied>
prev parent reply other threads:[~2009-07-07 7:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-06 18:56 Model quirks and duplicate device IDs Ozan Çağlayan
2009-07-07 6:20 ` Takashi Iwai
2009-07-07 7:47 ` Ozan Çağlayan [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=4A52FD8D.90805@pardus.org.tr \
--to=ozan@pardus.org.tr \
--cc=alsa-devel@alsa-project.org \
--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