choosing a file system to use on NAND/UBI
Hamish Moffatt
hamish at cloud.net.au
Mon Apr 7 03:48:36 EDT 2008
On Mon, Apr 07, 2008 at 05:32:27PM +1000, Hamish Moffatt wrote:
> UBI attach time appears to be about 6 seconds.
>
> [ 0.960000] NAND device: Manufacturer ID: 0xec, Chip ID: 0xdc (Samsung NAND 512MiB 3,3V 8-bit)
> [ 0.970000] Scanning device for bad blocks
> [ 1.020000] Bad eraseblock 494 at 0x03dc0000
> [ 1.110000] Bad eraseblock 1300 at 0x0a280000
> [ 1.240000] Bad eraseblock 2554 at 0x13f40000
> [ 1.280000] Bad eraseblock 2923 at 0x16d60000
> [ 1.330000] Bad eraseblock 3349 at 0x1a2a0000
> [ 1.370000] Bad eraseblock 3790 at 0x1d9c0000
> [ 1.410000] cmdlinepart partition parsing not available
> [ 7.210000] UBI: attached mtd9 to ubi0
Less with some NAND glue improvements.
[ 0.960000] NAND device: Manufacturer ID: 0xec, Chip ID: 0xdc (Samsung NAND 512MiB 3,3V 8-bit)
[ 0.970000] Scanning device for bad blocks
[ 1.010000] Bad eraseblock 494 at 0x03dc0000
[ 1.060000] Bad eraseblock 1300 at 0x0a280000
[ 1.140000] Bad eraseblock 2554 at 0x13f40000
[ 1.170000] Bad eraseblock 2923 at 0x16d60000
[ 1.200000] Bad eraseblock 3349 at 0x1a2a0000
[ 1.230000] Bad eraseblock 3790 at 0x1d9c0000
[ 1.260000] cmdlinepart partition parsing not available
[ 6.910000] UBI: attached mtd9 to ubi0
Hamish
--
Hamish Moffatt VK3SB <hamish at debian.org> <hamish at cloud.net.au>
More information about the linux-mtd
mailing list