On Fri, 27 Mar 2009 23:30:19 +0100 Jean-Christophe PLAGNIOL-VILLARD <plagn...@jcrosoft.com> wrote:
> diff --git a/drivers/mtd/cfi_flash.c b/drivers/mtd/cfi_flash.c > index 631b969..175d82a 100644 > --- a/drivers/mtd/cfi_flash.c > +++ b/drivers/mtd/cfi_flash.c > @@ -1788,13 +1788,10 @@ static void flash_fixup_atmel(flash_info_t > *info, struct cfi_qry *qry) > /* AT49BV6416(T) list the erase regions in the wrong order. > * However, the device ID is identical with the non-broken > - * AT49BV642D since u-boot only reads the low byte (they > - * differ in the high byte.) So leave out this fixup for now. > + * AT49BV642D they differ in the high byte. > */ > -#if 0 > if (info->device_id == 0xd6 || info->device_id == 0xd2) > reverse_geometry = !reverse_geometry; > -#endif Hmm...was this shortcoming actually fixed or does this change bugger up a large number of currently working boards? Haavard _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot