From: "John Zhou" <zjzhou@newrocktech.com>
To: "'Wolfgang Denk'" <wd@denx.de>, "'Dale Harris'" <rodmur@maybe.org>
Cc: "'Mailing List: linuxppc-dev'" <linuxppc-dev@lists.linuxppc.org>
Subject: RE: A question on kernel clock:
Date: Wed, 31 Dec 2003 12:15:50 +0800 [thread overview]
Message-ID: <000201c3cf54$c70bd5f0$b702a8c0@newrock2> (raw)
In-Reply-To: <20031230214037.77A1CC12DD@atlas.denx.de>
Sorry! It should be usleep() used in user space!
Best Regards,
John
> run on the board. But, my "nsleep()" is not exactly. So, I want to
> realize the timer mechanism of Linux used.
> (1) which timer is used for nsleep?
I have not the slightest idea. I don't know of any standard funtion
with that name - neither in user space nor in kernel code.
-----Original Message-----
From: Wolfgang Denk
Sent: Wednesday, December 31, 2003 5:41 AM
Subject: Re: A question on kernel clock:
In message <20031230210713.GC5005@maybe.org> you wrote:
>
> > > (1) which timer is used for nsleep?
> >
> > I have not the slightest idea. I don't know of any standard funtion
> > with that name - neither in user space nor in kernel code.
>
> Perhaps he means nanosleep().
Perhaps. But then the definition of nanosleep() says that it will cause
a delay of "at least the time specified in *req", i. e. the upper bound
is not even specified. But the OP seemed to assume a strict timing, so
maybe it was yet another function.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-12-31 4:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-23 14:46 NULL-pointer dereference in ELF core dump, and proposed fix John Whitney
2003-12-24 3:51 ` Benjamin Herrenschmidt
2003-12-30 6:34 ` A question on kernel clock: John Zhou
2003-12-30 10:22 ` Wolfgang Denk
2003-12-30 10:45 ` John Zhou
2003-12-30 18:49 ` Wolfgang Denk
2003-12-30 21:07 ` Dale Harris
2003-12-30 21:40 ` Wolfgang Denk
2003-12-31 4:15 ` John Zhou [this message]
2003-12-31 2:44 ` John Zhou
2003-12-31 2:44 ` about small dhcp client/server and http client/server John Zhou
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='000201c3cf54$c70bd5f0$b702a8c0@newrock2' \
--to=zjzhou@newrocktech.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=rodmur@maybe.org \
--cc=wd@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.