linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "John Zhou" <zjzhou@newrocktech.com>
To: "'Wolfgang Denk'" <wd@denx.de>
Cc: "'Mailing List: linuxppc-dev'" <linuxppc-dev@lists.linuxppc.org>,
	<rodmur@maybe.org>
Subject: RE: A question on kernel clock:
Date: Wed, 31 Dec 2003 10:44:46 +0800	[thread overview]
Message-ID: <000001c3cf48$0e4b80d0$b702a8c0@newrock2> (raw)
In-Reply-To: <20031230184951.94F07C12DD@atlas.denx.de>


Thanks a lot!

I means nanosleep() function.

Best Regards,
John

> (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: owner-linuxppc-dev@lists.linuxppc.org
[mailto:owner-linuxppc-dev@lists.linuxppc.org]On Behalf Of Wolfgang Denk
Sent: Wednesday, December 31, 2003 2:50 AM
To: zjzhou@newrocktech.com
Cc: 'Mailing List: linuxppc-dev'
Subject: Re: A question on kernel clock:



Dear John,

in message <000501c3cec2$130dbab0$b702a8c0@newrock2> you wrote:
>
> The processor I mentioned is MPC82xx. Now, I have kernel from kernel.org

[I guessed that from the ...BRG8 part.]

> 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.

> (2) can udelay() be changed to be preempted by other process?

That makes little sense. If you allow to run other prcesses inbetween
you will have  looong  delays  -  udelay()  was  not  made  for  such
purposes,  but  for  very  short delays (as the name suggests: in the
range of a few microseconds).

> (3) which is good choice for Kernel timeslice?

What's wrong with the standard 10 ms ?

> Additional, could we develop a bootloader like vxworks' bootloader? (
> vxworks bootloader is a little vxworks, I think.)

Of course you can. But what for? If you like the VxWorks boot loader,
then use it. If you like something more powerful, use U-Boot.


Best regards,

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
This all sounds complicated, but it mostly does excatly what you  ex-
pect. It's just difficult for us to explain what you expect...
                       - L. Wall & R. L. Schwartz, _Programming Perl_


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  parent reply	other threads:[~2003-12-31  2:44 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
2003-12-31  2:44           ` John Zhou [this message]
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='000001c3cf48$0e4b80d0$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 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).