summaryrefslogtreecommitdiff
path: root/MAINTAINERS
diff options
context:
space:
mode:
authorAlistair John Strachan <alistair@devzero.co.uk>2009-09-15 17:18:10 +0200
committerJean Delvare <khali@linux-fr.org>2009-09-15 17:18:10 +0200
commitbbe5939ab1834f79f177739cb84904bc12d08073 (patch)
treeca90a7d9b19f76602de5821493786b780f1b5793 /MAINTAINERS
parent18240904960a39e582ced8ba8ececb10b8c22dd3 (diff)
downloadlwn-bbe5939ab1834f79f177739cb84904bc12d08073.tar.gz
lwn-bbe5939ab1834f79f177739cb84904bc12d08073.zip
hwmon: (abituguru3) Support multiple DMI strings per chip ID
Most known Abit motherboards have unique uguru chip IDs. However, some "refresh" boards keep the same chip ID but have a different DMI string. As our DMI board string matching is (necessarily) strict, some boards were failing DMI detection, and as the old probe method was also failing, the driver would not load. The only known boards affected by this problem are the IP35 Pro XE (vs IP35 Pro) and the AB9 Pro (vs AB9). Is it not sufficient to relax the match criteria, as some boards (e.g. the AB9 Quad GT) have different uguru chip IDs. This patch replaces the dmi_name string with a NULL terminated array of strings to be matched per uguru chip ID. It has been compile and runtime tested (thanks Rune). References: https://bugs.launchpad.net/bugs/298798 Signed-off-by: Alistair John Strachan <alistair@devzero.co.uk> Tested-by: Rune Svendsen <runesvend@gmail.com> Acked-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Jean Delvare <khali@linux-fr.org>
Diffstat (limited to 'MAINTAINERS')
0 files changed, 0 insertions, 0 deletions