diff options
author | Tom Wai-Hong Tam <waihong@chromium.org> | 2011-08-12 18:27:31 +0800 |
---|---|---|
committer | Simon Glass <sjg@chromium.org> | 2011-08-29 10:59:30 -0700 |
commit | 2efaa58738ab9c907aeb8ade8b535b9aaa9c4a64 (patch) | |
tree | 6b0d6b2bd8cffb65d7f7e33d8d6abf3558d1b19b /net | |
parent | 59838c878aa585589c758d49ae011a3fa50c36ca (diff) |
CHROMIUM: Assign the frame buffer address as FDT one instead of u-boot one.
The framebuffer address should be specified in the device tree and not u-boot
assigned. This FDT value should be the same as the one defined in Linux kernel;
otherwise, it causes screen flicker. The FDT value overrides the framebuffer
allocated at the top of memory by board_init_f().
If the framebuffer address is not defined in the FDT, falls back to use the
address allocated by board_init_f().
BUG=chrome-os-partner:5338
TEST=build without error and boot Chrome OS on Aebl, see the screen not
corrupted and splash screen showed.
Change-Id: Ia6a996d127d74d6084900814d2c934fb95518e23
Reviewed-on: http://gerrit.chromium.org/gerrit/5877
Reviewed-by: Tom Wai-Hong Tam <waihong@chromium.org>
Tested-by: Tom Wai-Hong Tam <waihong@chromium.org>
Diffstat (limited to 'net')
0 files changed, 0 insertions, 0 deletions