Protect splashimage from improperly aligned addresses
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest0 of 2 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 2 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [U-Boot] [PATCH 0/2] Protect splashimage from improperly aligned addresses
Hi Tom,
Quoted 16 lines · Tom Rini
Quoted 14 lines · Nikita Kiryanov
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
Quoted 6 lines
Quoted 3 lines
Nikita Kiryanov (2):
lcd: implement a callback for splashimage
cm_t35: prevent splashimage from being set to a bad valueTo 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.
Signature · 2 lines
Regards, Nikita.