linux-kernel - Re: [PATCH] MTD jedec_probe: Recognize Atmel AT49BV6416

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20060807170029.3e8c829d@cad-250-152.norway.atmel.com>
Date:	Mon, 7 Aug 2006 17:00:29 +0200
From:	Haavard Skinnemoen <hskinnemoen@...el.com>
To:	David Woodhouse <dwmw2@...radead.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] MTD jedec_probe: Recognize Atmel AT49BV6416

On Fri, 04 Aug 2006 17:06:19 +0800
David Woodhouse <dwmw2@...radead.org> wrote:

> On Fri, 2006-08-04 at 10:52 +0200, Haavard Skinnemoen wrote:
> > It is actually a CFI chip. But I couldn't figure out how to install
> > the fixup in the other patch in the CFI code. The AT49BV6416 chip
> > identifies itself as using the AMD command set, so the fixup must be
> > installed based on the jedec ID... 
> 
> Er, note that the _correct_ answer is to advertise the availability of
> the lock functionality in the CFI 'extended query' information. Did
> the hardware designer screw that up?

I can't find any information about the softlock feature in the PRI
block. However, the AT49BV6416 is obsolete, and the replacement chip,
AT49BV642D, does not power up locked. We'll be using AT49BV642D for new
designs, but in order to support the AT32STK1000 development board, we
need to install a fixup for AT49BV6416.

Another issue is that Atmel uses a different PRI block than AMD. I can
work around this by installing a CFI fixup that converts the Atmel PRI
block to look like an AMD block.

Alternatively, we could define a vendor-independent format with just
the information we need and select different readers/parsers based on
the JEDEC manufacturer ID. Do you know if there are other vendors using
the AMD command set but a different PRI format?

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/