| Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
per-sensor structure a long time ago. Garbage collect the old structure
member which is now unused.
|
|
No functional change intended, and atf tests (using swsensor(4)) still
pass 100%
|
|
And also, changind space(s) in the middle with '-'.
PR#47232.
|
|
- don't assume that all batteries have exactly one ENVSYS_INDICATOR
- check capacity and charge sensors for ENVSYS_SVALID before using them
now this works on macppc
|
|
( thanks martin@ )
|
|
for defflagging these.
|
|
|
|
2. Update handling of FMONCRITICAL event reporting. The state
transition does not require a corresponding change in value.
With these changes, you can now have an INDICATOR sensor that
reports the presence or absence of a device, and (if the device
is present) separately monitor it for proper functioning.
Should address the concerns expressed recently with the commit
of changes to wmi(4) BBU handling.
|
|
|
|
|
|
While here, clean up a couple of comments.
|
|
to reset (via envstat -S)
|
|
entropy gathering), allow it to be updated for the current request to
add a real entry.
|
|
|
|
callback to update the value can be polled to provide rnd(4) entropy.
|
|
hook the sensor into rnd subsystem, and make sure we periodically
refresh the sensor whether or not it is being actively monitored.
|
|
all the associated events.
|
|
|
|
1) Move core entropy-pool code and source/sink/sample management code
to sys/kern from sys/dev.
2) Remove use of NRND as test for presence of entropy-pool code throughout
source tree.
3) Remove use of RND_ENABLED in device drivers as microoptimization to
avoid expensive operations on disabled entropy sources; make the
rnd_add calls do this directly so all callers benefit.
4) Fix bug in recent rnd_add_data()/rnd_add_uint32() changes that might
have lead to slight entropy overestimation for some sources.
5) Add new source types for environmental sensors, power sensors, VM
system events, and skew between clocks, with a sample implementation
for each.
ok releng to go in before the branch due to the difficulty of later
pullup (widespread #ifdef removal and moved files). Tested with release
builds on amd64 and evbarm and live testing on amd64.
|
|
or ram.
|
|
Hotkey press/release events now happen in the correct order.
|
|
lets the atf tests run again.
Move validation of current value vs min/max into the refresh routine
where it will get checked every time, not just at initialization.
While here, do a little more housekeeping:
- Retrieve numeric property value once
- Ensure that a numeric-specified sensor type is valid
- printout any unrecognized properties (DEBUG only)
|
|
does not properly initialize sensor state.
|
|
|
|
|
|
|
|
|
|
types, allow the user to specify the type using the units description.
XXX Numeric specification is still permitted but will be removed soon.
|
|
type.
|
|
Battery-Charge sensors. Fix this.
|
|
the source file by ~100 lines, and amd64 object file shrinks by
~650 bytes.
No functional change intended.
|
|
Battery-charge sensors.
|
|
|
|
remove value_avg from the prop_dict. We can't completely remove it
because there's one driver that uses this field for its own private
purposes, so for now we just rename the member.
|
|
as setting the ENVSYS_FPERCENT flag
|
|
and can't be disabled). Add critical pool hooks for kernel tickled
watchdogs.
|
|
callout immediately rather than waiting for the previous timer to
expire.
|
|
|
|
Fix a problem with envstat -S call which was installing bogus/random
limits.
ok pgoyette.
|
|
using "-i value=<value>".
Suggested by njoly@
|
|
than duplicating the code every time. Minor reduction in code size
(about 1200 bytes on amd64), no change in functionality.
|
|
provide their own internal limit(s).
|
|
sensor types
|
|
whether the properties actually exist.
When setting new limit values, don't complain/ignore about duplicate
values if the associated flag bits (indicating that the limit is valid)
are not set.
These two fixes together should fix a problem reported in private Email
by njoly@ a couple months ago. Issue replicated and solution tested
using my recent swsensor pseudo-device running inside qemu world!
|
|
|
|
tried to cpu_reboot() from a callout. Make it reboot from a workq
instead.
problem made manifest
by atf test
rumpfs unmount flush
caused issue to un-shush
tested: rump kernel (tests/dev/sysmon) and qemu
|
|
is of course still used by kernel&config pseudodev.
pointed out by jakllsch
|