06 May, 2016

1 commit


20 Oct, 2015

1 commit


21 May, 2014

1 commit


06 Mar, 2014

1 commit

  • In order to allow a future ioctl parameter, such as a creation flag,
    we change the UBI_IOCVOLCRBLK so it accepts a struct ubi_blkcreate_req.
    For the time being the structure is not in use, but fully reserved.

    This ABI change is still possible and harmless, because the ioctl has just
    been introduced and there's no userspace program which uses it.

    Signed-off-by: Ezequiel Garcia
    Signed-off-by: Artem Bityutskiy

    Ezequiel Garcia
     

05 Mar, 2014

1 commit

  • Rename the UBI_IOCVOLATTBLK and UBI_IOCVOLDETBLK to UBI_IOCVOLCRBLK and
    UBI_IOCVOLRMBLK, because we do not use terms "attach" and "detach" for the R/O
    block devices on top of UBI volumes. Instead, we use terms "create" and
    "remove". This patch also amends the related commentaries.

    Signed-off-by: Artem Bityutskiy
    Acked-by: Ezequiel Garcia

    Artem Bityutskiy
     

28 Feb, 2014

1 commit

  • This commit introduces read-only block device emulation on top of UBI volumes.

    Given UBI takes care of wear leveling and bad block management it's possible
    to add a thin layer to enable block device access to UBI volumes.
    This allows to use a block-oriented filesystem on a flash device.

    The UBI block devices are meant to be used in conjunction with any
    regular, block-oriented file system (e.g. ext4), although it's primarily
    targeted at read-only file systems, such as squashfs.

    Block devices are created upon user request through new ioctls:
    UBI_IOCVOLATTBLK to attach and UBI_IOCVOLDETBLK to detach.
    Also, a new UBI module parameter is added 'ubi.block'. This parameter is
    needed in order to attach a block device on boot-up time, allowing to
    mount the rootfs on a ubiblock device.
    For instance, you could have these kernel parameters:

    ubi.mtd=5 ubi.block=0,0 root=/dev/ubiblock0_0

    Or, if you compile ubi as a module:

    $ modprobe ubi mtd=/dev/mtd5 block=/dev/ubi0_0

    Artem: amend commentaries and massage the patch a little bit.

    Signed-off-by: Ezequiel Garcia
    Signed-off-by: Artem Bityutskiy

    Ezequiel Garcia
     

28 Oct, 2013

2 commits


29 May, 2013

1 commit

  • The current ioctl define implies that this func expects to be passed a
    64bit number directly rather than a pointer to a 64bit. The code that
    processes this ioctl shows that it clearly expects a pointer.

    It'd be best if we could change the type to "__s64*", but that would
    change the generated ioctl number thus breaking the userland ABI. So
    just add a comment for intrepid developers.

    Signed-off-by: Mike Frysinger
    Signed-off-by: Artem Bityutskiy

    Mike Frysinger
     

09 Oct, 2012

1 commit


03 Oct, 2012

1 commit