From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jean Delvare Subject: Re: [lm-sensors] Could the k8temp driver be interfering with ACPI? Date: Sun, 18 Feb 2007 18:38:05 +0100 Message-ID: <20070218183805.5a4fd813.khali@linux-fr.org> References: <45D5EA88.7090300@redhat.com> <45D6DDCE.5050803@assembler.cz> <45D7461A.2040808@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: Received: from smtp-100-sunday.nerim.net ([62.4.16.100]:2524 "EHLO kraid.nerim.net" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751659AbXBRRhz (ORCPT ); Sun, 18 Feb 2007 12:37:55 -0500 In-Reply-To: <45D7461A.2040808@redhat.com> Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: Chuck Ebbert Cc: Rudolf Marek , linux-acpi@vger.kernel.org, linux-kernel , lm-sensors@lm-sensors.org On Sat, 17 Feb 2007 13:14:50 -0500, Chuck Ebbert wrote: > Well I had an idea after looking at k8temp -- why not make it default to > doing only reads from the sensor? You'd only get information from whatever > core/sensor combination that ACPI had last used, but it would be safe. ACPI is broken here, not k8temp, so let's fix ACPI instead. ACPI doesn't conflict with only k8temp, but with virtually all hardware monitoring drivers, all I2C/SMBus drivers, and probably other types of drivers too. We just can't restrict or blacklist all these drivers because ACPI misbehaves. -- Jean Delvare