Date: Sat, 22 Aug 2009 18:29:23 +0200 From: Alexander Leidinger <Alexander@Leidinger.net> To: Marc Balmer <marc@msys.ch> Cc: =?ISO-8859-1?Q?Aur=E9lien_M=E9r=E9?= <kindman@amc-os.com>, Oliver Pinter <oliver.pntr@gmail.com>, Gonzalo Nemmi <gnemmi@gmail.com>, freebsd-hackers@FreeBSD.org Subject: Re: Common interface for sensors/health monitoring Message-ID: <20090822182923.000064e0@unknown> In-Reply-To: <2DC22872-96F5-4C0A-82E4-F9755A10E245@msys.ch> References: <D3D19C706C2842389C87590424D0A8CB@kmlaptop> <6101e8c40908211917k69c82491w3cff00a527d14873@mail.gmail.com> <19e9a5dc0908212303j28a6913er604bfd06e7df81ec@mail.gmail.com> <2DC22872-96F5-4C0A-82E4-F9755A10E245@msys.ch>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 22 Aug 2009 08:50:23 +0200 Marc Balmer <marc@msys.ch> wrote: > The OpenBSD sensors framework lacks some desireable features, e.g. > event capabilities like getting an event if a certain threshold is > exceeded. And it propbably was used for things that it better had This assumes the kernel is monitoring the device periodically (in the general case, as there are a lot of dump sensors which do not send events on their own). The framework as in the SoC did not provide this feature to keep the kernel part simple. You want to see a value, you poll the kernel for it, and the userland would have been responsible to fire up an event. For smart sensors which trigger an event on their own (interrupt), you can use the exiting kernel event framework (and the idea in the SoC was to use it for such sensors). The devd is the userland side of it. > not (yes, I am culprit for on of these (ab)uses...). > > I am sure these features could be added if only the code was in the > tree to hack on... The event stuff is in the kernel, go ahead and write a driver for your smart sensor which fires events on its own. Bye, Alexander.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090822182923.000064e0>