Tomi Valkeinen 09a8c45cbb OMAPFB: remove warning when trying to alloc at certain paddress ... omapfb gives a WARN_ONCE if a predefined physical address is given for allocating the framebuffer memory, as this is not currently supported. However, the same warning happens if omapfb fails to allocate memory during runtime, as when the allocation has failed, omapfb tries to re-allocate the old memory with the physical address of the old memory area. Remove the warning from omapfb_alloc_fbmem, as it serves no purpose on the failure case above, and move it to omapfb_parse_vram_param, so that we only warn if physical address is given via omapfb module parameters. Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>		2012-12-07 16:55:03 +02:00
..
displays	OMAPDSS: Add terminating entry for picodlp_i2c_id table	2012-11-30 10:54:41 +02:00
dss	OMAPDSS: Use only "omapdss_dss" platform device to get context lost count	2012-11-29 12:48:49 +02:00
omapfb	OMAPFB: remove warning when trying to alloc at certain paddress	2012-12-07 16:55:03 +02:00
Kconfig	OMAP: remove vram allocator	2012-11-13 09:52:41 +02:00
Makefile	OMAP: remove vram allocator	2012-11-13 09:52:41 +02:00
vrfb.c	OMAPDSS: VRFB: add omap_vrfb_supported()	2012-10-17 12:17:18 +03:00