From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Message-ID: <46713711.5010709@ru.mvista.com> Date: Thu, 14 Jun 2007 16:39:45 +0400 From: Sergei Shtylyov MIME-Version: 1.0 To: David Gibson Subject: Re: [PATCH] powerpc: Create "rom" (MTD) device prpmc2800 References: <7878cf1aec340b976b90b86b9e83bf18@kernel.crashing.org> <20070612044246.GC4198@localhost.localdomain> <9fbd7a7f5cdde58768569ab23c7aec7c@kernel.crashing.org> <20070613061254.GG16148@localhost.localdomain> <20070613091904.GA30948@localhost.localdomain> <791ab8b82c5b5d2b3ae4827a891a43ea@kernel.crashing.org> <20070614042906.GC11177@localhost.localdomain> In-Reply-To: <20070614042906.GC11177@localhost.localdomain> Content-Type: text/plain; charset=us-ascii; format=flowed Cc: linuxppc-dev List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , David Gibson wrote: >>>>How do non-device-tree MTD users handle this? >>>Invidual, board-specific map files with hardcoded partition tables. >>That's what I was afraid of. Sigh. >>>See drivers/mtd/maps/ebony.c for example. >>[/me looks...] Oh horror. >>>Hence my view of the device >>>tree as a preferable option. >>I think some binary partition table format that can be >>used by _all_ MTD consumers should be defined. How >>that table should be communicated to the kernel in the >>device tree case we can discuss later, then. Maybe >>something as simple as storing it in flash, and have a >>"partition-table-offset" property or something like that. >>This is something the MTD people will have to buy into >>of course. > I tought I saw some config option implying that there already existed > an on-device partition table format for flashes. Doesn't help us for You probably mean RedBoot table? > existing boards which don't expect such a setup, of course. Exactly. It's specific to RedBoot. WBR, Sergei