[PATCH 1/2] mtdpart: memory accessor interface for MTD layer
david-b at pacbell.net
Wed Aug 4 06:31:45 EDT 2010
--- On Wed, 8/4/10, David Woodhouse <dwmw2 at infradead.org> wrote:
> 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.
EMPHASIS ON "CORRECT" ...
> I don't see how.
> The only information it passes to the callout is the
> information it was
> already *given* in the partition structure.
There can be multiple such structures, each
of which describes different data to be extracted
from different persistent media contexts.
Examples: one context holds one MAC address (and
another, a different one) ... another might embed
calibration data; another, serial numbers; etc.
Pass the wrong context around, you've trashed all
the data instead of getting it right.
> 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.
"Initialization sequence" is a grab-bag category
that covers most init issues.
Point is to ensure that enough of the right context
information is available to initialize correctly.
So the right data is extracted and passed on.
> I'm also unhappy that it only works on partitioned devices
> -- that seems wrong.
Very different issue. Seems easily fixable
if needed. Agreed that e.g. EEPROMS won't
often be partitioned (unlike flash).
More information about the linux-mtd