Patrick Georgi 5dc87fe470 libpayload/arm64: Mark existing framebuffer as DMAable ... If a framebuffer is already configured by coreboot, libpayload's MMU tables didn't mark its memory DMAable (unlike when libpayload set up its own framebuffer memory). BRANCH=none BUG=chrome-os-partner:52826 TEST=depthcharge's recovery screen is not corrupted anymore on kevin Change-Id: I228a861b3fdcf1298a3cfa0a054214c78ed55e70 Signed-off-by: Patrick Georgi <pgeorgi@chromium.org> Original-Commit-Id: 889e8358a0f2f504abd9910549aa68f3992bb4e8 Original-Change-Id: I7ba79151ccc1eb605f82e1869a74b539a6be5e99 Original-Signed-off-by: Patrick Georgi <patrick@georgi-clan.de> Original-Signed-off-by: Vadim Bendebury <vbendeb@chromium.org> Original-Reviewed-on: https://chromium-review.googlesource.com/341092 Reviewed-on: https://review.coreboot.org/14685 Tested-by: build bot (Jenkins) Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org>		2016-05-09 08:30:56 +02:00
..
arm	libpayload: Move base address, stack and heap size to Kconfig	2016-03-15 20:53:38 +01:00
arm64	libpayload/arm64: Mark existing framebuffer as DMAable	2016-05-09 08:30:56 +02:00
mips	libpayload: Move base address, stack and heap size to Kconfig	2016-03-15 20:53:38 +01:00
x86	libpayload: Move base address, stack and heap size to Kconfig	2016-03-15 20:53:38 +01:00