From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from pentafluge.infradead.org (pentafluge.infradead.org [213.146.154.40]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTP id 75A8E67A2E for ; Fri, 5 May 2006 09:34:36 +1000 (EST) Received: from nat-pool-stn.redhat.com ([62.200.124.98] helo=hades.cambridge.redhat.com) by pentafluge.infradead.org with esmtpsa (Exim 4.61 #1 (Red Hat Linux)) id 1FbnL5-0000lh-Se for linuxppc-dev@ozlabs.org; Fri, 05 May 2006 00:34:32 +0100 Subject: Flash map information in device tree. From: David Woodhouse To: linuxppc-dev@ozlabs.org Content-Type: text/plain Date: Fri, 05 May 2006 00:34:42 +0100 Message-Id: <1146785683.2885.148.camel@hades.cambridge.redhat.com> Mime-Version: 1.0 List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , I'd like to get rid of some of the 'map' drivers in drivers/mtd/maps/ and replace them with simple platform devices. On PPC, I'd like to do that with nodes in the device tree, with appropriate properties: - physical address - size - bankwidth - chip probe type (CFI/JEDEC/RAM/ROM/etc) - partitioning information Can we define a format for this so it can be included in the device trees which we're presumably going to be generating for the embedded boards which are supported by the arch/powerpc kernel? If we can get either an updated u-boot or a boot wrapper which work on the Wind River SBC8265 or SBC8560 boards, I might even be able to test it myself. -- dwmw2