>
> Dear Stefan,
>
> In message <20100623131040.ga23...@frolo.macqel> Philippe De Muyter wrote:
> > Hello Wolfgang & list,
> >
> > This is a revised patch, with comments and indentation fixed, I hope.
> >
> > I have "ported" U-boot to a in house made board with Numonyx Axcell P33/P30
> > 256-Mbit 65nm flash chips.
> >
> > After some time :( searching for bugs in our board or soft, we have
> > discovered that those chips have a small but annoying bug, documented in
> > "Numonyx Axcell P33/P30 256-Mbit Specification Update"
> >
> > It states :
> > When customer uses [...] block unlock, the block lock status might be
> > altered inadvertently. Lock status might be set to either 01h or 03h
> > unexpectedly (00h as expected data), which leads to program/erase failure
> > on certain blocks.
> >
> > A working workaround is given, which I have applied and tested with success.
> >
> > Signed-off-by: Philippe De Muyter <p...@macqel.be>
> >
> > ---
> > drivers/mtd/cfi_flash.c | 27 ++++++++++++++++++++-------
> > 1 files changed, 20 insertions(+), 7 deletions(-)
>
> I didn't see comments from you?
>
> Best regards,
>
> Wolfgang Denk
Doesn't the Linux kernel need the same fix? Would be great if
you(Philippe) could provide one. I too have such chips but I have
never seen this problem so I guess I have been lucky so far :)
Jocke
_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
