From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Problems with udelay() on AT91RM9200 !
Date: Mon, 22 Nov 2004 19:57:00 +0100 [thread overview]
Message-ID: <20041122185705.3C347C1430@atlas.denx.de> (raw)
In-Reply-To: Your message of "Mon, 22 Nov 2004 19:05:59 +0100." <41A22A87.3050609@imc-berlin.de>
In message <41A22A87.3050609@imc-berlin.de> you wrote:
>
> Why didn't I think of this! ;-)
Dunno.
> But seriously what's the point in letting the timer run with 40 or 80 MHz?
> In my case udelay won't work for delays > 107ms anyway.... :-(
Then make it run slower if you like.
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
A memorandum is written not to inform the reader, but to protect the
writer. -- Dean Acheson
next prev parent reply other threads:[~2004-11-22 18:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20041122165543.AE556C1430@atlas.denx.de>
2004-11-22 18:05 ` [U-Boot-Users] Problems with udelay() on AT91RM9200 ! Steven Scholz
2004-11-22 18:57 ` Wolfgang Denk [this message]
2004-11-22 14:13 Steven Scholz
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=20041122185705.3C347C1430@atlas.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox