linux-kernel - x86: Fix HPET for Fujitsu u9200

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 16 Dec 2008 13:39:57 +0200
From:	Janne Kulmala <janne.t.kulmala@....fi>
To:	x86@...nel.org, linux-kernel@...r.kernel.org
Subject: x86: Fix HPET for Fujitsu u9200

HPET timer is listed in the ACPI table, but needs a quirk entry in order to
work. Unfortunately, the quirk code runs after first HPET hpet_enable() which
has already determined that the timer doesn't work (reads 0xFFFFFFFF). This
patch allows hpet_enable() to be called again after running the quirk code.

Signed-off-by: Janne Kulmala <janne.t.kulmala@....fi>

--- linux-2.6.28/arch/x86/kernel/quirks.c~	2008-12-16 12:58:48.000000000 +0200
+++ linux-2.6.28/arch/x86/kernel/quirks.c	2008-12-16 12:59:14.000000000 +0200
@@ -168,6 +168,8 @@
  			 ich_force_enable_hpet);
  DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_ICH8_1,
  			 ich_force_enable_hpet);
+DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_ICH8_4,
+			 ich_force_enable_hpet);
  DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_ICH9_7,
  			 ich_force_enable_hpet);

--- linux-2.6.28/arch/x86/kernel/hpet.c~	2008-12-16 13:08:06.000000000 +0200
+++ linux-2.6.28/arch/x86/kernel/hpet.c	2008-12-16 13:10:29.000000000 +0200
@@ -811,7 +811,7 @@

  out_nohpet:
  	hpet_clear_mapping();
-	boot_hpet_disable = 1;
+	hpet_address = 0;
  	return 0;
  }


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/