From: Scott McNutt <smcnutt@psyent.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] core ticks/timer code
Date: Tue, 31 Mar 2009 07:41:03 -0400 [thread overview]
Message-ID: <49D2014F.4070802@psyent.com> (raw)
In-Reply-To: <200903302110.06020.vapier@gentoo.org>
> so if we were to document things, it should read like this:
> - CONFIG_SYS_HZ is required to be 1000
Can't this just be eliminated? It's stupid to have a configurable
option that is neither ;-)
And it doesn't do much for my confidence when things stop working
(like my tftp downloads now that the tftp timeout has been, ahem,
"fixed") only because a "configurable" option wasn't set to the
"correct" value.
If we can't change it with breaking something, then let's stop
kidding ourselves and get rid of it.
--Scott
next prev parent reply other threads:[~2009-03-31 11:41 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-28 1:30 [U-Boot] core ticks/timer code Mike Frysinger
2009-03-28 7:07 ` Dirk Behme
2009-03-31 1:10 ` Mike Frysinger
2009-03-31 11:41 ` Scott McNutt [this message]
2009-03-31 15:48 ` Wolfgang Denk
2009-03-31 21:25 ` Scott Wood
2009-03-31 21:27 ` Wolfgang Denk
2009-04-02 12:38 ` Detlev Zundel
2009-04-02 13:09 ` Scott McNutt
2009-03-31 20:46 ` Wolfgang Denk
2009-03-31 8:17 ` Jean-Christophe PLAGNIOL-VILLARD
2009-03-31 9:13 ` Mike Frysinger
2009-03-31 10:28 ` Wolfgang Denk
2009-03-31 11:25 ` Mike Frysinger
2009-03-31 11:41 ` Jean-Christophe PLAGNIOL-VILLARD
2009-03-31 15:55 ` Dirk Behme
2009-04-02 19:16 ` Ladislav Michl
2009-04-02 21:18 ` Graeme Russ
2009-04-04 21:35 ` Wolfgang Denk
2009-03-31 15:46 ` Wolfgang Denk
2009-03-31 11:39 ` Jean-Christophe PLAGNIOL-VILLARD
2009-03-31 15:49 ` Wolfgang Denk
2009-03-31 21:32 ` Scott Wood
2009-04-04 21:14 ` Wolfgang Denk
2009-04-06 19:12 ` Scott Wood
2009-04-06 19:43 ` Wolfgang Denk
2009-03-31 20:43 ` 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=49D2014F.4070802@psyent.com \
--to=smcnutt@psyent.com \
--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