From: Michael Brandt
extfs.c assumes that there is always a valid inode_size field in the
superblock. But this is not true for ext2fs rev 0. Such ext2fs images are for
instance generated by genext2fs. Symptoms on ARM machines are messages like:
"raise: Signal # 8 caught"
This fix chec
Hello,
> Here also Wolfgang Denk says that ext2 is currently broken in u-boot
> for newer ext2 images.
I rather would say it is broken for rev 0,
i.e. old ext2 images and images generated with genext2fs
> Is this still true or has it been fixed since then?
I just posted a patch: [PATCH] EXT2FS:
2 matches
Mail list logo