From: Elvis D. <elv...@ma...> - 2010-04-01 18:00:47
|
Thanks Dave! On Apr 1, 2010, at 9:49 PM, Dave Hylands wrote: > Running > > mtd_debug info /dev/mtd0 > > reports the following: > > mtd.type = MTD_NANDFLASH > mtd.flags = MTD_CAP_ROM > mtd.size = 524288 (512K) > mtd.erasesize = 131072 (128K) > mtd.writesize = 2048 (2K) > mtd.oobsize = 64 > regions = 0 > > So this corresponds to a blocksize (aka erasesize) of 128K which is > made up of 64 x 2K pages (aka writesize). I just needed to check if everything matched up, which I think it does, at the moment, in terms of block size. Creating 7 MTD partitions on "omap2-nand": 0x000000000000-0x000000080000 : "xloader" 0x000000080000-0x000000240000 : "uboot" 0x000000240000-0x000000280000 : "uboot environment" 0x000000280000-0x000000680000 : "linux" 0x000000680000-0x00000a680000 : "system" 0x00000a680000-0x00000c680000 : "userdata" 0x00000c680000-0x00000e680000 : "cache" root@overo:/# cat /proc/mtd dev: offset size erasesize name mtd0: 0x000000000000 00080000 00020000 "xloader" mtd1: 0x000000080000 001c0000 00020000 "uboot" mtd2: 0x000000240000 00040000 00020000 "uboot environment" mtd3: 0x000000280000 00400000 00020000 "linux" mtd4: 0x000000680000 0a000000 00020000 "system" mtd5: 0x00000a680000 02000000 00020000 "userdata" mtd6: 0x00000c680000 02000000 00020000 "cache" Best regards, Elvis |