From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] README: Clarify difference of CONFIG_WATCHDOG and CONFIG_HW_WATCHDOG
Date: Fri, 29 Apr 2011 20:17:45 -0400 [thread overview]
Message-ID: <201104292017.47119.vapier@gentoo.org> (raw)
In-Reply-To: <m2bozp71v3.fsf@ohwell.denx.de>
On Friday, April 29, 2011 07:06:56 Detlev Zundel wrote:
> > On Wed, Apr 27, 2011 at 11:25, Detlev Zundel wrote:
> >> Now that we have the documentation, the code should be changed to
> >> reflect it ;)
> >>
> >> Asd far as I can see, these are the places where HW_WATCHDOG is used
> >
> >> instead of WATCHDOG:
> > the trouble is that watchdog.h doesnt seem to match, nor does the
> > name. "hardware" means to me "hardware" as in "the cpu hardware".
>
> Yes, I understand that the situation is not 100% ideal, but I do not
> share your pessimism.
it isnt pessimism ... it's a fact that the documentation does not match the
source, nor is the source clear.
> > > the watchdog system is a legacy mess, so probably be easier to just
> > gut the whole thing.
>
> A agree that the naming is not ideal, but this isn't a good enough
> argument for removing it. Apart from that, this feature is used in many
> commercial systems...
i didnt mean remove it and not provide equivalent functionality. there should
be a single CONFIG_WATCHDOG and every different watchdog driver should have
its own CONFIG_WATCHDOG_FOO define.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20110429/f99694a0/attachment.pgp
next prev parent reply other threads:[~2011-04-30 0:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-27 15:25 [U-Boot] [PATCH] README: Clarify difference of CONFIG_WATCHDOG and CONFIG_HW_WATCHDOG Detlev Zundel
2011-04-27 16:27 ` Mike Frysinger
2011-04-29 11:06 ` Detlev Zundel
2011-04-30 0:17 ` Mike Frysinger [this message]
2011-05-12 21:26 ` Wolfgang Denk
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=201104292017.47119.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=u-boot@lists.denx.de \
/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