Simon Glass a65d1a06c9 sandbox: Zero the ram buffer on startup ...

At present the RAM buffer is not inited unless it is read from a file,
likely produced by an earlier phase of U-Boot. This causes valgrind
warnings whenever the RAM buffer is used. Correct this by initing it if
needed.

Signed-off-by: Simon Glass <sjg@chromium.org>

2018-12-05 06:01:34 -07:00

..

cpu.c

sandbox: remove stray DEBUG

2018-11-20 19:14:22 -07:00

eth-raw-os.c

sandbox: Use malloc() and free() from os layer

2018-11-26 08:25:37 -05:00

Makefile

SPDX: Convert all of our single license tags to Linux Kernel style

2018-05-07 09:34:12 -04:00

os.c

sandbox: Fix up the debug message for the image filename

2018-12-05 06:01:34 -07:00

sdl.c

sandbox: Enable sound

2018-11-29 09:30:05 -07:00

spl.c

sandbox: Check the filename in jump_to_image_no_args()

2018-12-05 06:01:34 -07:00

start.c

sandbox: Zero the ram buffer on startup

2018-12-05 06:01:34 -07:00

state.c

sandbox: Remove the old memory file later

2018-10-09 04:40:26 -06:00

u-boot-spl.lds

sandbox: Add an option to display of-platdata in SPL

2018-11-26 08:25:35 -05:00

u-boot.lds

Partially revert "efi_loader: Rename sections to allow for implicit data"

2018-08-23 16:17:41 -04:00