Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760668AbZDWXFf (ORCPT ); Thu, 23 Apr 2009 19:05:35 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755605AbZDWXFZ (ORCPT ); Thu, 23 Apr 2009 19:05:25 -0400 Received: from vms173007pub.verizon.net ([206.46.173.7]:42134 "EHLO vms173007pub.verizon.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755316AbZDWXFY (ORCPT ); Thu, 23 Apr 2009 19:05:24 -0400 Date: Thu, 23 Apr 2009 19:05:09 -0400 (EDT) From: Len Brown X-X-Sender: lenb@localhost.localdomain To: Ingo Molnar Cc: x86@kernel.org, Linux Kernel Mailing List , Venkatesh Pallipadi , linux-acpi@vger.kernel.org, "H. Peter Anvin" , Thomas Gleixner Subject: Re: [PATCH] x86/hpet: prevent boot hang when hpet=force used on old ICH In-reply-to: <20090423060936.GA1917@elte.hu> Message-id: References: <20090423060936.GA1917@elte.hu> User-Agent: Alpine 2.00 (LFD 1167 2008-08-23) MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 705 Lines: 18 Ingo, Thanks for the reply. But please disregard that patch -- we've cooked up a better one that allows ICH4M to continue to use hpet=force, even for clocksource. (and it is an ACPI patch rather than an x86 patch:-) However, I'll also send a 2nd patch to stop soliciting more hpet=force users, since technically we shouldn't be encouraging the use of this un-documented and lightly-validated hardware. thanks, Len Brown, Intel Open Source Technology Center -- 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/