| 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: <20100206104251.1be31941@neptune.home> Date: Sat, 6 Feb 2010 10:42:51 +0100 From: Bruno Prémont <bonbons@...ux-vserver.org> To: "Chris Verges" <chrisv@...erswitching.com> Cc: "Greg Kroah-Hartman" <gregkh@...e.de>, <linux-usb@...r.kernel.org>, <linux-kernel@...r.kernel.org>, "Rob Owings" <rowings@...rmistor.com>, lm-sensors@...sensors.org Subject: Re: [PATCH] linux-2.6.32-directemp On Thu, 04 February 2010 "Chris Verges" wrote: > Attached is a patch for the QTI DirecTEMP USB thermometer & > thermometer/hygrometer sensors. This patch is based on linux-2.6.32. > Functionality has been verified against both hardware variants listed > in the driver (0x0002 and 0x0006), as both monolithic and modular. > > When the QTI DirecTEMP sensor is connected to a system, the directemp > driver adds appropriate sysfs entries for the sensor type(s) > supported. Examples: > > # PID 0x0002 (temp only) > /sys/bus/usb/devices/.../temp > > # PID 0x0006 (temp + relative humidity) > /sys/bus/usb/devices/.../temp > /sys/bus/usb/devices/.../rh > > Using a standard "cat" will display the value. Wouldn't it make sense to make use of hardware monitoring interfaces so lm_sensors could handle the sensor information? (added to CC) This would also be a good reason to have the driver on kernel side rather than somewhere in userspace. Bruno -- 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