diff for duplicates of <87siubneuf.fsf@natisbad.org> diff --git a/a/1.txt b/N1/1.txt index 0f87200..38eb237 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -45,7 +45,7 @@ long. AFAICT, the log output seems to indicate that blocks are which is also what mtdinfo reports: - root@mood:~# mtdinfo /dev/mtd4 + root at mood:~# mtdinfo /dev/mtd4 mtd4 Name: jffs2 Type: nand @@ -81,7 +81,7 @@ expected that the partition definition (start address and length) > > So we run the test a few more times, just to be sure. -root@mood:~# nandtest --passes 2 /dev/mtd4 +root at mood:~# nandtest --passes 2 /dev/mtd4 ECC corrections: 0 ECC failures : 0 Bad blocks : 8 @@ -107,7 +107,7 @@ Bad block at 0x067e0000 Finished pass 2 successfully ->> root@mood:~# nandwrite -p /dev/mtd4 /tmp/toto +>> root at mood:~# nandwrite -p /dev/mtd4 /tmp/toto >> ... >> Writing data to block 795 at offset 0x6360000 >> Writing data to block 796 at offset 0x6380000 @@ -132,12 +132,12 @@ Finished pass 2 successfully Well, I did the same test again, and I think the answer is 'no': -root@mood:~# dd if=/dev/mtd4 of=/tmp/toto +root at mood:~# dd if=/dev/mtd4 of=/tmp/toto 212992+0 records in 212992+0 records out 109051904 bytes (109 MB) copied, 11.136 s, 9.8 MB/s -root@mood:~# flash_erase /dev/mtd4 0 0 +root at mood:~# flash_erase /dev/mtd4 0 0 Erasing 128 Kibyte @ 66e0000 -- 98 % complete flash_erase: Skipping bad block at 06700000 flash_erase: Skipping bad block at 06720000 flash_erase: Skipping bad block at 06740000 @@ -148,7 +148,7 @@ flash_erase: Skipping bad block at 067c0000 flash_erase: Skipping bad block at 067e0000 Erasing 128 Kibyte @ 67e0000 -- 100 % complete -root@mood:~# nandwrite -p /dev/mtd4 /tmp/toto +root at mood:~# nandwrite -p /dev/mtd4 /tmp/toto Writing data to block 0 at offset 0x0 Writing data to block 1 at offset 0x20000 Writing data to block 2 at offset 0x40000 @@ -186,7 +186,7 @@ nandwrite: error!: /dev/mtd4: MTD get bad block failed error 22 (Invalid argument) nandwrite: error!: Data was only partially written due to error error 22 (Invalid argument) -root@mood:~# +root at mood:~# Well, this time I don't get the "ready timeout" error I had last time around block 800. I did the test a second time (flash_erase and diff --git a/a/content_digest b/N1/content_digest index 6b10711..73f2e19 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -9,16 +9,9 @@ "ref\087bo12kcyt.fsf@natisbad.org\0" "ref\020131202103305.GB2466@localhost\0" "From\0arno@natisbad.org (Arnaud Ebalard)\0" - "Subject\0Re: [PATCH v5 00/14] Armada 370/XP NAND support\0" + "Subject\0[PATCH v5 00/14] Armada 370/XP NAND support\0" "Date\0Mon, 02 Dec 2013 22:05:28 +0100\0" - "To\0Ezequiel Garcia <ezequiel.garcia@free-electrons.com>\0" - "Cc\0Lior Amsalem <alior@marvell.com>" - Thomas Petazzoni <thomas.petazzoni@free-electrons.com> - Jason Cooper <jason@lakedaemon.net> - linux-mtd@lists.infradead.org - Gregory Clement <gregory.clement@free-electrons.com> - Brian Norris <computersforpeace@gmail.com> - " linux-arm-kernel@lists.infradead.org\0" + "To\0linux-arm-kernel@lists.infradead.org\0" "\00:1\0" "b\0" "Hi Ezequiel,\n" @@ -68,7 +61,7 @@ "\n" "which is also what mtdinfo reports:\n" "\n" - " root@mood:~# mtdinfo /dev/mtd4\n" + " root at mood:~# mtdinfo /dev/mtd4\n" " mtd4\n" " Name: jffs2\n" " Type: nand\n" @@ -104,7 +97,7 @@ ">\n" "> So we run the test a few more times, just to be sure.\n" "\n" - "root@mood:~# nandtest --passes 2 /dev/mtd4\n" + "root at mood:~# nandtest --passes 2 /dev/mtd4\n" "ECC corrections: 0\n" "ECC failures : 0\n" "Bad blocks : 8\n" @@ -130,7 +123,7 @@ "\n" "Finished pass 2 successfully\n" "\n" - ">> root@mood:~# nandwrite -p /dev/mtd4 /tmp/toto\n" + ">> root at mood:~# nandwrite -p /dev/mtd4 /tmp/toto\n" ">> ...\n" ">> Writing data to block 795 at offset 0x6360000\n" ">> Writing data to block 796 at offset 0x6380000\n" @@ -155,12 +148,12 @@ "\n" "Well, I did the same test again, and I think the answer is 'no':\n" "\n" - "root@mood:~# dd if=/dev/mtd4 of=/tmp/toto\n" + "root at mood:~# dd if=/dev/mtd4 of=/tmp/toto\n" "212992+0 records in\n" "212992+0 records out\n" "109051904 bytes (109 MB) copied, 11.136 s, 9.8 MB/s\n" "\n" - "root@mood:~# flash_erase /dev/mtd4 0 0\n" + "root at mood:~# flash_erase /dev/mtd4 0 0\n" "Erasing 128 Kibyte @ 66e0000 -- 98 % complete flash_erase: Skipping bad block at 06700000\n" "flash_erase: Skipping bad block at 06720000\n" "flash_erase: Skipping bad block at 06740000\n" @@ -171,7 +164,7 @@ "flash_erase: Skipping bad block at 067e0000\n" "Erasing 128 Kibyte @ 67e0000 -- 100 % complete \n" "\n" - "root@mood:~# nandwrite -p /dev/mtd4 /tmp/toto\n" + "root at mood:~# nandwrite -p /dev/mtd4 /tmp/toto\n" "Writing data to block 0 at offset 0x0\n" "Writing data to block 1 at offset 0x20000\n" "Writing data to block 2 at offset 0x40000\n" @@ -209,7 +202,7 @@ " error 22 (Invalid argument)\n" "nandwrite: error!: Data was only partially written due to error\n" " error 22 (Invalid argument)\n" - "root@mood:~# \n" + "root at mood:~# \n" "\n" "Well, this time I don't get the \"ready timeout\" error I had last\n" "time around block 800. I did the test a second time (flash_erase and\n" @@ -275,4 +268,4 @@ "\n" a+ -3d2885ee4acc62527eed5270b4231f795c3be3698248705843207dff665ed897 +6dc82b8b293396c15ff0424e22e2f53e778120ed64c098c88adbd7174f059c7c
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.