From mboxrd@z Thu Jan 1 00:00:00 1970 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id fACIShq02157 for linux-mips-outgoing; Mon, 12 Nov 2001 10:28:43 -0800 Received: from hermes.mvista.com (gateway-1237.mvista.com [12.44.186.158]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id fACISe002154 for ; Mon, 12 Nov 2001 10:28:40 -0800 Received: from mvista.com (IDENT:jsun@orion.mvista.com [10.0.0.75]) by hermes.mvista.com (8.11.0/8.11.0) with ESMTP id fACIRwB11557; Mon, 12 Nov 2001 10:27:58 -0800 Message-ID: <3BF0145C.9795C8CC@mvista.com> Date: Mon, 12 Nov 2001 10:26:36 -0800 From: Jun Sun X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.18 i686) X-Accept-Language: en MIME-Version: 1.0 To: Pete Popov CC: "Maciej W. Rozycki" , Geert Uytterhoeven , Linux/MIPS Development , Linux/m68k , Linux/PPC Development Subject: Re: [RFC] generic MIPS RTC driver References: <1005581679.459.4.camel@zeus> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-mips@oss.sgi.com Precedence: bulk Pete Popov wrote: > > On Mon, 2001-11-12 at 05:29, Maciej W. Rozycki wrote: > > On Mon, 12 Nov 2001, Geert Uytterhoeven wrote: > > > > > > Unless you use a non-MC146818 RTC, which you need to write a separate > > > > driver for anyway. > > > > > > Yep, so that's why both m68k and PPC have common routines to read/write the > > > RTC, with a /dev/rtc-compatible abstraction on top of it. > > > > OK, then you need an RTC chipset-specific driver and not a CPU > > architecture-specific one. Otherwise we'll end with a zillion of similar > > RTC drivers like we already have for LANCE and SCC chips. > > I agree. We don't have arch specific network drivers so why have arch > specific rtc drivers. > Because we can have a free RTC driver working once you get kernel working. Jun