On Mon, 2011-06-20 at 16:16 +0530, Tushar Behera wrote: > Currently display support for omap2 is selected by default and > it gets built for all the configurations. > > Instead of it being a built-in feature, it's compilation should > depend on the config option CONFIG_FB_OMAP2. No, I don't think so. omap2 directory contains vram, vrfb and omapdss, all of which can be used without omapfb driver. vram and vrfb can be even used without omapdss driver. Is this patch fixing some real problem? Tomi -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
