[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1280916725.19499.12.camel@localhost>
Date: Wed, 04 Aug 2010 11:12:05 +0100
From: David Woodhouse <dwmw2@...radead.org>
To: David Brownell <david-b@...bell.net>
Cc: 'Kevin Hilman' <khilman@...prootsystems.com>,
Sudhakar Rajashekhara <sudhakar.raj@...com>,
'Bernd Schmidt' <bernd.schmidt@...log.com>,
'Nicolas Pitre' <nico@...xnic.net>,
linux-kernel@...r.kernel.org,
'David Howells' <dhowells@...hat.com>,
'David Brownell' <dbrownell@...rs.sourceforge.net>,
linux-mtd@...ts.infradead.org,
'Andrew Morton' <akpm@...ux-foundation.org>
Subject: RE: [PATCH 1/2] mtdpart: memory accessor interface for MTD layer
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@...el.com Intel Corporation
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists