From: Matt Porter <porter@cox.net>
To: Scott Murray <scottm@somanetworks.com>
Cc: Patrick Mochel <mochel@osdl.org>,
Rusty Lynch <rusty@linux.co.intel.com>,
Dave Jones <davej@codemonkey.org.uk>,
wingel@nano-systems.com, lkml <linux-kernel@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH][RFC] Proposal for a new watchdog interface using sysfs
Date: Thu, 13 Feb 2003 15:58:17 -0700 [thread overview]
Message-ID: <20030213155817.B1738@home.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0302131603500.23407-100000@rancor.yyz.somanetworks.com>; from scottm@somanetworks.com on Thu, Feb 13, 2003 at 04:12:28PM -0500
On Thu, Feb 13, 2003 at 04:12:28PM -0500, Scott Murray wrote:
> On Thu, 13 Feb 2003, Patrick Mochel wrote:
> >
> [snip]
> > Create a watchdog timer class. That will contain all watchdog timers, no
> > matter what bus they are on.
> >
> > I apologize for leading you astray with suggesting you treat them as
> > system devices; I was under the assumption they were more important. :)
> > They should always be in the most accurate place in the tree. Don't worry
> > about what the user sees; consistency and accuracy are more important..
>
> I like this idea, since it means my init scripts wouldn't have to dig
> around looking for watchdog directories/files on various flavours of cPCI
> CPU cards. :)
Yes, and on embedded SoC devices we have watchdog facilities sitting
on an internal chip bus. It would be nice to find access points in
a uniform place on any Linux system. i.e. PCI watchdog on my x86 desktop
is in the same place as the on-chip watchdog on my PPC44x system.
IMHO, anything else would be a logical step backwards from accessing
/dev/watchdog across platforms.
Regards,
--
Matt Porter
porter@cox.net
This is Linux Country. On a quiet night, you can hear Windows reboot.
next prev parent reply other threads:[~2003-02-13 22:48 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-13 3:16 [PATCH][RFC] Proposal for a new watchdog interface using sysfs Rusty Lynch
2003-02-13 4:27 ` Daniel Pittman
2003-02-13 7:32 ` Rusty Lynch
2003-02-13 11:55 ` Dave Jones
2003-02-13 15:34 ` Rusty Lynch
2003-02-13 16:04 ` Patrick Mochel
2003-02-13 15:51 ` Rusty Lynch
2003-02-13 19:07 ` Dave Jones
2003-02-13 18:31 ` Rusty Lynch
2003-02-13 19:19 ` Patrick Mochel
2003-02-13 21:12 ` Scott Murray
2003-02-13 22:58 ` Matt Porter [this message]
2003-02-13 22:05 ` Rusty Lynch
2003-02-14 0:47 ` Rusty Lynch
2003-02-14 14:48 ` Alan Cox
2003-02-14 15:32 ` Rusty Lynch
2003-02-14 17:55 ` Alan Cox
2003-02-14 19:02 ` Rusty Lynch
2003-02-14 20:43 ` Alan Cox
2003-02-14 21:12 ` Joel Becker
2003-02-14 13:48 ` Valdis.Kletnieks
2003-02-14 14:57 ` Alan Cox
2003-02-13 16:04 ` Dave Jones
2003-02-13 18:20 ` Rusty Lynch
2003-02-13 18:21 ` Rusty Lynch
2003-02-13 23:04 ` Pavel Machek
2003-02-14 22:12 ` Alan Cox
2003-02-14 21:35 ` Pavel Machek
2003-02-14 23:17 ` Rusty Lynch
2003-02-15 1:54 ` Alan Cox
2003-02-15 8:27 ` Cort Dougan
2003-02-15 9:13 ` John Bradford
2003-02-15 21:03 ` Alan Cox
2003-02-15 20:37 ` John Bradford
2003-02-15 12:42 ` Ingo Oeser
2003-02-15 17:26 ` Pavel Machek
2003-02-19 5:24 ` Rusty Lynch
2003-02-20 21:19 ` Jakob Oestergaard
2003-02-20 22:36 ` Alan Cox
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=20030213155817.B1738@home.com \
--to=porter@cox.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davej@codemonkey.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.org \
--cc=rusty@linux.co.intel.com \
--cc=scottm@somanetworks.com \
--cc=wingel@nano-systems.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox