Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 13 Jan 2003 18:05:13 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 13 Jan 2003 18:05:12 -0500 Received: from ip68-0-152-218.tc.ph.cox.net ([68.0.152.218]:18050 "EHLO opus.bloom.county") by vger.kernel.org with ESMTP id ; Mon, 13 Jan 2003 18:04:36 -0500 Date: Mon, 13 Jan 2003 16:13:25 -0700 From: Tom Rini To: Linus Torvalds Cc: Kernel Mailing List Subject: [PATCH][RESEND x 5] Don't ask about "Enhanced Real Time Clock Support" on some archs Message-ID: <20030113231325.GA764@opus.bloom.county> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org The following patch adds an explicit no list of arches who do not want to have the "Enhanced Real Time Clock Support" RTC driver asked. This adds PPC32 (who for a long time had their own 'generic' RTC driver, and then have adopted the genrtc driver) and PARISC (who have always used the genrtc driver). Per request of Peter Chubb, IA64 is on this list as well. The problem is that on some archs there is no hope of this driver working, and having it compiled into the kernel can cause many different problems. On the other hand, there are some arches for whom that driver does work, on some platforms. So having an explicit yes list would result in some rather ugly statements. -- Tom Rini (TR1265) http://gate.crashing.org/~trini/ ===== drivers/char/Kconfig 1.1 vs edited ===== --- 1.1/drivers/char/Kconfig Tue Oct 29 18:16:55 2002 +++ edited/drivers/char/Kconfig Wed Nov 13 07:56:39 2002 @@ -1053,6 +1053,7 @@ config RTC tristate "Enhanced Real Time Clock Support" + depends on !PPC32 && !PARISC && !IA64 ---help--- If you say Y here and create a character special file /dev/rtc with major number 10 and minor number 135 using mknod ("man mknod"), you - 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/