On Fri, Nov 13, 2015 at 11:00 PM, Brian Norris
<[email protected]> wrote:
(...)
> (2) we should define a comptible property for the hard-coded
> partitioning case (e.g., compatible = "partitions")
(...)
> If we went with option (2), then ofpart.c could just check only for
> 'compatible = "partitions"' (or similar), and if not found bail out.
So this "hard-coded partitioning case" the case is where all partitions
are defined in the device tree as described in
Documentation/devicetree/bindings/mtd/partition.txt ?
Or is it a way to indicate that this array
static const char * const part_probe_types_def[] = {
"cmdlinepart", "RedBoot", "ofpart", "ofoldpart", NULL };
in physmap_of.c should be used?
Sorry if I don't fully follow, I'm a bit stupid when it comes to the MTD
helicopter view of the situation.... :(
> I think option (2) makes more sense. But it would require an update to
> the binding and code for 4.4, since [1] was only introduced during this
> release cycle.
Does that mean all old device trees that specify no compatible
string all of a sudden stop working? We can't break the DT ABI, so I
guess not.
A bit confused here, I can't really see what I should do with the patch...
Yours,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe devicetree-spec" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
