[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20060930013612.92e12313.akpm@osdl.org>
Date: Sat, 30 Sep 2006 01:36:12 -0700
From: Andrew Morton <akpm@...l.org>
To: Thomas Gleixner <tglx@...utronix.de>
Cc: LKML <linux-kernel@...r.kernel.org>, Ingo Molnar <mingo@...e.hu>,
Jim Gettys <jg@...top.org>, John Stultz <johnstul@...ibm.com>,
David Woodhouse <dwmw2@...radead.org>,
Arjan van de Ven <arjan@...radead.org>,
Dave Jones <davej@...hat.com>
Subject: Re: [patch 03/23] GTOD: persistent clock support, i386
On Fri, 29 Sep 2006 23:58:22 -0000
Thomas Gleixner <tglx@...utronix.de> wrote:
> persistent clock support: do proper timekeeping across suspend/resume,
> i386 arch support.
>
This description implies that the patch implements something for i386
> arch/i386/kernel/apm.c | 44 ---------------------------------------
> arch/i386/kernel/time.c | 54 +---------------------------------------------
but all it does is delete stuff.
I _assume_ that it switches i386 over to using the (undescribed) generic
core, and it does that merely by implementing read_persistent_clock().
But I'd have expected to see some Kconfig change in there as well?
Does this implementation support all forms of persistent clock which are
known to exist on i386 platforms?
If/when you issue new changelogs, please describe what has to be done to
port other architectures over to use this overall framework.
Do ports for other architectures exist?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists