Date: Wed, 21 May 2003 15:49:28 -0700
From: Tom Rini <trini@kernel.crashing.org>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org, Russell King <rmk@arm.linux.org.uk>
Subject: Re: must-fix list, v5
Message-ID: <20030521224928.GA774@ip68-0-152-218.tc.ph.cox.net>
References: <20030521152255.4aa32fba.akpm@digeo.com> <20030521152334.4b04c5c9.akpm@digeo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030521152334.4b04c5c9.akpm@digeo.com>
User-Agent: Mutt/1.5.4i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1222
Lines: 31

On Wed, May 21, 2003 at 03:23:34PM -0700, Andrew Morton wrote:

> drivers/char/rtc/
> ~~~~~~~~~~~~~~~~~
> 
> o rmk: I think we need a generic RTC driver (which is backed by real RTCs).
>    Integrator-based stuff has a 32-bit 1Hz counter RTC with alarm, as has the
>   SA11xx, and probably PXA.  There's another implementation for the RiscPC
>   and ARM26 stuff.  I'd rather not see 4 implementations of the RTC userspace
>   API, but one common implementation so that stuff gets done in a consistent
>   way.
> 
>   We postponed this at the beginning of 2.4 until 2.5 happened.  We're now
>   at 2.5, and I'm about to add at least one more (the Integrator
>   implementation.) This isn't sane imo.

I talked with RMK on IRC a bit about this.  After reading
drivers/char/rtc.c, I think this can be vastly simplied to:
Add support for alarms to the existing generic rtc driver
(drivers/char/genrtc.c).

Does this sound like a plan?

-- 
Tom Rini
http://gate.crashing.org/~trini/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/