diff options
| author | Bin Meng <bmeng.cn@gmail.com> | 2016-10-09 04:14:17 -0700 |
|---|---|---|
| committer | Bin Meng <bmeng.cn@gmail.com> | 2016-10-12 10:58:23 +0800 |
| commit | 3968398eb2d974b4840d7210d8503d7cbd8f4c48 (patch) | |
| tree | ef831d690e3431618eec471b37dbbe37b806bd9a /arch/x86/dts/chromebook_link.dts | |
| parent | 13b2bfce5104ad7b4243025554a354a2000b352b (diff) | |
| download | u-boot-3968398eb2d974b4840d7210d8503d7cbd8f4c48.tar.gz u-boot-3968398eb2d974b4840d7210d8503d7cbd8f4c48.tar.xz u-boot-3968398eb2d974b4840d7210d8503d7cbd8f4c48.zip | |
dm: video: Don't do anything in alloc_fb() when plat->size is zero
With DM VESA driver on x86 boards, plat->base/size/align are all
zeroes and starting address passed to alloc_fb() happens to be 1MB
aligned, so this routine does not trigger any issue. On QEMU with
U-Boot as coreboot payload, the starting address is within 1MB
range (eg: 0x7fb0000), thus causes failure in video_post_bind().
Actually if plat->size is zero, it makes no sense to do anything
in this routine. Add such check there.
Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'arch/x86/dts/chromebook_link.dts')
0 files changed, 0 insertions, 0 deletions