summaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorWolfgang Denk <wd@denx.de>2013-01-03 00:43:59 +0000
committerAnatolij Gustschin <agust@denx.de>2013-01-14 20:16:51 +0100
commit44a53b57439dc1f117135b4f8c22d25915096164 (patch)
tree068b3f6c20c3ca73bca806b07d4853265593ad11 /README
parentdad631ccf720b78201e4b026422bb347fec64f5a (diff)
VIDEO: better document the correct use of CONFIG_FB_ADDR
Signed-off-by: Wolfgang Denk <wd@denx.de> cc: Anatolij Gustschin <agust@denx.de>
Diffstat (limited to 'README')
-rw-r--r--README11
1 files changed, 7 insertions, 4 deletions
diff --git a/README b/README
index 8707bf2d7c..a336476237 100644
--- a/README
+++ b/README
@@ -2714,10 +2714,13 @@ FIT uImage format:
CONFIG_FB_ADDR
Define CONFIG_FB_ADDR if you want to use specific
- address for frame buffer.
- Then system will reserve the frame buffer address to
- defined address instead of lcd_setmem (this function
- grabs the memory for frame buffer by panel's size).
+ address for frame buffer. This is typically the case
+ when using a graphics controller has separate video
+ memory. U-Boot will then place the frame buffer at
+ the given address instead of dynamically reserving it
+ in system RAM by calling lcd_setmem(), which grabs
+ the memory for the frame buffer depending on the
+ configured panel size.
Please see board_init_f function.