From: "John Zhou" <zjzhou@newrocktech.com>
To: "'Mailing List: linuxppc-dev'" <linuxppc-dev@lists.linuxppc.org>
Subject: A question on kernel clock:
Date: Tue, 30 Dec 2003 14:34:36 +0800 [thread overview]
Message-ID: <000301c3ce9e$ff345440$b702a8c0@newrock2> (raw)
In-Reply-To: <1072237883.699.34.camel@gaston>
Dear All,
A question on kernel clock:
Normally, which is kernel clock source? Can we use any one of BRG1-8? Can we use bus clock? Which is good for choice?
Can anyone give me some suggestions?
Regards,
John
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-12-30 6:34 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 ` John Zhou [this message]
2003-12-30 10:22 ` A question on kernel clock: 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
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='000301c3ce9e$ff345440$b702a8c0@newrock2' \
--to=zjzhou@newrocktech.com \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).