From: Pantelis Antoniou <panto@intracom.gr>
To: David Ho <DavidHo@nanometrics.ca>
Cc: Dan Malek <dan@embeddededge.com>,
Linuxppc-Embedded <linuxppc-embedded@lists.linuxppc.org>,
Tom Rini <trini@kernel.crashing.org>
Subject: Re: RTC no longer exist on the 866/87x/88x
Date: Fri, 28 May 2004 15:45:05 +0300 [thread overview]
Message-ID: <40B73451.4080001@intracom.gr> (raw)
In-Reply-To: <OFA7FE93B3.1BAFEB05-ON85256EA2.0044EB60-85256EA2.00457969@nanometrics.ca>
David Ho wrote:
>
>
>
>Hi 8xx gurus,
>
>I just noticed the RTC is no longer documented/tested/supported on the
>duet. How does this impact the current 2.4 8xx tree?
>
>I know the /dev/rtc still uses RTC on the processor, it appears to work
>fine, but I wouldn't bet my life on it for production units.
>
I believe there's a problem with increased power consumption
by the RTC so that's why Motorola removed it from the docs.
>
>How about the kernel's timing service and scheduling, does it use the
>timebase register instead? Are these services effected at all?
>
>
Don't worry, they're not affected at all.
>Thanks a lot,
>
>David Ho
>Nanometrics Inc.
>
>
>
>
>
Regards
Pantelis
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-05-28 12:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-28 8:40 2.6-7-rc1 8xx - No go Pantelis Antoniou
2004-05-28 10:17 ` Pantelis Antoniou
2004-05-28 11:38 ` rdiz
2004-05-28 12:16 ` Robert P. J. Day
2004-05-28 12:59 ` Pantelis Antoniou
2004-05-28 12:24 ` Pantelis Antoniou
2004-05-28 12:38 ` RTC no longer exist on the 866/87x/88x David Ho
2004-05-28 12:45 ` Pantelis Antoniou [this message]
2004-05-28 13:29 ` Mark Chambers
2004-05-28 23:23 ` 2.6-7-rc1 8xx - No go Paul Mackerras
2004-05-28 23:43 ` Tom Rini
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=40B73451.4080001@intracom.gr \
--to=panto@intracom.gr \
--cc=DavidHo@nanometrics.ca \
--cc=dan@embeddededge.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=trini@kernel.crashing.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 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.