On 5 December 2015 at 11:15, Geert Uytterhoeven <geert@xxxxxxxxxxxxxx> wrote: > On Sat, Dec 5, 2015 at 6:19 AM, Brian Norris > <computersforpeace@xxxxxxxxx> wrote: >> There have been several discussions [1] about adding a device tree binding for >> associating flash devices with the partition parser(s) that are used on the >> flash. There are a few reasons: >> >> (1) drivers shouldn't have to be encoding platform knowledge by listing what >> parsers might be used on a given system (this is the currently all that's >> supported) >> (2) we can't just scan for all supported parsers (like the block system does), since >> there is a wide diversity of "formats" (no standardization), and it is not >> always safe or efficient to attempt to do so, particularly since many of >> them allow their data structures to be placed anywhere on the flash, and >> so require scanning the entire flash device to find them. > > I read the second reason, but would it be useful to (partially) merge > block/partitions/ and drivers/mtd/partitions/, so I can use e.g. msdos > partitions > on an mtd device?? > Using msdos partition on a MTD device does not sound terribly useful. On what kind of non-block device would you expect to find one? On the other hand, using FMAP on a block device might work an even might have some uses. Thanks Michal -- To unsubscribe from this list: send the line "unsubscribe devicetree-spec" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
