Hi Christian, ansuelsmth@xxxxxxxxx wrote on Fri, 9 Aug 2024 19:20:58 +0200: > This small series handle 2 problems. > > It does try to ""standardize"" the usage of block2mtd module with > MTD OF nodes. > > It is very easy to add support for MTD parser by just adding an > OF node to the mtd created for block2mtd. > > This apply only if the root block is used for block2mtd to allow > scenario where the full eMMC or an NVME is used for MTD and it doesn't > have any partition table. > > To also support NVME, similar to how it's done with eMMC, we introduce > a subnode to the NVME controller that needs to have the "nvme-card" > compatible where a dev can define fixed-paritions for MTD parser usage. > > This series also add support for the Airoha partition table where > the last partition is always ART and is placed at the end of the flash. > > This require dynamic calculation of the offset as some dedicated > driver for bad block management might be used that reserve some space > at the end of the flash for block accounting. Who is reserving this space? And this is not reflected anywhere in the partition table? > New aarch64 Airoha SoC make use of this partition table and use block2mtd > for eMMC to treat them as MTD with custom bad block management and block > tracking. I am sorry, I am not used to such use cases, and I really fail getting why you would like to use mtd with an eMMC. Can you explain a little bit more what is not available in the block world that you really need from mtd? Also, did you consider nvmem layouts instead to detect and define the ART area? (just asking). Thanks, Miquèl
