diff for duplicates of <87ob4xbs8l.fsf@natisbad.org> diff --git a/a/1.txt b/N1/1.txt index 3164cd1..2a05ca1 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -58,7 +58,7 @@ ok. Will put a comment in the .dts about that. > On the other issue, about the timeout... > ->> 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 @@ -96,7 +96,7 @@ ok. Will put a comment in the .dts about that. >> error 22 (Invalid argument) >> nandwrite: error!: Data was only partially written due to error >> error 22 (Invalid argument) ->> root@mood:~# +>> root at mood:~# >> > > OK... Then I guess the driver works fine but you're trying to write @@ -137,10 +137,10 @@ is different (dual-core armada Xp mv78230 on RN2120 instead of Armada related config options: -root@thin:~# flash_erase /dev/mtd4 0 0 +root at thin:~# flash_erase /dev/mtd4 0 0 ... -root@thin:~# nandwrite -p /dev/mtd4 /tmp/mtd4ro +root at thin:~# nandwrite -p /dev/mtd4 /tmp/mtd4ro Writing data to block 0 at offset 0x0 [ 782.766892] pxa3xx-nand d00d0000.nand: Ready time out!!! libmtd: error!: cannot write 2048 bytes to mtd4 (eraseblock 0, offset 2048) @@ -193,7 +193,7 @@ Writing data to block 9 at offset 0x120000 So I decided to increase CHIP_DELAY_TIMEOUT in the driver as you suggested in a previous email (HZ instead of 2*HZ/10): -root@thin:~# nandwrite -p /dev/mtd4 mtd4ro +root at thin:~# nandwrite -p /dev/mtd4 mtd4ro Writing data to block 0 at offset 0x0 [ 273.917098] pxa3xx-nand d00d0000.nand: Ready time out!!! libmtd: error!: cannot write 2048 bytes to mtd4 (eraseblock 0, offset 2048) @@ -215,7 +215,7 @@ Writing data to block 3 at offset 0x60000 And then to 25*HZ/10 (I know it's a lot): -root@thin:~# nandwrite /dev/mtd4 mtd4ro +root at thin:~# nandwrite /dev/mtd4 mtd4ro Writing data to block 0 at offset 0x0 [ 192.118574] 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 e9876ff..61d2c71 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -10,16 +10,9 @@ "ref\087siubneuf.fsf@natisbad.org\0" "ref\020131203002225.GA5333@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\0Tue, 03 Dec 2013 21:21:30 +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" @@ -82,7 +75,7 @@ "\n" "> On the other issue, about the timeout...\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" @@ -120,7 +113,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" ">\n" "> OK... Then I guess the driver works fine but you're trying to write\n" @@ -161,10 +154,10 @@ "related config options:\n" "\n" "\n" - "root@thin:~# flash_erase /dev/mtd4 0 0\n" + "root at thin:~# flash_erase /dev/mtd4 0 0\n" "...\n" "\n" - "root@thin:~# nandwrite -p /dev/mtd4 /tmp/mtd4ro \n" + "root at thin:~# nandwrite -p /dev/mtd4 /tmp/mtd4ro \n" "Writing data to block 0 at offset 0x0\n" "[ 782.766892] pxa3xx-nand d00d0000.nand: Ready time out!!!\n" "libmtd: error!: cannot write 2048 bytes to mtd4 (eraseblock 0, offset 2048)\n" @@ -217,7 +210,7 @@ "So I decided to increase CHIP_DELAY_TIMEOUT in the driver as you\n" "suggested in a previous email (HZ instead of 2*HZ/10):\n" "\n" - "root@thin:~# nandwrite -p /dev/mtd4 mtd4ro \n" + "root at thin:~# nandwrite -p /dev/mtd4 mtd4ro \n" "Writing data to block 0 at offset 0x0\n" "[ 273.917098] pxa3xx-nand d00d0000.nand: Ready time out!!!\n" "libmtd: error!: cannot write 2048 bytes to mtd4 (eraseblock 0, offset 2048)\n" @@ -239,7 +232,7 @@ "\n" "And then to 25*HZ/10 (I know it's a lot):\n" "\n" - "root@thin:~# nandwrite /dev/mtd4 mtd4ro \n" + "root at thin:~# nandwrite /dev/mtd4 mtd4ro \n" "Writing data to block 0 at offset 0x0\n" "[ 192.118574] pxa3xx-nand d00d0000.nand: Ready time out!!!\n" "libmtd: error!: cannot write 2048 bytes to mtd4 (eraseblock 0, offset 2048)\n" @@ -262,4 +255,4 @@ "\n" a+ -8e2656ef1d55a96e9f49ee1cc7cc33b7ba3d709c37dab0fa65eb5761cdab7c77 +c985df1a2f527f1fec38f60fe86b43c1ebf9b0e3899c8edd01897876c6556581
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.