From: Alessandro Zummo <a.zummo@towertech.it>
To: John Stultz <john.stultz@linaro.org>
Cc: Randy Dunlap <rdunlap@infradead.org>,
Stefani Seibold <stefani@seibold.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Greg KH <greg@kroah.com>,
"rtc-linux@googlegroups.com" <rtc-linux@googlegroups.com>,
Prarit Bhargava <prarit@redhat.com>
Subject: Re: X86: Impossible select Enhanced Real Time Clock Support (legacy PC RTC driver)
Date: Mon, 28 Apr 2014 20:20:34 +0200 [thread overview]
Message-ID: <20140428202034.782de089@linux.lan.towertech.it> (raw)
In-Reply-To: <CALAqxLVVGM2nON71BbhuD-7eXnqbKGomfL63COaT7nePuQQ=zg@mail.gmail.com>
On Mon, 28 Apr 2014 11:16:37 -0700
John Stultz <john.stultz@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?
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
next prev parent reply other threads:[~2014-04-28 21:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-13 19:05 X86: Impossible select Enhanced Real Time Clock Support (legacy PC RTC driver) Stefani Seibold
2014-04-21 17:58 ` Randy Dunlap
2014-04-28 18:16 ` John Stultz
2014-04-28 18:20 ` Alessandro Zummo [this message]
2014-05-02 20:03 ` Stefani Seibold
2014-05-05 23:34 ` Maciej W. Rozycki
2014-05-06 9:56 ` [rtc-linux] " Alessandro Zummo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140428202034.782de089@linux.lan.towertech.it \
--to=a.zummo@towertech.it \
--cc=greg@kroah.com \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=prarit@redhat.com \
--cc=rdunlap@infradead.org \
--cc=rtc-linux@googlegroups.com \
--cc=stefani@seibold.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox