summaryrefslogtreecommitdiffstats
path: root/include/configs/tegra124-common.h
diff options
context:
space:
mode:
authorMartin Pietryka <martin.pietryka@chello.at>2016-04-27 21:39:16 +0200
committerAnatolij Gustschin <agust@denx.de>2016-04-28 16:51:17 +0200
commit3d47b2d741683023de05f08f9adb4bd25c189c46 (patch)
treea1abb79c3ae6b061711e39a97ce1da196afe88b0 /include/configs/tegra124-common.h
parent7d045170ac1bf512ed148e97432b7a8d772943e9 (diff)
downloadtalos-obmc-uboot-3d47b2d741683023de05f08f9adb4bd25c189c46.tar.gz
talos-obmc-uboot-3d47b2d741683023de05f08f9adb4bd25c189c46.zip
drivers/video/am335x-fb: Properly point framebuffer behind palette
The DMA was outputting the palette on the screen because the base for the DMA was not after the palette. In addition to that, the ceiling was also too high, this led that the output on the screen was shifted. NOTE: According to the TRM, even in 16/24bit mode a palette is required in the first 32 bytes of the framebuffer. See also: https://e2e.ti.com/support/arm/sitara_arm/f/791/p/234967/834483#834483 "In this mode, the LCDC will assume all information is data and thus you need to ensure that the DMA points to the first pixel of data and not the first entry in the frame buffer which is the beginning of the 512 byte palette." Signed-off-by: Martin Pietryka <martin.pietryka@chello.at> Reviewed-by: Hannes Schmelzer <oe5hpm@oevsv.at> Tested-by: Hannes Schmelzer <oe5hpm@oevsv.at>
Diffstat (limited to 'include/configs/tegra124-common.h')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud