From: Martin Costabel <costabel@wanadoo.fr>
To: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Upgraded utils...
Date: Sat, 15 Jul 2000 17:20:37 +0200 [thread overview]
Message-ID: <39708145.63271470@wanadoo.fr> (raw)
In-Reply-To: 4.3.2.7.2.20000714210226.039b37f0@mail.munich.netsurf.de
Franz Sirl wrote:
>
> At 20:54 14.07.00, Martin Costabel wrote:
> >Could be /sbin/hwclock is now a binary that was compiled with
> >util-linux. This doesn't mean it works, though. Better put the old fake
> >hwclock shell script there ("/sbin/clock -s"). Or is one now supposed to
> >create /dev/rtc and use it as on any other architecture?
>
> Yes! That's why I did CONFIG_PPC_RTC, it's such simple code, but it helps a
> lot to bring us in line with the other architectures.
For the record: Yes, it works. (On a Pmac 6400, with a 2.2.17pre11
kernel from bitkeeper; 2.4.0-test4 still doesn't want to boot, so I
can't test it).
I was too timid and had compiled PPC_RTC only as a module. Apparently
the kernel does not load this module automatically, but when I put a
line
/sbin/modprobe rtc
just before the hwclock stuff in /etc/rc.sysinit, it works (yes
/etc/rc.sysinit; this is initscripts-5.27 which has /etc/rc.d as symlink
to /etc, so that all the rc* stuff now clutters /etc. Big progress...)
/sbin/hwclock comes from util-linux-2.10k, compiled without problems
from the RedHat SRPM.
Thanks
--
Martin
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-07-15 15:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-14 17:30 Upgraded utils Iain Sandoe
2000-07-14 18:54 ` Martin Costabel
2000-07-14 19:06 ` Franz Sirl
2000-07-14 19:16 ` Martin Costabel
2000-07-15 15:20 ` Martin Costabel [this message]
2000-07-16 11:45 ` RTC on 2.4.0-test4 (Was Re: Upgraded utils...) Martin Costabel
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=39708145.63271470@wanadoo.fr \
--to=costabel@wanadoo.fr \
--cc=Franz.Sirl-kernel@lauterbach.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 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.