[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090224193708.5f8be86c@i1501.lan.towertech.it>
Date: Tue, 24 Feb 2009 19:37:08 +0100
From: Alessandro Zummo <alessandro.zummo@...ertech.it>
To: rtc-linux@...glegroups.com
Cc: Geert.Uytterhoeven@...ycom.com,
Richard Zidlicky <rz@...ux-m68k.org>,
linux-parisc@...r.kernel.org,
Linux Kernel Development <linux-kernel@...r.kernel.org>,
David@...abs.org, Kyle McMartin <kyle@...artin.ca>,
Linux/PPC Development <linuxppc-dev@...abs.org>,
Linux/m68k <linux-m68k@...ts.linux-m68k.org>,
Woodhouse <dwmw2@...radead.org>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>
Subject: Re: [rtc-linux] Re: [PATCH/RFC 0/5] Generic RTC class driver
On Tue, 24 Feb 2009 18:56:03 +0100 (CET)
Geert Uytterhoeven <Geert.Uytterhoeven@...ycom.com> wrote:
>
> On Mon, 23
> >
> > I'd start writing a working driver and then see how we should eventually
> > adapt the rtc subsystem to cope with your needs.
>
> OK, so here's a first example: rtc-ps3.
>
> Note that this single patch adds 100+ lines of code, while my previous patch
> series removed 500+ lines of code, while solving the autoloading problem for
> several ppc and m68k platforms.
This patch has a much cleaner approach, imho.
> Converting all (ca. 20?) ppc and m68k RTC support code into individual RTC
> class drivers would add ca. 100+ lines of code for each individual driver.
How different are all of those boards? It's simply a matter
of parameters and offsets? can we group them somehow?
--
Best regards,
Alessandro Zummo,
Tower Technologies - Torino, Italy
http://www.towertech.it
--
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