From: Dan Malek <dan@mvista.com>
To: Gabriel Paubert <paubert@iram.es>
Cc: Benjamin Herrenschmidt <bh40@calva.net>,
linuxppc-dev@lists.linuxppc.org, paulus@linuxcare.com.au
Subject: Re: 2.2.18pre17 again
Date: Tue, 31 Oct 2000 20:20:29 -0500 [thread overview]
Message-ID: <39FF6FDD.50DFBE38@mvista.com> (raw)
In-Reply-To: Pine.HPX.4.10.10010311722330.15431-100000@gra-ux1.iram.es
Gabriel Paubert wrote:
>
> On Tue, 31 Oct 2000, Benjamin Herrenschmidt wrote:
>
> > Because you didn't implement it yet ? :)
>
> Perhaps...
Make sure you look at the code in the "boot" directories. I think
all of them have udelay functions that use the timebase. At least,
it would be a starting point.
> Even with a 33 MHz timebase (keep dreaming), the maximal delay for non
> 601 CPUs is over 100 seconds.
I thought at one time we had mdelay/udelay that were smart enough
to loop and call the lower level delay to ensure this maximum
delay wasn't exceeded.....maybe I was smoking something :-).
-- Dan
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-11-01 1:20 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-26 6:30 2.2.18pre17 again Paul Mackerras
2000-10-26 14:19 ` Gabriel Paubert
2000-10-27 1:51 ` Paul Mackerras
2000-10-27 6:21 ` Martin Costabel
2000-10-27 11:59 ` Lombard Sleep Crash (Was: 2.2.18pre17 again) Albrecht Dre_
2000-10-27 14:39 ` Olaf Hering
2000-11-02 12:34 ` Albrecht Dreß
2000-11-02 15:07 ` Claus
2000-11-02 15:28 ` Albrecht Dre_
2000-11-02 18:09 ` Benjamin Herrenschmidt
2000-11-03 10:13 ` Albrecht Dre_
2000-11-03 12:22 ` Michael Schmitz
2000-11-03 12:32 ` Albrecht Dre_
2000-11-03 12:52 ` Michael Schmitz
2000-11-03 14:11 ` Albrecht Dre_
2000-11-03 14:52 ` Michael Schmitz
2000-11-03 21:51 ` Michael Schmitz
2000-11-02 15:35 ` Benjamin Herrenschmidt
2000-11-02 15:43 ` Michael Schmitz
2000-11-02 16:11 ` Benjamin Herrenschmidt
2000-11-02 17:13 ` Michael Schmitz
2000-11-03 15:22 ` Claus
2000-11-03 15:55 ` Benjamin Herrenschmidt
2000-11-03 21:53 ` Michael Schmitz
2000-11-09 1:22 ` Claus
2000-11-09 8:26 ` Michael Schmitz
2000-11-02 17:23 ` Joseph P. Garcia
2000-11-02 18:06 ` Benjamin Herrenschmidt
2000-11-02 22:18 ` Michael Schmitz
2000-11-02 22:56 ` Olaf Hering
2000-11-08 20:35 ` Michael Schmitz
2000-11-08 20:54 ` Benjamin Herrenschmidt
2000-11-08 21:48 ` Michael Schmitz
2000-10-27 19:02 ` 2.2.18pre17 again Olaf Hering
2000-10-28 0:14 ` Olaf Hering
2000-10-31 6:49 ` Michel Lanners
2000-10-31 11:53 ` Benjamin Herrenschmidt
2000-10-31 14:03 ` Gabriel Paubert
2000-10-31 14:48 ` Benjamin Herrenschmidt
2000-10-31 17:20 ` Gabriel Paubert
2000-11-01 1:20 ` Dan Malek [this message]
2000-11-01 7:33 ` Michel Lanners
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=39FF6FDD.50DFBE38@mvista.com \
--to=dan@mvista.com \
--cc=bh40@calva.net \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paubert@iram.es \
--cc=paulus@linuxcare.com.au \
/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;
as well as URLs for NNTP newsgroup(s).