Hi Tomi,Sebastien, On Tue, Mar 15, 2011 at 9:36 AM, Tomi Valkeinen <tomi.valkeinen@xxxxxx> wrote: > On Mon, 2011-03-14 at 05:37 -0500, Jan, Sebastien wrote: >> Hi Tomi, >> >> On Thu, Mar 10, 2011 at 2:44 PM, Tomi Valkeinen <tomi.valkeinen@xxxxxx> 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 > > Yes, I get those every time I enable or disable the HDMI output. That > shouldn't cause any problems, but it's something that needs to be fixed > at some point. > >> 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)? > > Currently the resolution has to be configured by the user manually. I > haven't tried, but I think giving the resolution with boot parameters > should also work. Mythri, have you tried that? > You could configure the timings later on with the sysfs ( set_timings ) or HDMI driver would pick the best timing (as suggested by standard) , but yes framebuffer would have picked the timing on probe so it will not update. > I don't think it is possible for the omapdss, panel or omapfb drivers to > configure the resolution automatically, except at boot time. After we > have booted up, there may be users for the framebuffer and changing it > "secretly" would cause problems. > > I think the best way here is that the HDMI/omapdss driver gives hotplug > event, which is conveyed through omapfb to an userspace application. > This application can then query the available resolutions via some > mechanism, and select one of those. > >> 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). > > Thanks. I'll also set up a "test" branch in DSS2 tree shortly, to which > I'll add DVI and HDMI patches for easier testing. > > Tomi > Thanks and regards, Mythri. -- 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
