Use the watchdog(4) framework for watchdog services instead of rolling more or less the same code.  This means that all our watchdog drivers use the framework, and that they all can be configured using sysctl kern.watchdog.{period,auto}, and they can all use watchdogd.
Use the watchdog(4) framework for watchdog services instead of rolling
more or less the same code.  This means that all our watchdog drivers
use the framework, and that they all can be configured using sysctl
kern.watchdog.{period,auto}, and they can all use watchdogd.

At least for now we still support the /dev/wdt0 char device and
userland poking using ioctl.

Testing by < jg ! rilk , com >, many thanks!

ok deraadt

orumin/openbsd-efivars,orumin/openbsd-efivars,orumin/openbsd-efivars,orumin/openbsd-efivars