[PATCH v6 01/11] mtd: core: always create master device
Richard Weinberger
richard at nod.at
Mon Jun 9 21:27:09 UTC 2025
----- Ursprüngliche Mail -----
> Von: "Guenter Roeck" <linux at roeck-us.net>
>>> I am trying to boot from "pnor". It looks like the partition data (from
>>> devicetree)
>>> is now ignored. mtdblock6 used to be the second flash.
>>>
>>> Guenter
>>
>> Is this with CONFIG_MTD_PARTITIONED_MASTER?
>>
>
> Yes
>
>> I think that mtd_is_partition is ambiguous now.
>> We always have master partition when CONFIG_MTD_PARTITIONED_MASTER
>> is enabled and parent check is useless.
>> We must check grandparent in this case.
>> Miquel, am I right?
>>
>> We can return to older patch version that have created partition
>> instead of the master device.
>> Or try to fix mtd_is_partition, like below.
>> Guenter, is below patch helps?
>>
> No, it does not make a difference. Partitions are still not created.
Looks like all partition parsing is broken when CONFIG_MTD_PARTITIONED_MASTER=y is set.
Alexander, I was able to reproduce with MTDRAM and the mtdparts= kernel parameter.
Build with CONFIG_MTD_MTDRAM=y and CONFIG_MTD_PARTITIONED_MASTER=y,
pass mtdparts=\"mtdram test device:256k(foo)ro,-(bar)\" to the kernel command line.
Before your change:
$ cat /proc/mtd
dev: size erasesize name
mtd0: 00400000 00020000 "mtdram test device"
mtd1: 00040000 00020000 "foo"
mtd2: 003c0000 00020000 "bar"
After:
$ cat /proc/mtd
dev: size erasesize name
mtd0: 00400000 00020000 "mtdram test device"
Hope this helps!
Thanks,
//richard
More information about the dri-devel
mailing list