On Mon, 2014-04-28 at 20:20 +0200, Alessandro Zummo wrote: > On Mon, 28 Apr 2014 11:16:37 -0700 > John Stultz <john.stu...@linaro.org> wrote: > > > >> This breaks the API since there is no more misc device /dev/rtc > > >> available without a udev rule or a link to /dev/rtc0. > > > > So yea.. I feel like that /dev/rtcN renaming (and API) break (which > > was a huge and annoying pain) was back in the 2.6.18-ish era? > > It's very old and linking/renaming is around since then. > > > But it sounds like the driver/char/rtc bit is dead code, and needs a > > cleanup? Or is there some use of that code that you need that the > > generic RTC layer doesn't have? >
The driver/char/rtc is not working code and should be a wrapper to the first rtc device. > as far as I know, no recent distribution is using the old code > anymore and the new (well, not so new anymore) framework provides the same > functionality. > Embedded distribution use it and depending on the /dev/rtc device. So what is missing is the /dev/rtc misc device 10,135. - Stefani -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
