From: Corey Minyard <minyard@acm.org>
To: Rob Radez <rob@osinvestor.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Further WatchDog Updates
Date: Tue, 09 Apr 2002 08:25:27 -0500 [thread overview]
Message-ID: <3CB2EBC7.4010207@acm.org> (raw)
In-Reply-To: <Pine.LNX.4.33.0204090645240.17511-100000@pita.lan>
Rob Radez wrote:
>On Mon, 8 Apr 2002, Corey Minyard wrote:
>
>>Rob Radez wrote:
>>
>>>Ok, new version of watchdog updates is up at
>>>http://osinvestor.com/bigwatchdog-4.diff
>>>
>>Could the timeout be in milliseconds? A lot of watchdogs have lower
>>resolution, and I have written applications that require a lower
>>resolution than a second. Milliseconds is small enough to not cause
>>problems, but big enough to give a good range of time.
>>
>
>Not in 2.4, and I wonder if that might be too fine-grained for some
>drivers which have an upper limit of 255 seconds. I also wonder if it
>would be considered ugly to extend WDIOC_SETOPTIONS to have a
>WDIOS_TIMEINMILLI bit.
>
>Regards,
>Rob Radez
>
Why is that too fine grained? You would just set the values from 1000
to 255000 instead of 1 to 255, and round up.
I have a board that sets the time value in wierd times (like 225ms,
450ms, 900ms, 1800ms, 3600ms, etc.). I wouldn't be against the
WDIOS_TIMEINMILLI option, but milliseconds should be good enough for anyone.
-Corey
next prev parent reply other threads:[~2002-04-09 13:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-08 3:45 Further WatchDog Updates Rob Radez
2002-04-08 12:44 ` Justin Cormack
2002-04-08 13:15 ` Roy Sigurd Karlsbakk
2002-04-08 20:54 ` Rob Radez
2002-04-09 4:25 ` Corey Minyard
2002-04-09 10:49 ` Rob Radez
2002-04-09 11:47 ` Zwane Mwaikambo
2002-04-09 15:02 ` Rob Radez
2002-04-09 15:31 ` Zwane Mwaikambo
2002-04-09 13:25 ` Corey Minyard [this message]
2002-04-09 15:17 ` Rob Radez
2002-04-09 15:55 ` Corey Minyard
2002-04-09 23:01 ` Rob Radez
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=3CB2EBC7.4010207@acm.org \
--to=minyard@acm.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rob@osinvestor.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