commit | f21d857fde838f7cb141f81c49070abbdf343fce | [log] [tgz] |
---|---|---|
author | Mike Frysinger <vapier@chromium.org> | Thu Dec 08 20:11:32 2016 |
committer | chrome-bot <chrome-bot@chromium.org> | Wed Mar 08 21:23:08 2017 |
tree | 947bdaa57a3e18a6e0b115cec4d24dc5c57cf6da | |
parent | 60338a8ef06d801b6d2e343dbb14697a16f85c1b [diff] |
README: convert to markdown for gitiles BUG=None TEST=looked at the output in gitiles Change-Id: I33b372bbdfacf8bf6378876f560187af75a344dc Reviewed-on: https://chromium-review.googlesource.com/428851 Commit-Ready: Mike Frysinger <vapier@chromium.org> Tested-by: Mike Frysinger <vapier@chromium.org> Reviewed-by: Ben Chan <benchan@chromium.org>
GPL Code is copied with explicit permission from Daniel Widyanto:
http://embeddedfreak.wordpress.com/2010/08/23/howto-use-linux-watchdog/
The project name is based on Samsung's “daisy” reference board design and I liked this quote from the daisy dog FAQ:
Daisy Dogs are not persnickety little ankle biters
When this daisydog doesn't run, the machine should reset. :)
An alternative code to start with would have been:
https://dev.openwrt.org/ticket/2270
The watchdog project is alot more complicated than what the Chromium OS project needs.