Constify struct cfattach.

ok miod@

hppa: gsckbc(4), power(4): tsleep(9) -> tsleep_nsec(9); ok kn@ visa@

One missing boot -> prsignal(initprocess) conversion

reboot(9): Shutdown system by signaling init(8) from kernel where appropriate

Some ports watch temperature in MD and try to shutdown system, when overheated,
by calling directly (re)boot(9). Change this to signal init(8) from kernel,
as acpi(4) and acpitz(4) do, which has been more tested. This also helps to
clarify design that ``clean shutdown must be always started by init(8)''.

Note that SIGUSR2 causes init(8) to call reboot(2) with RB_POWERDOWN, as
acpi(4) etc. already does. It is reasonable, pointed out by kettenis@,
considering system is overheated and immediate reboot may be dangerous.

OK deraadt@ miod@

boot(9), reboot(9): Migrate MD callers of boot(9) to reboot(9)

I have found that some ports call boot(9) from machine-dependent code to
reboot system. These should be changed to either:

- Sending signal to init(8) to trigger it to shutdown system cleanly, like
acpi(4) does, in cases where found problems don't prevent system from working
immediately, or

- Just doing panic(9) if the situation is severely broken.

For now, just rewrite boot() to reboot(). Actual fixes follow.

Discussed with & OK from kettenis@

It's been a quarter century: we can assume volatile is present with that name.

ok dlg@ mpi@ deraadt@

better name for power thread (for power users only)

branches: 1.4.2;
Pass -Wformat, fix a few uninitialized variables as well.

devise the power reg address as hpa for the power device and thus avoid manual offset printing. add some code for interrupt-driven power-fail

support systems where power service is available from pdc and implement a cold hook as well thus do not powerleash lasi should we have cold_hook already set

handle power button (on 712 for now)

hppa: gsckbc(4), power(4): tsleep(9) -> tsleep_nsec(9); ok kn@ visa@

One missing boot -> prsignal(initprocess) conversion

reboot(9): Shutdown system by signaling init(8) from kernel where appropriate

Some ports watch temperature in MD and try to shutdown system, when overheated,
by calling directly (re)boot(9). Change this to signal init(8) from kernel,
as acpi(4) and acpitz(4) do, which has been more tested. This also helps to
clarify design that ``clean shutdown must be always started by init(8)''.

Note that SIGUSR2 causes init(8) to call reboot(2) with RB_POWERDOWN, as
acpi(4) etc. already does. It is reasonable, pointed out by kettenis@,
considering system is overheated and immediate reboot may be dangerous.

OK deraadt@ miod@

boot(9), reboot(9): Migrate MD callers of boot(9) to reboot(9)

I have found that some ports call boot(9) from machine-dependent code to
reboot system. These should be changed to either:

- Sending signal to init(8) to trigger it to shutdown system cleanly, like
acpi(4) does, in cases where found problems don't prevent system from working
immediately, or

- Just doing panic(9) if the situation is severely broken.

For now, just rewrite boot() to reboot(). Actual fixes follow.

Discussed with & OK from kettenis@

It's been a quarter century: we can assume volatile is present with that name.

ok dlg@ mpi@ deraadt@

better name for power thread (for power users only)

branches: 1.4.2;
Pass -Wformat, fix a few uninitialized variables as well.

devise the power reg address as hpa for the power device and thus avoid manual offset printing. add some code for interrupt-driven power-fail

support systems where power service is available from pdc and implement a cold hook as well thus do not powerleash lasi should we have cold_hook already set

handle power button (on 712 for now)

One missing boot -> prsignal(initprocess) conversion

reboot(9): Shutdown system by signaling init(8) from kernel where appropriate

Some ports watch temperature in MD and try to shutdown system, when overheated,
by calling directly (re)boot(9). Change this to signal init(8) from kernel,
as acpi(4) and acpitz(4) do, which has been more tested. This also helps to
clarify design that ``clean shutdown must be always started by init(8)''.

Note that SIGUSR2 causes init(8) to call reboot(2) with RB_POWERDOWN, as
acpi(4) etc. already does. It is reasonable, pointed out by kettenis@,
considering system is overheated and immediate reboot may be dangerous.

OK deraadt@ miod@

boot(9), reboot(9): Migrate MD callers of boot(9) to reboot(9)

I have found that some ports call boot(9) from machine-dependent code to
reboot system. These should be changed to either:

- Sending signal to init(8) to trigger it to shutdown system cleanly, like
acpi(4) does, in cases where found problems don't prevent system from working
immediately, or

- Just doing panic(9) if the situation is severely broken.

For now, just rewrite boot() to reboot(). Actual fixes follow.

Discussed with & OK from kettenis@

It's been a quarter century: we can assume volatile is present with that name.

ok dlg@ mpi@ deraadt@

better name for power thread (for power users only)

branches: 1.4.2;
Pass -Wformat, fix a few uninitialized variables as well.

devise the power reg address as hpa for the power device and thus avoid manual offset printing. add some code for interrupt-driven power-fail

support systems where power service is available from pdc and implement a cold hook as well thus do not powerleash lasi should we have cold_hook already set

handle power button (on 712 for now)