From: Rusty Lynch <rusty@linux.co.intel.com>
To: wingel@nano-system.com, mochel@osdl.org
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Plans for non-iocl watchdog API?
Date: 07 Feb 2003 14:16:06 -0800 [thread overview]
Message-ID: <1044656167.1134.10.camel@vmhack> (raw)
I am getting ready to write a new watchdog timer for a couple of
different cpci single board computers, and was wondering if there are
plans to move to a sysfs based api. The current model (as documented in
Documentation/watchdog-api.txt) is based on the old way of doing things,
with ioctls for configuring and reading/writing to a char device for
refreshing the watchdog.
--rustyl
reply other threads:[~2003-02-07 22:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1044656167.1134.10.camel@vmhack \
--to=rusty@linux.co.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.org \
--cc=wingel@nano-system.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.