From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate.crashing.org (gate.crashing.org [63.228.1.57]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTPS id D134DDDEF8 for ; Mon, 31 Mar 2008 04:15:56 +1000 (EST) In-Reply-To: <20080327100304.GC10397@localhost.localdomain> References: <200803101606.39184.laurentp@cse-semaphore.com> <200803251914.24021.laurentp@cse-semaphore.com> <47EA4741.2050402@ru.mvista.com> <200803271013.32612.laurentp@cse-semaphore.com> <20080327100304.GC10397@localhost.localdomain> Mime-Version: 1.0 (Apple Message framework v623) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <7c44646510c3b98075de9aa57cad0bce@kernel.crashing.org> From: Segher Boessenkool Subject: Re: OF compatible MTD platform RAM driver ? Date: Sun, 30 Mar 2008 20:15:46 +0200 To: David Gibson Cc: ben@simtec.co.uk, linuxppc-dev@ozlabs.org, linux-mtd@lists.infradead.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , >> Could we agree on a name ? I'd like to submit a new patch. > > For ROMs I think just plain "rom" should be sufficient. Yes. > For RAMs we > need something to indicate that it's memory but intended for secondary > storage, not as main memory. How it is intended to be used is not a property of the hardware, so that information doesn't belong in the device tree at all. The Linux platform code should handle this, I imagine. Segher