[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140428202034.782de089@linux.lan.towertech.it>
Date: Mon, 28 Apr 2014 20:20:34 +0200
From: Alessandro Zummo <a.zummo@...ertech.it>
To: John Stultz <john.stultz@...aro.org>
Cc: Randy Dunlap <rdunlap@...radead.org>,
Stefani Seibold <stefani@...bold.net>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Greg KH <greg@...ah.com>,
"rtc-linux@...glegroups.com" <rtc-linux@...glegroups.com>,
Prarit Bhargava <prarit@...hat.com>
Subject: Re: X86: Impossible select Enhanced Real Time Clock Support (legacy
PC RTC driver)
On Mon, 28 Apr 2014 11:16:37 -0700
John Stultz <john.stultz@...aro.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?
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.
--
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