force a new sensor task to be run as soon as possible. previously it used
to have to wait its timeout before the first run, which led to some
weird values or states being visible after boot, but befo

force a new sensor task to be run as soon as possible. previously it used
to have to wait its timeout before the first run, which led to some
weird values or states being visible after boot, but before the first
update.

for jolan@

show more ...

Remove device id from hotplug events.

ok henning

intrducing device type DV_SENSOR turned out to be a bad idea as it
affects way more than just hotplug messages. remove DV_SENSOR and use
DV_DULL for the moment. proper solution coming.
discussed with

intrducing device type DV_SENSOR turned out to be a bad idea as it
affects way more than just hotplug messages. remove DV_SENSOR and use
DV_DULL for the moment. proper solution coming.
discussed with deraadt mk jason

show more ...

need <sys/device.h> or it doesn't compile on sparc64

Include device id in hotplug events. This will be used by ntpd to check
sensors on attach/detach. hotplugd changes following in a minute.

ok henning.

unbreak, of course this needs to included sys/hotplug.h too

Make sensor add/remove create hotplug events (after much prodding from henning). Idea from mbalmer. 'in it goes!' deraadt.

sensors_head is only used in kern_sensors.c, so its unnecessay to declare
it in sensors.h.

from Constantine A. Murenin

get rid of the sensors globals. theyre were only used by sysctl for
locating and finding the correct sensor to spit out. instead provide a
a sensor_get function that wraps up the access to the vars.

get rid of the sensors globals. theyre were only used by sysctl for
locating and finding the correct sensor to spit out. instead provide a
a sensor_get function that wraps up the access to the vars. theyre now
safe inside kern_sensors.c.

theres also a touch of whitespace tweaking

ok grange@

show more ...

Replace SENSOR_ADD() macro with a pair of functions
sensor_add()/sensor_del() so that sensors can be attached
and detached dynamicaly.

ok kettenis@ deraadt@ dlg@

rename the sensor globals to names that are not obvious to avoid
collisions with local variable names someone might make. this has bitten
me twice now and caused me to lose about 4 hours scratching m

rename the sensor globals to names that are not obvious to avoid
collisions with local variable names someone might make. this has bitten
me twice now and caused me to lose about 4 hours scratching my head when
nsensors just magically corrupts and gets bigger. at least my ram isnt
screwed.

ok marco@

show more ...

shorten this a bit through better use of TAILQ macros.

mostly ok otto@ (ive since fixed the chunk he was worried about)

the tasklist can be modified while the kthread is sleeping, so refetch
the first element before iterating through the rest of them. stylistic
guidance from angela pascoe.

mark all tasks using the sa

the tasklist can be modified while the kthread is sleeping, so refetch
the first element before iterating through the rest of them. stylistic
guidance from angela pascoe.

mark all tasks using the same argument as not running anymore, rather than
just the first one we bump into.

show more ...

first go at a generic kthread for sensors to be run out of. its a bit
hairy at the moment, but its going into the tree so it can be worked on
and used.

split the sensors stuff out into a source file of its own.

tested on GENERIC and RAMDISK_CD to see if the small_kernel stuff stays
happy