Date: Thu, 10 Mar 2005 09:52:50 +0100 (CET)
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.11-mm2 vs audio for kino and tvtime
Message-ID: <XO42l8mC.1110444770.5508140.khali@localhost>
In-Reply-To: <200503091927.24558.gene.heskett@verizon.net>
From: "Jean Delvare" <khali@linux-fr.org>
Bounce-To: "Jean Delvare" <khali@linux-fr.org>
CC: "Andrew Morton" <akpm@osdl.org>, linux1394-devel@lists.sourceforge.net,
       video4linux-list@redhat.com, sensors@stimpy.netroedge.com
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7BIT
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1237
Lines: 33


Hi Gene,

> > I've dropped the "id" member of struct i2c_client, as it were
> > useless. Third-party driver authors now need to do the same.
>
> Aha!  As in just 'dd' any line containing the .id in vim?

Exactly. Don't kill all lines with .id though, only the i2c_client id
was dropped, and there are plenty of other ids in the media/video
drivers.

> > THRM is most likely a temperature you get from
> > /proc/acpi/thermal_zone, and isn't related with the w83627hf
> > driver.
>
> Humm, it is the highest temp reported, as is temp2 in gkrellm, so I
> had assumed it was somehow a dup of the diode in the cpu, or of the
> thermistor against the bottom of it inside the socket.  Wrong
> assumption?

Not necessarily wrong. It is possible that the same diode temperature is
read from the W83627HF chip by both the ACPI subsystem and by the
w83627hf driver. But if this is the case, I would be worried by
concurrent I/O accesses to the chip, which could possibly cause trouble.

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