Hi Tomi, On Thu, Mar 10, 2011 at 2:44 PM, Tomi Valkeinen <[email protected]> wrote: > I think this version is good. It works for me, at least =). > > Any Panda or Blaze owners reading this want to give this a try?
Tested on my pandaboard, with these patches applied on top of your dss2 tree: I get a working display on my DVI or my HDMI screen. => I tested by running the Ubuntu UI. I have a couple of these traces from times to times (seems linked to screen saver enabling/disabling the screen): omapdss DISPC error: timeout waiting for EVSYNC The best screen resolution is properly selected on both of my screens, but the frame-buffer is sized to 640x480. So the display works but the usable surface when going though /dev/fb0 is quite reduced. Is there a way to get the FB sized according to the screen resolution (in the init sequence, it appears that the FBs are allocated before the init of the HDMI)? Fyi, I have also tested with the patches for DVI support and can get both outputs working simultaneously (my tree is here: http://dev.omapzoom.org/?p=sebjan/kernel.git;a=shortlog;h=refs/tags/topic-display-iv1-2.6.38-rc7). -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
