From: Matt Porter <mporter@kernel.crashing.org>
To: Eugene Surovegin <ebs@ebshome.net>
Cc: Wolfgang Denk <wd@denx.de>, Paul Mackerras <paulus@samba.org>,
linuxppc-dev@lists.linuxppc.org
Subject: Re: set_rtc_time() cleanup / normalization
Date: Tue, 13 May 2003 20:47:43 -0700 [thread overview]
Message-ID: <20030513204743.A31841@home.com> (raw)
In-Reply-To: <5.1.0.14.2.20030513171616.037f6800@mail.ebshome.net>; from ebs@ebshome.net on Tue, May 13, 2003 at 05:30:13PM -0700
On Tue, May 13, 2003 at 05:30:13PM -0700, Eugene Surovegin wrote:
> >The main reason to remove it is thatit's broken (i. e. causes kernel
> >crashes) on many hardware configurations.
>
> Well, properly implemented set_rtc_time will not cause kernel crashes.
> I doesn't crash on our hardware. Guess why?
Well, I didn't want to "me too" as an opponent of doing this in the
kernel but I guess I need to. This type of thing doesn't *need* to
be in the kernel because it can be implemented in userspace.
<snip>
> >and you just removed the only argument to put
> >it into the timer interrupt at all.
>
> Well, I don't see such placement as an optimization, just as some place
> from where it can be done easily without requiring cron, hwclock or other
> usermode stuff.
If cron and hwclock are too heavyweight for your fs then this is
screaming for a simple busybox solution. I haven't looked at
busybox in a while, most of it might even be there already in a
slimmed down form factor.
Regards,
--
Matt Porter
mporter@kernel.crashing.org
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-05-14 3:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-12 21:17 set_rtc_time() cleanup / normalization Wolfgang Denk
2003-05-13 0:16 ` Dan Malek
2003-05-13 7:52 ` Geert Uytterhoeven
2003-05-13 8:18 ` Gabriel Paubert
[not found] ` <Pine.GSO.4.21.0305131051420.20323-100000@vervain.sonytel.be>
2003-05-13 10:21 ` Gabriel Paubert
2003-05-13 13:35 ` Wolfgang Denk
2003-05-13 12:03 ` Richard Zidlicky
2003-05-13 23:05 ` Paul Mackerras
2003-05-13 23:33 ` Eugene Surovegin
2003-05-14 0:08 ` Wolfgang Denk
[not found] ` <5.1.0.14.2.20030513171616.037f6800@mail.ebshome.net>
2003-05-14 3:47 ` Matt Porter [this message]
[not found] ` <5.1.0.14.2.20030513214040.02a6e6d0@mail.ebshome.net>
[not found] ` <3EC1DB1F.8000408@embeddededge.com>
2003-05-14 6:41 ` Eugene Surovegin
2003-05-14 6:47 ` Wolfgang Denk
2003-05-14 8:32 ` Benjamin Herrenschmidt
2003-05-14 15:57 ` Gabriel Paubert
2003-05-14 16:41 ` Eugene Surovegin
2003-05-14 15:50 ` Gabriel Paubert
2003-05-14 15:43 ` Gabriel Paubert
2003-05-14 16:28 ` Dan Malek
2003-05-15 18:04 ` Gabriel Paubert
2003-05-15 18:21 ` Wolfgang Denk
[not found] ` <20030515184412.GA22327@iram.es>
2003-05-15 19:37 ` Benjamin Herrenschmidt
[not found] <20030514230638.GB1687@linux-m68k.org>
[not found] ` <Pine.GSO.4.21.0305151031410.13683-100000@vervain.sonytel.be>
2003-05-15 10:45 ` Gabriel Paubert
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=20030513204743.A31841@home.com \
--to=mporter@kernel.crashing.org \
--cc=ebs@ebshome.net \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paulus@samba.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).