[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALAqxLVVGM2nON71BbhuD-7eXnqbKGomfL63COaT7nePuQQ=zg@mail.gmail.com>
Date: Mon, 28 Apr 2014 11:16:37 -0700
From: John Stultz <john.stultz@...aro.org>
To: Randy Dunlap <rdunlap@...radead.org>
Cc: 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>,
Alessandro Zummo <a.zummo@...ertech.it>,
Prarit Bhargava <prarit@...hat.com>
Subject: Re: X86: Impossible select Enhanced Real Time Clock Support (legacy
PC RTC driver)
On Mon, Apr 21, 2014 at 10:58 AM, Randy Dunlap <rdunlap@...radead.org> wrote:
> [adding more patch committers]
>
> On 04/13/2014 12:05 PM, Stefani Seibold wrote:
>> Since some kernel version it is impossible to select the Enhanced Real
>> Time Clock Support (legacy PC RTC driver) because RTC_LIB is set by
>> default in arch/x86/Kconfig, but the rule for selecting CONFIG_RTC is
>> RTC_LIB=n. So the code of driver/char/rtc is still useless.
>>
>> 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?
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?
thanks
-john
--
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