diff for duplicates of <87iov5aapx.fsf@natisbad.org> diff --git a/a/1.txt b/N1/1.txt index d126da9..11402b6 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,6 +1,6 @@ Hi Ezequiel, -arno@natisbad.org (Arnaud Ebalard) writes: +arno at natisbad.org (Arnaud Ebalard) writes: > So I guess, if you have any (non hardware destructive ;-) ) idea, I now > have a platform on which the problem is reproducible. Meanwhile, I will @@ -10,7 +10,7 @@ Well, on the RN104 (same chip, same kernel and same SoC as the RN102), I have the following (I get the same with a patched driver to increase the timeout): -root@humble:~# flash_erase /dev/mtd4 0 0 +root at humble:~# flash_erase /dev/mtd4 0 0 Erasing 128 Kibyte @ 72e0000 -- 99 % complete flash_erase: Skipping bad block at 07300000 flash_erase: Skipping bad block at 07320000 flash_erase: Skipping bad block at 07340000 @@ -21,7 +21,7 @@ flash_erase: Skipping bad block at 073c0000 flash_erase: Skipping bad block at 073e0000 Erasing 128 Kibyte @ 73e0000 -- 100 % complete -root@humble:~# nandwrite -p /dev/mtd4 mtd4ro +root at humble:~# nandwrite -p /dev/mtd4 mtd4ro Writing data to block 0 at offset 0x0 [ 449.915173] pxa3xx-nand d00d0000.nand: Ready time out!!! libmtd: error!: cannot write 2048 bytes to mtd4 (eraseblock 0, offset 2048) diff --git a/a/content_digest b/N1/content_digest index 97b4c22..8dd3d15 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -11,21 +11,14 @@ "ref\020131203002225.GA5333@localhost\0" "ref\087ob4xbs8l.fsf@natisbad.org\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\0Tue, 03 Dec 2013 22:25:14 +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" "\n" - "arno@natisbad.org (Arnaud Ebalard) writes:\n" + "arno at natisbad.org (Arnaud Ebalard) writes:\n" "\n" "> So I guess, if you have any (non hardware destructive ;-) ) idea, I now\n" "> have a platform on which the problem is reproducible. Meanwhile, I will\n" @@ -35,7 +28,7 @@ "have the following (I get the same with a patched driver to increase the\n" "timeout):\n" "\n" - "root@humble:~# flash_erase /dev/mtd4 0 0 \n" + "root at humble:~# flash_erase /dev/mtd4 0 0 \n" "Erasing 128 Kibyte @ 72e0000 -- 99 % complete flash_erase: Skipping bad block at 07300000\n" "flash_erase: Skipping bad block at 07320000\n" "flash_erase: Skipping bad block at 07340000\n" @@ -46,7 +39,7 @@ "flash_erase: Skipping bad block at 073e0000\n" "Erasing 128 Kibyte @ 73e0000 -- 100 % complete \n" "\n" - "root@humble:~# nandwrite -p /dev/mtd4 mtd4ro \n" + "root at humble:~# nandwrite -p /dev/mtd4 mtd4ro \n" "Writing data to block 0 at offset 0x0\n" "[ 449.915173] pxa3xx-nand d00d0000.nand: Ready time out!!!\n" "libmtd: error!: cannot write 2048 bytes to mtd4 (eraseblock 0, offset 2048)\n" @@ -102,4 +95,4 @@ "a specific option (debug or something else) may have an impact on how the\n" driver behave. -ad9dbafe2c891e10549fd8b8a62215d98ee3a0af2c2703a0cad835145fe5c61e +aeec67a5963263859d1f9121e071d1b72c8b666d402aaef82703953f4ac68de8
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.