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: <1154682060.31031.184.camel@shinybook.infradead.org>
Date:	Fri, 04 Aug 2006 17:01:00 +0800
From:	David Woodhouse <dwmw2@...radead.org>
To:	Haavard Skinnemoen <hskinnemoen@...el.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] MTD jedec_probe: Recognize Atmel AT49BV6416

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... 

But that's OK -- doesn't the cfi_probe code also read the jedec ID so
that the same fixups work?

-- 
dwmw2

-
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/