mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alessandro Zummo <alessandro.zummo@towertech.it>
To: David Woodhouse <dwmw2@infradead.org>
Cc: rtc-linux@googlegroups.com, paulus@samba.org,
	linux-kernel@vger.kernel.org
Subject: Re: [rtc-linux] Re: [PATCH] RTC class driver for ppc_md RTC functions
Date: Wed, 30 Apr 2008 22:29:14 +0200	[thread overview]
Message-ID: <20080430222914.4e1dd640@i1501.lan.towertech.it> (raw)
In-Reply-To: <1209576873.25560.398.camel@pmac.infradead.org>

On Wed, 30 Apr 2008 18:34:33 +0100
David Woodhouse <dwmw2@infradead.org> wrote:

> > 
> >  If we are talking about milliseconds I think a suspect is not enough.
> 
> Let me rephrase: This is how we're doing it for _every_ machine/platform
> which supports update_persistent_clock(). It makes sense to let
> individual RTC-class drivers do it differently if they need to, but it's
> a damn good default behaviour until/unless someone actually shows that
> they need it to be different. :)

 I still do not think that it makes sense to keep an unreliable hw RTC in
 sync with the system clock.. 

 I remember somone wrote a kind of ntp subsytem for the kernel but can't
 remember who :(
 
> >  My opinion is that such NTP mode could be removed from the kernel/not
> >  implemented in rtc class without loosing anything.
> 
> Want to send a patch to lkml which removes update_persistent_clock() and
> see what people think of that? :)

 I'm not _that_ mad, unless the patch is signed by Linus :)

 Anyway I will gladly accept a patch that implements this ntp mode :)

-- 

 Best regards,

 Alessandro Zummo,
  Tower Technologies - Torino, Italy

  http://www.towertech.it


      reply	other threads:[~2008-04-30 20:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <18449.48370.434716.293552@cargo.ozlabs.ibm.com>
     [not found] ` <20080428102629.6e702137@i1501.lan.towertech.it>
     [not found]   ` <1209371478.25560.114.camel@pmac.infradead.org>
     [not found]     ` <20080428105245.5c9fff85@i1501.lan.towertech.it>
     [not found]       ` <1209378191.25560.121.camel@pmac.infradead.org>
     [not found]         ` <20080428124033.70e78dcf@i1501.lan.towertech.it>
     [not found]           ` <1209380882.25560.127.camel@pmac.infradead.org>
2008-04-30  9:39             ` Alessandro Zummo
2008-04-30 17:34               ` David Woodhouse
2008-04-30 20:29                 ` Alessandro Zummo [this message]

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=20080430222914.4e1dd640@i1501.lan.towertech.it \
    --to=alessandro.zummo@towertech.it \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulus@samba.org \
    --cc=rtc-linux@googlegroups.com \
    /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

Powered by JetHome