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 fACGDp524932 for linux-mips-outgoing; Mon, 12 Nov 2001 08:13:51 -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 fACGDm024929 for ; Mon, 12 Nov 2001 08:13:48 -0800 Received: from zeus.mvista.com (zeus.mvista.com [10.0.0.112]) by hermes.mvista.com (8.11.0/8.11.0) with ESMTP id fACGDgB04379; Mon, 12 Nov 2001 08:13:42 -0800 Subject: Re: [RFC] generic MIPS RTC driver From: Pete Popov To: "Maciej W. Rozycki" Cc: Geert Uytterhoeven , Jun Sun , Linux/MIPS Development , Linux/m68k , Linux/PPC Development In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.99.1+cvs.2001.11.07.16.47 (Preview Release) Date: 12 Nov 2001 08:14:39 -0800 Message-Id: <1005581679.459.4.camel@zeus> Mime-Version: 1.0 Sender: owner-linux-mips@oss.sgi.com Precedence: bulk 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. Pete