Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933125AbaD1V7M (ORCPT ); Mon, 28 Apr 2014 17:59:12 -0400 Received: from zabrina.hetzner-de.towertech.it ([178.63.16.19]:41109 "EHLO zabrina.hetzner-de.towertech.it" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932230AbaD1V7L (ORCPT ); Mon, 28 Apr 2014 17:59:11 -0400 Date: Mon, 28 Apr 2014 20:20:34 +0200 From: Alessandro Zummo To: John Stultz Cc: Randy Dunlap , Stefani Seibold , "linux-kernel@vger.kernel.org" , Greg KH , "rtc-linux@googlegroups.com" , Prarit Bhargava Subject: Re: X86: Impossible select Enhanced Real Time Clock Support (legacy PC RTC driver) Message-ID: <20140428202034.782de089@linux.lan.towertech.it> In-Reply-To: References: <1397415946.1555.16.camel@vger.seibold.net> <53555C56.1040900@infradead.org> Organization: Tower Technologies MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 28 Apr 2014 11:16:37 -0700 John Stultz 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/