From: Pete Popov <ppopov@mvista.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: Linux MIPS mailing list <linux-mips@linux-mips.org>
Subject: Re: udelay
Date: 04 Aug 2003 10:29:20 -0700 [thread overview]
Message-ID: <1060018159.9217.93.camel@zeus.mvista.com> (raw)
In-Reply-To: <20030804014132.GA4419@linux-mips.org>
On Sun, 2003-08-03 at 18:41, Ralf Baechle wrote:
> On Fri, Aug 01, 2003 at 06:49:08PM -0700, Pete Popov wrote:
>
> > Looks like the latest udelay in 2.4 is borked. Anyway else notice that
> > problem? I did a 10 sec test: mdelay works, udelay is broken, at least
> > for the CPU and toolchain I'm using.
>
> That just doesn't make sense. Mdelay is based on udelay so if udelay
> is broken mdelay should be broken, too.
I think the problem may be occurring when udelay is used with very large
values, like 10000. I've told the developer that that's not recommended
and to use mdelays in that case.
Pete
next prev parent reply other threads:[~2003-08-04 17:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-02 1:49 udelay Pete Popov
2003-08-02 2:42 ` udelay Kumba
2003-08-02 12:01 ` udelay Geert Uytterhoeven
2003-08-02 20:41 ` udelay Kumba
2003-08-04 1:41 ` udelay Ralf Baechle
2003-08-04 17:29 ` Pete Popov [this message]
2003-08-04 21:38 ` udelay Ralf Baechle
2003-08-04 22:04 ` udelay Pete Popov
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=1060018159.9217.93.camel@zeus.mvista.com \
--to=ppopov@mvista.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
/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