<?xml version="1.0"?>
<?xml-stylesheet type="text/css" href="http://elinux.org/skins/common/feed.css?303"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
		<id>http://elinux.org/index.php?title=CELF_Project_Proposal/Create_a_watchdog_framework_for_the_Linux_kernel&amp;feed=atom&amp;action=history</id>
		<title>CELF Project Proposal/Create a watchdog framework for the Linux kernel - Revision history</title>
		<link rel="self" type="application/atom+xml" href="http://elinux.org/index.php?title=CELF_Project_Proposal/Create_a_watchdog_framework_for_the_Linux_kernel&amp;feed=atom&amp;action=history"/>
		<link rel="alternate" type="text/html" href="http://elinux.org/index.php?title=CELF_Project_Proposal/Create_a_watchdog_framework_for_the_Linux_kernel&amp;action=history"/>
		<updated>2013-06-20T03:24:59Z</updated>
		<subtitle>Revision history for this page on the wiki</subtitle>
		<generator>MediaWiki 1.22alpha</generator>

	<entry>
		<id>http://elinux.org/index.php?title=CELF_Project_Proposal/Create_a_watchdog_framework_for_the_Linux_kernel&amp;diff=15812&amp;oldid=prev</id>
		<title>Tim Bird: add project</title>
		<link rel="alternate" type="text/html" href="http://elinux.org/index.php?title=CELF_Project_Proposal/Create_a_watchdog_framework_for_the_Linux_kernel&amp;diff=15812&amp;oldid=prev"/>
				<updated>2009-12-17T23:08:43Z</updated>
		
		<summary type="html">&lt;p&gt;add project&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;; Summary : Create a watchdog framework for the Linux kernel&lt;br /&gt;
&lt;br /&gt;
; Proposer : Wolfram Sang&lt;br /&gt;
&lt;br /&gt;
== Description ==&lt;br /&gt;
The watchdog API of the Linux kernel is documented and used for&lt;br /&gt;
years. Yet, there is no abstraction for its common functionality (open, write,&lt;br /&gt;
ioctl, close), so every watchdog driver has to implement those methods on its&lt;br /&gt;
own. In addition to the vast amount of code duplication in the kernel source,&lt;br /&gt;
this is also error-prone as there are subtle corner-cases in handling the&lt;br /&gt;
watchdog and the userspace-input correctly. Although there is code review for&lt;br /&gt;
new drivers, it seems very desirable to improve the situation as a whole.&lt;br /&gt;
&lt;br /&gt;
There have been two approaches for a generic watchdog framework, one from Alan&lt;br /&gt;
Cox and one from Wim van Sebroeck, the current watchdog maintainer. Sadly,&lt;br /&gt;
nothing from those have made it to mainline so far. This is a bit surprising;&lt;br /&gt;
although watchdogs are usually rather simple devices, they are crucial for the&lt;br /&gt;
stability concept of an enormous number of devices. The benefit of this&lt;br /&gt;
proposal is to have a rock-solid, well maintainable and trustworthy watchdog&lt;br /&gt;
framework, which makes writing new drivers faster and less error-prone.&lt;br /&gt;
&lt;br /&gt;
== Related work ==&lt;br /&gt;
* Proposal by Alan Cox:&lt;br /&gt;
** http://git.kernel.org/?p=linux/kernel/git/wim/linux-2.6-watchdog-next.git;a=shortlog;h=refs/heads/alan-generic-watchdog&lt;br /&gt;
* Proposal by Wim van Sebroeck:&lt;br /&gt;
** http://git.kernel.org/?p=linux/kernel/git/wim/linux-2.6-watchdog-next.git;a=shortlog;h=refs/heads/wim-generic-watchdog&lt;br /&gt;
&lt;br /&gt;
== Scope ==&lt;br /&gt;
My estimation would be 4 weeks of development and testing&lt;br /&gt;
&lt;br /&gt;
== Comments ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Project proposals]]&lt;/div&gt;</summary>
		<author><name>Tim Bird</name></author>	</entry>

	</feed>