From mboxrd@z Thu Jan 1 00:00:00 1970 Subject: RE: [PATCH 1/2] mtdpart: memory accessor interface for MTD layer From: David Woodhouse To: David Brownell In-Reply-To: <54038.80733.qm@web180305.mail.gq1.yahoo.com> References: <54038.80733.qm@web180305.mail.gq1.yahoo.com> Content-Type: text/plain; charset="UTF-8" Date: Wed, 04 Aug 2010 11:12:05 +0100 Message-ID: <1280916725.19499.12.camel@localhost> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Cc: 'Bernd Schmidt' , Sudhakar Rajashekhara , 'Nicolas Pitre' , 'Kevin Hilman' , linux-kernel@vger.kernel.org, 'David Howells' , 'David Brownell' , linux-mtd@lists.infradead.org, 'Andrew Morton' List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Wed, 2010-07-07 at 04:08 -0700, David Brownell wrote: > > I think the short answer is that the callout is > what provides the board drivers enough information > to make the correct calls. I don't see how. The only information it passes to the callout is the information it was already *given* in the partition structure. I'm more inclined to believe Sudhakar's claim that you'll get an 'initialization sequence problem', although I'm not sure I believe it can't be solved in a better way than this. I'm also unhappy that it only works on partitioned devices -- that seems wrong. -- David Woodhouse Open Source Technology Centre David.Woodhouse@intel.com Intel Corporation