| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20080930142207.72d5edaa@hskinnemo-gx745.norway.atmel.com> Date: Tue, 30 Sep 2008 14:22:07 +0200 From: Haavard Skinnemoen <haavard.skinnemoen@...el.com> To: "Leon Woestenberg" <leon.woestenberg@...il.com> Cc: linux-mtd@...ts.infradead.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH] mtd: AT49BV6416 has swapped erase regions "Leon Woestenberg" <leon.woestenberg@...il.com> wrote: > Haavard, > > On Tue, Sep 30, 2008 at 1:55 PM, Haavard Skinnemoen > <haavard.skinnemoen@...el.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. > 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists