Hi Guenter,
> > This allows setting a default value for the watchdog.open_timeout
> > commandline parameter via Kconfig.
> >
> > Some BSPs allow remote updating of the kernel image and root file
> > system, but updating the bootloader requires physical access. Hence, if
> > one has a firmware
Hi Guenter,
> Hi Wim,
>
> On Sun, Mar 06, 2016 at 11:49:56AM +0100, Wim Van Sebroeck wrote:
> > Hi Guenter,
> >
> > > The watchdog infrastructure is currently purely passive, meaning
> > > it only passes information from user space to drivers and vice ver
Hi Guenter,
> The watchdog infrastructure is currently purely passive, meaning
> it only passes information from user space to drivers and vice versa.
>
> Since watchdog hardware tends to have its own quirks, this can result
> in quite complex watchdog drivers. A number of scanarios are
Hi Guenter,
Code is OK, but I still have one last remark:
When I coded the generic watchdog framework, I used the following terminology:
* timeout for userspace timeout's
* heartbeat for the internal hardware timeout.
I would like us to stick to this, so that the story keeps being clear and
