VIDEO: better document the correct use of CONFIG_FB_ADDR

Signed-off-by: Wolfgang Denk <wd@denx.de> cc: Anatolij Gustschin <agust@denx.de>

VIDEO: better document the correct use of CONFIG_FB_ADDR
Signed-off-by: Wolfgang Denk <wd@denx.de> cc: Anatolij Gustschin <agust@denx.de>
Wolfgang Denk · Anatolij Gustschin
1 parent dad631ccf7
Showing 1 changed file with 7 additions and 4 deletions Side-by-side Diff
README
@@ -2714,10 +2714,13 @@
 		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.
...	...	@@ -2714,10 +2714,13 @@
2714	2714	CONFIG_FB_ADDR
2715	2715
2716	2716	Define CONFIG_FB_ADDR if you want to use specific
2717		- address for frame buffer.
2718		- Then system will reserve the frame buffer address to
2719		- defined address instead of lcd_setmem (this function
2720		- grabs the memory for frame buffer by panel's size).
	2717	+ address for frame buffer. This is typically the case
	2718	+ when using a graphics controller has separate video
	2719	+ memory. U-Boot will then place the frame buffer at
	2720	+ the given address instead of dynamically reserving it
	2721	+ in system RAM by calling lcd_setmem(), which grabs
	2722	+ the memory for the frame buffer depending on the
	2723	+ configured panel size.
2721	2724
2722	2725	Please see board_init_f function.
2723	2726