Bug#813995: flash-kernel: writes to nand without being aware of bad blocks

[Gijs Hillenius <gijs@hillenius.net>]

I installed Debian Jessie on a ReadyNas102 that has a bad block, like so:

,----
| NAND:  (ID 0xf1ad)      128 MiB
| MMC:   MRVL_MMC: 0
| Bad block table found at page 65472, version 0x01
| Bad block table found at page 65408, version 0x01
| nand_read_bbt: Bad block at 0x000000240000
`----

Where using the current flash-kernel resulted in a non-booting
system, with messages like these:

,----
| nand: nand_erase_nand: attempt to erase a bad block at page 0x00000480
| mtdblock: erase of region [0x40000, 0x20000] on "uImage" failed
`----

I can confirm that Uwe's patched flash-kernel works. Short quote from
the log:

,----
| flash-kernel: appending /usr/lib/linux-image-3.16.0-4-armmp/armada-370-netgear-rn102.dtb to kernel
| Generating kernel u-boot image... done.
| Erasing 128 Kibyte @ 20000 --  2 % complete flash_erase: Skipping bad block at 00040000
| Erasing 128 Kibyte @ 5e0000 -- 100 % complete 
| Writing data to block 0 at offset 0x0
| Writing data to block 1 at offset 0x20000
| Writing data to block 2 at offset 0x40000
| Bad block at 40000, 1 block(s) from 40000 will be skipped
| Writing data to block 3 at offset 0x60000
`----

-- 
Caution: Keep out of reach of children.