| 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
| ||
|
Message-ID: <68676e00912110847o3594931etf6e045340043e2c6@mail.gmail.com> Date: Fri, 11 Dec 2009 17:47:29 +0100 From: Luca Tettamanti <kronos.it@...il.com> To: Matthew Garrett <mjg59@...f.ucam.org> Cc: lm-sensors@...sensors.org, linux-kernel@...r.kernel.org Subject: Re: [lm-sensors] [PATCH] hwmon: Add driver for intel PCI thermal subsystem On Fri, Dec 11, 2009 at 5:38 PM, Matthew Garrett <mjg59@...f.ucam.org> wrote: > On Fri, Dec 11, 2009 at 05:36:59PM +0100, Luca Tettamanti wrote: >> On Fri, Dec 11, 2009 at 5:33 PM, Matthew Garrett <mjg59@...f.ucam.org> wrote: >> >> Does it plays nice with other drivers? >> >> More specifically: is it possible to load the native driver and this >> >> one (which I presume pokes at the same chip) at the same time? >> > >> > What do you mean by native driver? This is a native driver for the chip >> > in question. >> >> I mean the driver for the hwmon chip attached to I2C/SMB bus. > > This is the hwmon chip. Sorry, I think we're not understanding each other :) Does the PCH samples the values directly from the probes? Or is it an interface for the real monitoring chip (most likely the superio chip)? In the latter case it might be possible to access directly the monitoring hardware using another driver (e.g. w83627ehf, lm80, etc.), thus racing against the PCI driver. Did I make myself clear? thanks, Luca -- 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