On Tue, 2011-07-26 at 14:27 +0200, David Wagner wrote:
> Advantages of ubiblk over gluebi+mtdblock_ro:
>
> * Simpler architecture
>
> * The numbering of devices is much easier with ubiblk than with
>gluebi+mtdblock_ro. With gluebi+mtdblock_ro, you get one additional
>MTD device for each
On Tue, 2011-07-26 at 14:27 +0200, David Wagner wrote:
> * The numbering of devices is much easier with ubiblk than with
>gluebi+mtdblock_ro. With gluebi+mtdblock_ro, you get one additional
>MTD device for each UBI volume, so the number of MTD devices grows
>quite a lot and is a bit di
On 07/26/2011 02:34 PM, Christoph Hellwig wrote:
>> TODO:
>> * the modules keeps a table of the devices which length is the
maximum number
>>of UBI volumes. It should make use of a linked list.
>
> A linked list isn't very nice either. Try using idr, which gives you
> both an allocator for t
> TODO:
> * the modules keeps a table of the devices which length is the maximum number
>of UBI volumes. It should make use of a linked list.
A linked list isn't very nice either. Try using idr, which gives you
both an allocator for the minor number space, and a way to look up
the structure
ubiblk is a read-only block layer on top of UBI. It presents UBI volumes as
read-only block devices.
It is used by putting a block filesystem image on a UBI volume and then mounting
the corresponding device (/dev/ubiblkX_Y where X is the UBI device number and Y
the volume ID).
It uses the UBI AP
