On Fri, Sep 9, 2011 at 11:29 PM, Jon Ringle <jon@xxxxxxxxxx> wrote: > I have a NAND device with a few bad eraseblocks, which is not > uncommon. I figured that barebox would properly handle avoiding the > bad eraseblocks. > So I was surprised when I discovered that this is not entirely the > case when I #define DEBUG at the top of nand.c. erase seems to honor > the bad eraseblocks, but write still silently uses the bad erase block > and read fails when it reads the bad eraseblock at 0x001e0000. Am I > missing something? I found that I had CONFIG_GLOB=n and that was causing /env/bin/hush_hack to fail to create the bad block aware devices with "nand -a /dev/nand0.*" Jon _______________________________________________ barebox mailing list barebox@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox
