UBI and OneNAND
Hi,
Quoted 8 lines
Quoted 8 lines
##
## Look at existing devices
##
/ # ls -l/dev/mtdblock?brw-r----- 1 0 0 31, 0 Jan 1 00:00 /dev/mtdblock0 brw-r----- 1 0 0 31, 1 Jan 1 00:00 /dev/mtdblock1 brw-r----- 1 0 0 31, 2 Jan 1 00:00 /dev/mtdblock2 brw-r----- 1 0 0 31, 3 Jan 1 00:00 /dev/mtdblock3
Quoted 7 lines
Yo do not need mtdblock devices to mount JFFS2 at all. JFFS2 anyway works with MTD devices directly and this is just an old way to mount JFFS2.
/dev/mtdXare character devices and you cannot feed the mount utility by character devices, so this is why fake block devices were used. Nowadays there is device-less mount support and you may use:mount mtd7
/mnt/nvm
Yes, I can mount ubi with avobe method.
I can't mount with name but It's possible with new mtdblock node
mtd = 3 -> mtd > 7
# mount -t jffs2 /dev/mtdblock7 /mnt
I will send more detailed description tomorrow.
Thank you,
Kyungmin Park
Hello,
Quoted 9 lines · Kyungmin Park
Quoted 7 lines
Yo do not need mtdblock devices to mount JFFS2 at all. JFFS2 anyway works with MTD devices directly and this is just an old way to mount JFFS2.
/dev/mtdXare character devices and you cannot feed the mount utility by character devices, so this is why fake block devices were used. Nowadays there is device-less mount support and you may use:mount mtd7
/mnt/nvmYes, I can mount ubi with avobe method.
The device-less mount I described is a feature of *JFFS2*. It does not depend on if there is UBI or not.
You are just trying to do an incorrect thing.
It is similar to LVM - you feed hard drives to LVM, then create LVM volumes, then mount those LVM volumes, not the hard drives. Similar in case of UBI. You feed mtd3 to UBI, then you create UBI volumes which are also accessible as emulated MTD devices, and you mount _those_ MTD devices.
Signature · 2 lines
Best regards, Artem Bityutskiy (Битюцкий Артём)