Watchdog API Update

Watchdog API Update

[Andrew Kilkenny]

Patched from 2.6.16

Included are patches for the Watchdog API. This API is already AD HOC 
according to the documentation, so the update is not expected to meet 
much opposition.

The patch/api update adds support for enabling watchdog monitoring 
directly via the kernel driver. It appears some drivers do this on their 
own, while others implement the api, dictating that userspace programs 
manage the watchdog. This includes adding both the ability for userspace 
to enable/disable the feature, and to compile in the feature to be 
enabled automatically at boot.

The Patch file includes diffs from watchdog.h, the watchdog.txt 
documentation, and a KConfig file.

I am unsure on the licensing information. The header file only mentions 
it was derived from Ken's original code. GPL information is absent, 
along with dates. In fact, I am unsure where the copyright belongs, if 
it defaults to Berkshire PC, if it must be GPL, and the like. Guidance 
will be greatly appreciated, especially if (absent a GPL declaration) I 
need permission to handle this code.

Re: Watchdog API Update

[Randy Dunlap]

On Fri, 01 Jun 2007 14:00:10 -0500 Andrew Kilkenny wrote:

> Patched from 2.6.16
> 
> Included are patches for the Watchdog API. This API is already AD HOC 
> according to the documentation, so the update is not expected to meet 
> much opposition.
> 
> The patch/api update adds support for enabling watchdog monitoring 
> directly via the kernel driver. It appears some drivers do this on their 
> own, while others implement the api, dictating that userspace programs 
> manage the watchdog. This includes adding both the ability for userspace 
> to enable/disable the feature, and to compile in the feature to be 
> enabled automatically at boot.
> 
> The Patch file includes diffs from watchdog.h, the watchdog.txt 
> documentation, and a KConfig file.

what patch file??

> I am unsure on the licensing information. The header file only mentions 
> it was derived from Ken's original code. GPL information is absent, 
> along with dates. In fact, I am unsure where the copyright belongs, if 
> it defaults to Berkshire PC, if it must be GPL, and the like. Guidance 
> will be greatly appreciated, especially if (absent a GPL declaration) I 
> need permission to handle this code.


---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***