On 01/19/2012 03:37 PM, Somebody in the thread at some point said: > Thanks for all your responses. > We will try it as soon as possible :) > > So this tells me that the build determines which resolution it has, this > can not be changed through any setting. Is this right?
You can try messing with dss kernel commandlines but I dunno you get anywhere good. Fracture in video status reflects fracture in TI approach to how the work is done. There's an upstream effort to get definitive mainline support in, and separately there's customer support based approach from TI that is mainly targeted at Android / Omapzoom. The code quality is best in mainline but support is incomplete, especially about multihead. In OZ and OZ-ish kernels, filter for what goes in is not as aggressive as mainline, enablement is better but basis is always an old release. That means, the old, working 3.0 code diverges from what got into mainline for later releases and can't be brought on easily unless treated as alien code like SGX. Linaro TI LT kernel is trying to be a third approach, while worshipping mainline HEAD above all, so we have recent development basis, we glue on whatever missing pieces we can scavenge from wherever, keeping them up to date with Linus HEAD with to goal of being a highly enabled "fake upstream" with the missing pieces integrated. In your case that boils down to: Jassi added code to come out on HDMI connector at 1080p via EDID on our kernel, AOSP omap 3.0-based kernel doesn't have that support. -Andy -- Andy Green | TI Landing Team Leader Linaro.org │ Open source software for ARM SoCs | Follow Linaro http://facebook.com/pages/Linaro/155974581091106 - http://twitter.com/#!/linaroorg - http://linaro.org/linaro-blog _______________________________________________ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
