On Fri, 20 Feb 2009 16:46:44 +0100
Geert Uytterhoeven <Geert.Uytterhoeven@xxxxxxxxxxx> wrote:
Fortunately there already exists a generic RTC class driver: "rtc-parisc".
Despite it's name, it's platform-independent, as it's build on top of the RTC
abstraction used by "genrtc".
This patch series
- adds a missing module alias to rtc-parisc,
- renames rtc-parisc to rtc-generic,
- converts the architectures that currently have CONFIG_GEN_RTC enabled in
their defconfig (m68k, parisc, powerpc) to rtc-generic,
- removes the obsolete rtc-ppc driver,
- removes the old genrtc driver.
Note that genrtc may be used on other archictectures as well: at least alpha
has the required infrastructure ([gs]et_rtc_time()). The Kconfig rules allow
genrtc to be enabled on several others (cris, h8300, mn10300, um, x86, xtensa).
Furthermore genrtc and rtc-generic are not 100% userspace compatible:
- /dev/rtc provided by genrtc uses a misc character device (10:135),
- /dev/rtc provided by rtc-generic uses a dynamic character device.
Hello,
my opinion on this kind of stuff is that I want to avoid the layering
of implementations under the rtc subsystem. I'd rather prefer that each
rtc device had its own driver.
I've made error in the past, by accepting such kind of drivers, and
would like to avoid that it happens again.
Regarding the user space, the assumption that a device has
a fixed major:minor number should be dropped as well.
--
Best regards,
Alessandro Zummo,
Tower Technologies - Torino, Italy
http://www.towertech.it
--
To unsubscribe from this list: send the line "unsubscribe linux-m68k" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
