This changeset push causes a flagday for the kernel,
/usr/kernel/drv/pm, and /usr/sbin/pmconfig.  All of these
components must be either from a pre-7491 changeset
or all from 7491 or later.

If using a Cap-I Install "tar" kernel, both /usr/sbin/pmconfig
and /usr/kernel/drv/pm must be copied onto the test machine
from the matching workspace proto area.  A bfu should
do the right thing.

pm will ASSERT if called with an unknown ioctls.
The old pm will ASSERT if the cpu_deep_idle keyword
is added to /etc/power.conf and the new pmconfig is run.
The old pmconfig will complain about the cpu_deep_idle
keyword.  The cpu_deep_idle keyword is not added to
/etc/power.conf by default (and it does not need to be for
proper function).

Regards,
Bill


On 10/22/08 18:31, Bill.Holler at Sun.COM wrote:
> Author: Bill Holler <Bill.Holler at Sun.COM>
> Repository: /hg/tesla/pad-gate
> Latest revision: 45891d77c0b28b98b95e9b18f939c1a0c06471f2
> Total changesets: 1
> Log message:
> cpu_deep_idle keyword in power.conf
> suspend/resume support
> cpupm_enabled does not have CPUPM_C_STATES bit set
>
> Files:
>       update: usr/src/cmd/power/handlers.c
>       update: usr/src/cmd/power/parse.c
>       update: usr/src/cmd/power/pmconfig.h
>       update: usr/src/uts/common/io/pm.c
>       update: usr/src/uts/common/sys/callb.h
>       update: usr/src/uts/common/sys/pm.h
>       update: usr/src/uts/i86pc/io/cpudrv/cpu_idle.c
>       update: usr/src/uts/i86pc/io/cpudrv/cpudrv_mach.c
>       update: usr/src/uts/i86pc/io/hpet_acpi.c
>       update: usr/src/uts/i86pc/os/cpupm.c
>       update: usr/src/uts/i86pc/os/mp_machdep.c
>       update: usr/src/uts/i86pc/os/mp_startup.c
>       update: usr/src/uts/i86pc/sys/cpu_idle.h
>       update: usr/src/uts/i86pc/sys/cpudrv_mach.h
>       update: usr/src/uts/i86pc/sys/hpet.h
>       update: usr/src/uts/i86pc/sys/hpet_acpi.h
>       update: usr/src/uts/i86pc/sys/machcpuvar.h
> _______________________________________________
> tesla-dev mailing list
> tesla-dev at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/tesla-dev
>   



Reply via email to