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: <alpine.LFD.1.10.0805100140490.3197@apollo.tec.linutronix.de>
Date:	Sat, 10 May 2008 01:42:30 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Andrew Morton <akpm@...ux-foundation.org>
cc:	Andreas Herrmann <andreas.herrmann3@....com>, mingo@...e.hu,
	hpa@...or.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86: enable hpet=force for AMD SB400

On Fri, 9 May 2008, Andrew Morton wrote:
> On Fri, 9 May 2008 11:49:11 +0200
> Andreas Herrmann <andreas.herrmann3@....com> wrote:
> 
> > x86: enable hpet=force for ATI SB400
> 
> Sigh.
> 
> > Add quirk to allow forced usage of HPET on ATI SB400.
> > I stumbled over machines where HPET is enabled but not reported
> > by BIOS.
> 
> Is there no way in which we can probe for or identify this condition,
> rather than hoping that the user will find out about this boot option?

I'd love to have a sane solution for that, but looking at the rate of
HPET wreckage since we increased the usage of HPET I'm happy to have
this as an opt in thingy.

Thanks,

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ