On 09/28/2012 12:18 PM, Robert Nelson wrote:
Ah, so looking at the config, ARCH switched to omapdrm... It kinda
works in v3.5.x, but i'd wait till a few more releases...
So, based on that config, they have both "CONFIG_FB_OMAP2" and
"CONFIG_DRM_OMAP" enabled.. That's a no-no...
CONFIG_DRM_OMAP
http://cateee.net/lkddb/web-lkddb/DRM_OMAP.html
depends on: ( CONFIG_DRM&& ! CONFIG_CONFIG_FB_OMAP2 )&& (
CONFIG_ARCH_OMAP2PLUS )
Option 1: Stay with omapfb
CONFIG_FB_OMAP2=m -> CONFIG_FB_OMAP2=y
disable: CONFIG_DRM_OMAP
Option 2: Go Experimental route with omapdrm
CONFIG_DRM_OMAP=m
CONFIG_DRM_OMAP_NUM_CRTCS=1
disable: CONFIG_FB_OMAP2
> Attached are config.gz from running system and gz'd complete dmesg output
> (hope attachments are OK on the list).
>
> There's another 3.5.4 build scheduled on the panda build farm this
> afternoon. If you have any config modification suggestions, they'd be very
> gratefully received.
Also, if your running that config on pre-es (omap4430) panda's..
CONFIG_OMAP4_ERRATA_I688=y& CONFIG_ARCH_HAS_BARRIERS=y
and save your self some debugging time...;)
Regards,
-- Robert Nelson http://www.rcn-ee.com/
Thanks Robert!
I passed along to the distro devs to include in today's build.
I'll follow up once I'm running the new version...
johnea
--
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
