From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] README: document the requirements for CONFIG_SYS_HZ
Date: Fri, 22 Mar 2013 22:12:03 +0100 [thread overview]
Message-ID: <20130322211203.BA4752014CE@gemini.denx.de> (raw)
In-Reply-To: <1363923692-12748-1-git-send-email-swarren@wwwdotorg.org>
Dear Stephen,
In message <1363923692-12748-1-git-send-email-swarren@wwwdotorg.org> you wrote:
> CONFIG_SYS_HZ must be 1000, and get_timer() must therefore return mS.
> Document this.
"must return mS" ? "mS" means Milli-Siemens, which is a unit of
electric conductance and electric admittance. You mean "ms" =
milliseconds ...
> +- CPU timer options:
> + CONFIG_SYS_HZ
> +
> + The frequency of the timer returned by get_timer(). This value
> + MUST be 1000.
This is misleading, or even incorrect. If I read this, I would expect
that get_timer() returns 1000. Obviously, this is incorrect. Instead,
get_timer() returns timestamp information in millisecond resolution.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Crash programs fail because they are based on the theory that, with
nine women pregnant, you can get a baby a month. - Wernher von Braun
next prev parent reply other threads:[~2013-03-22 21:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-22 3:41 [U-Boot] [PATCH] README: document the requirements for CONFIG_SYS_HZ Stephen Warren
2013-03-22 21:12 ` Wolfgang Denk [this message]
2013-03-22 21:18 ` Stephen Warren
2013-03-22 21:41 ` Wolfgang Denk
2013-03-27 20:01 ` Tom Rini
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=20130322211203.BA4752014CE@gemini.denx.de \
--to=wd@denx.de \
--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 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.