From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-in-04.arcor-online.net (mail-in-04.arcor-online.net [151.189.21.44]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mx.arcor.de", Issuer "Thawte Premium Server CA" (verified OK)) by ozlabs.org (Postfix) with ESMTP id 23FFCDDED2 for ; Thu, 17 May 2007 09:47:59 +1000 (EST) In-Reply-To: <0c3907573f12a0731d03335fe3334363@kernel.crashing.org> References: <1179245829.8132.100.camel@rhino> <1179246470.8132.112.camel@rhino> <1179333421.7018.17.camel@ld0161-tx32> <1179346653.8132.223.camel@rhino> <0c3907573f12a0731d03335fe3334363@kernel.crashing.org> Mime-Version: 1.0 (Apple Message framework v623) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: From: Segher Boessenkool Subject: Re: [PATCH 2/5] Add legacy devices to mpc8641_hpcn.dts Date: Thu, 17 May 2007 01:47:40 +0200 To: Segher Boessenkool Cc: linuxppc-dev List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , >>>>> + isa@f0 { >>> >>> isa@1e > > You didn't reply to this one, but you *really* need > to fix it. Oh you did reply, heh. >> Is there a recommended "compatible" property for a standard PC-like >> CMOS >> RTC? > > None in the bindings that I know of. It typically would > be the model name/number of the oldest chip used, or one > that is very commonly used. "pnpPNP,b00" Segher