| 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: <200805211752.15670.david-b@pacbell.net> Date: Wed, 21 May 2008 17:52:15 -0700 From: David Brownell <david-b@...bell.net> To: Jean Delvare <khali@...ux-fr.org> Cc: spi-devel-general@...ts.sourceforge.net, Jonathan Cameron <Jonathan.Cameron@...il.com>, Dmitry Torokhov <dtor@...l.ru>, linux-kernel@...r.kernel.org, LM Sensors <lm-sensors@...sensors.org> Subject: Re: Accelerometer, Gyros and ADC's etc within the kernel. On Tuesday 20 May 2008, Jean Delvare wrote: > This all sounds quite different from our hwmon drivers. Our hwmon > drivers read all the sensor values at once and cache the readings for a > couple seconds, so you can't get an instant reading at any time, and > they also don't support interrupts in general. That's something of an issue when the hardware monitor triggers alarms though, right? I couldn't figure out how to get a TMP75 alert out to any userspace code that would care, to pick one example, even after teaching the i2c core how to handle SMBus alerts. ;) I suppose this just emphasizes the point made by Hans that we kind of need (industrial) "control" components (or "data acquisition"?) not just "monitoring" ones. Such alarms are of course different from the "data ready" signals of an accelerometer. - Dave -- 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