| Age | Commit message (Collapse) | Author |
|---|
|
|
|
kernel thread of its own. the api has changed (which will be fixed in the
manpage shortly) so all the users of sensor tasks that i can find have
been fixed too.
noone tested, so its going in to force people to run with it.
"put it in" deraadt@
|
|
deref in sensor_task_work(); found by krw, dlg should talk to him
|
|
apologies to art for abusing timeouts so badly. apologies to tedu for
making his head hurt.
tested by and ok tedu@
|
|
of new fields in the future is less disruptive. This is done similar
to how struct proc is handled for ps(1). ok jmc (man page changes)
tested fkr simon, and more suggestions from millert
|
|
Constantine A. Murenin
|
|
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@
|
|
ok henning
|
|
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
|
|
|
|
sensors on attach/detach. hotplugd changes following in a minute.
ok henning.
|
|
|
|
henning). Idea from mbalmer. 'in it goes!' deraadt.
|
|
it in sensors.h.
from Constantine A. Murenin
|
|
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@
|
|
sensor_add()/sensor_del() so that sensors can be attached
and detached dynamicaly.
ok kettenis@ deraadt@ dlg@
|
|
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@
|
|
mostly ok otto@ (ive since fixed the chunk he was worried about)
|
|
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.
|
|
hairy at the moment, but its going into the tree so it can be worked on
and used.
|
|
tested on GENERIC and RAMDISK_CD to see if the small_kernel stuff stays
happy
|
