[...]
> > > I'm assuming it's per partition type rather than storage medium (e.g. > > > SATA, USB, SD, NAND, SPI-NOR)? GPT, 'fixed-partitions', other DT > > > partition bindings, etc. If so, then I'm really wondering why it's a > > > standalone tree rather than integrated into those existing partition > > > bindings. > > > > I think it's per medium, unless I misunderstood something. Sughosh? > > The bindings would be required as per the metadata access mechanism. > So for example, the MTD bindings would suffice for all the storage > mediums which would have MTD based partitioning schemes. Same for all > GPT partitioned devices. Again, as for the need for a separate node > with the compatible property, it is as per the driver model design. > For the other properties, we can indeed have them integrated with the > corresponding partition bindings. Ok, Rob is correct then it really is per partition type. Thanks /Ilias > > -sughosh
