"Leon Woestenberg" <leon.woestenberg@gmail.com> wrote:
quoted text
> Haavard,
> 
> On Tue, Sep 30, 2008 at 1:55 PM, Haavard Skinnemoen
> <haavard.skinnemoen@atmel.com> wrote:
> > The CFI information read from AT49BV6416 lists the erase regions in the
> > wrong order, causing problems when trying to erase or update the first
> > or last 64K block.
> >
> Are there other Atmel designs with this bug or only the chip with this CFI ID?

That's a good question. I guess there may be others in the same family
with the same bug. I don't really know.

The replacement, AT49BV642D, does not have this bug.

quoted text
> I ask, because the check in u-boot is too generic; I found u-boot
> wrongly assumes wrong order for another Atmel part, not checking on a
> specific CFI ID.

That's interesting...especially since u-boot only reads the low byte
of the JEDEC ID, so adding a fixup for one particular ID may match tons
of chips with 16-bit IDs.

I'll have to check the latest u-boot and see if it breaks any of my
boards.

Haavard
--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/