* Model quirks and duplicate device IDs
@ 2009-07-06 18:56 Ozan Çağlayan
2009-07-07 6:20 ` Takashi Iwai
0 siblings, 1 reply; 3+ messages in thread
From: Ozan Çağlayan @ 2009-07-06 18:56 UTC (permalink / raw)
To: alsa-devel
Hi,
A user reports that toshiba model is working fine with its
laptop(Subsystem: 152d:0763). I checked the patch_realtek file and saw
that the exact ID was mapped against ALC268_ACER 2 years ago for ALSA
issue #3343.
Both laptops are not-so-popular local brands and checking against 152d
points to:
152d QUANTA Computer Inc
according to the pci.ids database.
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)?
Thanks,
Ozan Caglayan
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Model quirks and duplicate device IDs
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
0 siblings, 1 reply; 3+ messages in thread
From: Takashi Iwai @ 2009-07-07 6:20 UTC (permalink / raw)
To: Ozan Çağlayan; +Cc: alsa-devel
At Mon, 06 Jul 2009 21:56:57 +0300,
Ozan Çağlayan wrote:
>
> Hi,
>
> A user reports that toshiba model is working fine with its
> laptop(Subsystem: 152d:0763). I checked the patch_realtek file and saw
> that the exact ID was mapped against ALC268_ACER 2 years ago for ALSA
> issue #3343.
>
> Both laptops are not-so-popular local brands and checking against 152d
> points to:
>
> 152d QUANTA Computer Inc
>
> according to the pci.ids database.
>
> 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.
Takashi
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Model quirks and duplicate device IDs
2009-07-07 6:20 ` Takashi Iwai
@ 2009-07-07 7:47 ` Ozan Çağlayan
0 siblings, 0 replies; 3+ messages in thread
From: Ozan Çağlayan @ 2009-07-07 7:47 UTC (permalink / raw)
To: Takashi Iwai; +Cc: alsa-devel
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>
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2009-07-07 7:47 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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.