linux-kernel - Re: [PATCH v3] hpet: Detect hidden HPET on NVidia motherboards

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-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20070420154157.63c09794.akpm@linux-foundation.org>
Date:	Fri, 20 Apr 2007 15:41:57 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Mikko Tiihonen <mikko.tiihonen@....fi>
Cc:	Andi Kleen <andi@...stfloor.org>, linux-kernel@...r.kernel.org,
	Andy Currid <ACurrid@...dia.com>
Subject: Re: [PATCH v3] hpet: Detect hidden HPET on NVidia motherboards

On Wed, 18 Apr 2007 00:57:48 +0300
Mikko Tiihonen <mikko.tiihonen@....fi> wrote:

> Enables HPET for NVidia motherboards with broken BIOS. The patch reads
> the HPET address from the pci config space. The patch should also work
> if ACPI is disabled.
> 
> The new quirk activates use of HPET only run if
> - CONFIG_HPET_NFORCE_DETECT is enabled
> - nohpet boot option is not set
> - main chipset is from NVidia
> - ACPI tables do not list HPET
> - matching PCI ID for device with HPET is found
> - BIOS has set up the HPET to some address
> - there is no other resource allocated at the HPET address
> 
> This is true at least for some Asus, Gigabyte and DFI motherboards.
> 
> Patch is against 2.6.21-rc6-git7 but should apply cleanly to most
> kernels.

I looked at applying this but

a) there have been rather a lot of underlying changes in Andi's devel tree and

b) we still haven't heard from Andy?

-
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/