Hi Tom,
On 02/27/2013 10:06 PM, Tom Rini wrote:
On Sun, Feb 24, 2013 at 06:19:21PM +0200, Nikita Kiryanov wrote:
As discussed in the links below, one needs to be careful about choosing an address for a splash image BMP file when working on architectures that can't handle unaligned memory accesses. A bad address may lead to a bricked board, and the safe addresses are not obvious due to the internal structure of BMP files.
This patchset documents the problem and implements an optional callback that prevents the environment variable from being set to a bad value.
Finally, it turns this protection on for cm_t35.
http://lists.denx.de/pipermail/u-boot/2013-January/144666.html http://lists.denx.de/pipermail/u-boot/2013-February/146021.html
Nikita Kiryanov (2): lcd: implement a callback for splashimage cm_t35: prevent splashimage from being set to a bad value
To be clear, this series is the only part required of all of the various ones that have been posted about splash images?
Yes. It replaces "Create an API for safely accessing BMP header fields", and I commented on the "Add splash screen for CM-T35" V3 series to point out which patches should be dropped from it.