Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755546AbXIDP1b (ORCPT ); Tue, 4 Sep 2007 11:27:31 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754568AbXIDP1Y (ORCPT ); Tue, 4 Sep 2007 11:27:24 -0400 Received: from ns1.suse.de ([195.135.220.2]:38298 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754461AbXIDP1X (ORCPT ); Tue, 4 Sep 2007 11:27:23 -0400 From: Andi Kleen To: Alistair John Strachan Subject: Re: 2.6.23-rc4-mm1 Date: Tue, 4 Sep 2007 16:26:27 +0100 User-Agent: KMail/1.9.1 Cc: Nicolas Mailhot , linux-kernel@vger.kernel.org References: <20070902045634.06ea0515@loke.fish.not> <200709041620.47213.alistair@devzero.co.uk> In-Reply-To: <200709041620.47213.alistair@devzero.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200709041626.27945.ak@suse.de> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 907 Lines: 20 > Seconded. It's been largely ignored which is annoying because the HPET > works perfectly on this board. I assume the reason is still that nobody > from NVIDIA verified hardward support for the hack. It's IMHO a bad idea to add any overrides without access to data sheets and errata sheets. The hardware might be broken and do bad (subtle) bad things with HPET. That's not a theoretical case. There used to be at least one case where a chipset would occasionally destroy the BIOS flash when HPET was force enabled. That means for Intel it's fine to do (because errata sheets are public); but for Nvidia and VIA it's dangerous and should not be done. -Andi - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/