linux-kernel - Re: [PATCH] Fix Oops with Atmel SPI

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]

Date:	Wed, 14 Apr 2010 11:13:52 -0700
From:	Kevin Cernekee <cernekee@...il.com>
To:	Anders Larsen <al@...rsen.net>
Cc:	Iwo Mergler <iwo@...l-direct.com.au>,
	Artem Bityutskiy <Artem.Bityutskiy@...ia.com>,
	Ian McDonnell <ian@...ghtstareng.com>,
	Nicolas Pitre <nico@...xnic.net>, linux-kernel@...r.kernel.org,
	linux-mtd@...ts.infradead.org,
	Matthias Kaehlcke <matthias@...hlcke.net>,
	David Woodhouse <dwmw2@...radead.org>
Subject: Re: [PATCH] Fix Oops with Atmel SPI

On Wed, Apr 14, 2010 at 12:57 AM, Anders Larsen <al@...rsen.net> wrote:
> the original problem occurs with SPI flashes, which typically have a much
> smaller erase block size (and it only occurs when they are driven by an Atmel
> SoC SPI controller, hence the #ifdefs)

FWIW, the 16MiB Spansion SPI NOR flashes I've been seeing on new
designs have 64KiB or 256KiB (!) eraseblocks.  256KiB eraseblocks are
likely to become even more common as the device capacity increases to
32MiB and beyond.
--
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/