On 15 December 2014 at 06:29, John Crispin wrote:
> On 14/12/2014 21:37, Rafał Miłecki wrote:
>> 1) I've modified DT to create "ubi" MTD partition on NAND
>> 2) Wrote a simple preinit_main script creating "rootfs_data2" UBI volume
>> 3) Modified fstools to prefer rootfs_data2 over rootfs_data if i
On 14/12/2014 21:37, Rafał Miłecki wrote:
> 1) I've modified DT to create "ubi" MTD partition on NAND
> 2) Wrote a simple preinit_main script creating "rootfs_data2" UBI volume
> 3) Modified fstools to prefer rootfs_data2 over rootfs_data if it exists
i dont like that bit at all. its a work arou
On 14 December 2014 at 19:55, John Crispin wrote:
> gregley sent a extroot ubi support patch.
>
> with this in place 2 scenarios are possible.
>
> 1) install rootfs on your spi and with a extroot default config that
> will copy the whole content over to the ubi. magic markers might be
> required h
Hi,
gregley sent a extroot ubi support patch.
with this in place 2 scenarios are possible.
1) install rootfs on your spi and with a extroot default config that
will copy the whole content over to the ubi. magic markers might be
required here. currently extroot write a magic file to the external
Hi, this partially a continuation of the
"Some standard partition name for extra user data?"
thread.
Summary:
1) I have device with serial flash (16 MiB) and NAND flash (128 MiB).
2) Serial flash contains 2 partitions: "bootloader" and "firmware".
3) Bootloader writes supplied image to the "firmwa
