| Age | Commit message (Collapse) | Author |
|
values on temp limits. The actual ranges for temp limits varies if the
chip is running in "extended temperature" mode, so we need to handle this
difference, too.
Verified on my home machine which runs in extended-temp mode and by
njoly@ on a machine which does runs in the older 2s-complement mode.
|
|
|
|
|
|
too.
|
|
limit values from the device driver, remove the high_limit and low_limit
entries from the hw.dbcool<#>.<sensor> sysctl(8) tree. These limits are
now directly accessible via envstat(8). Simplify the remaining code
somewhat.
No objections raised on either tech-kern@ or current-users@
XXX The fan controllers's parameters (including those that are tied to
XXX temperature sensors) are still in sysctl, since there isn't any clean
XXX way to implement the fan controllers in sysmon_envsys yet. It is on
XXX my To-Do list...
|
|
|
|
|
|
of i2c devices, as discussed on tech-kern.
|
|
|
|
Move VID out of sysctl tree - make it a separate sensor of type INTEGER.
Clean-up some of the chip-descriptors.
|
|
and non-const types, and the kernel uses both const and non-const
PMF qualifiers and device suspensors, so change the pmf_qual_t and
device_suspensor_t typedefs from "pointers to const" to non-pointer,
non-const types.
|
|
Fixes PR kern/42736
|
|
From Takahiro HAYASHI in PR kern/40420
|
|
|
|
|
|
limit checking at initialization time. Later on, if user specifics any
unsupported limits, the driver will relinquish this task.
|
|
struct timeval passed to todr_gettime(9) and todr_settime(9).
We no longer have an ancient and volatile struct timeval `time'
global since we have switched to MI timercounter(9) on all port.
XXX1: some of these RTC drivers still assume 32bit time_t
XXX2: some of these should be rewritten to use todr_[gs]ettime_ymdhms()
XXX3: todr(9) man page doesn't mention todr_[gs]ettime_ymdhms()
|
|
|
|
|
|
|
|
in private Email from njoly@
|
|
limits. Remove sysctl(9) interface to the limit registers since it's
no longer needed.
|
|
|
|
we don't need individual flag bits. Clean up extra bit definitions.
Bump kernel version - welcome to 5.99.13
|
|
fractional bits. Otherwise, a setting of 52C reports 832 during
boot, and that's way too hot for any memory!
|
|
|
|
|
|
|
|
(These optional sensors are specified by JEDEC Standard No. 21-C
Section 4-7 and implemented by multiple vendors. Tested on my
amd64 machine with Kingston KVR1066D3E7S/2G memory which includes
a STMicro STTS424E02 sensor.)
|
|
monstrous if-then-else-if constructs.
2. Display module capacity in GB if it is at least 1GB.
3. Indicate if a memory module is "registered".
4. For DDR3, indicate if a temp-sensor is present.
Inspired by similar changes in OpenBSD's spdmem(4).
|
|
can be called _before_ we've identified the chip. Ensure that sc_chip
is initialized to NULL before chip is identified, and if it is NULL or
ADM1027, use the less-efficient send_byte/receive_byte.
While here, don't attempt to release the i2c bus if we failed to acquire
it. This would cause a panic on a LOCKDEBUG kernel.
Thanks to Nicholas Joly for pointing out both of these bugs.
|
|
case we use send_byte followed by receive_byte.
|
|
functional change intended.
While here, change some indentation to use tabs vs spaces.
|
|
addresses, rather than trying to read a byte of data from the device.
Some devices don't like to be read from (certain clock devices are, I'm
told, write-only!), while others expect to be asked only for words (or
pairs of bytes).
While here, skip a bunch of i2c addresses that can't (or at the very
least, shouldn't) have any slave devices.
This is the only use in NetBSD of the quick_read/quick_write protocol,
and it remains disabled by default. I've updated all the generic i2c
drivers to handle the quick_* protocols, but several port-specific
drivers have not been updated since I'm in no position to verify that
the changes work. Assistance from sandpoint, arm/xscale, evbarm/gumstix,
mips/alchemy, and macppc would be greatly appreciated.
|
|
routine, since we have already have the iic_smbus_* interfaces.
NOTE: i2c controllers that provide their own i2c_exec() routine also need
to be modified. I'll be committing most of these shortly.
|
|
physical packaging).
|
|
0.5 degC-precision the most-significant 9 bits of a 16-bit register.
Interpret them as such and simplify the conversion.
|
|
XXX This watchdog should eventually be integrated into the generic
watchdog framework.
|
|
at predefined addresses 0x2c, 0x2d, or 0x2e.
|
|
|
|
Verified on my single DDR3 machine to still produce correct data.
|
|
sysmon_envsys_destroy() twice
|
|
incremented by 1.
|
|
|
|
|
|
|
|
Tested by Martin Husemann
|
|
that we can use different routines for macppc's ki2c attachment. Fixes
problems reported by Robert Fritzsche on current-users@ list.
|
|
with embedded '.' so change the names to be better-conforming. Reported
by njoly
|
|
|