[Libdlo] [PATCH] Fix displaylink-mod with 2.6.32

[Andrew Kephart]

It would be useful to see the EDID that the monitor reports, too.  If
the reported physical dimensions of the monitor are off (or just larger
than 60x37cm), fb_find_best_display() will get confused and fall back on
the first modedb entry with detailed timing.

-andrew

On Thu, 2010-12-09 at 15:57 -0800, Bernie Thompson wrote:
> Hi Jonathan,
> 
> On Thu, Dec 9, 2010 at 3:39 PM, Jonathan McDowell <noodles at earth.li> wrote:
> > 1680x1050 is 1764000 pixels, so should fit in the 2080000 limit?
> 
> Yes, this is a bug.  I'll look into how it could happen (and why it
> hasn't been something run across before).
> 
> Udlfb is not rejecting the 1680x1050 mode, it's noted as valid .. yet
> it's not getting chosen by the fbdev function fb_find_best_display()
> that we call.  Can you "uname -a" to tell us what kernel version
> you're on?
> 
> This should be something we can fix.  We'll get this on the list with
> the other todos (including andrew's patch from today, the blanking
> enhancement triggered by Alexander's questions, and some cleanups
> requested by the fbdev area owner to move this driver from staging
> into mainline fbdev) ... hope to get to them soon.  Patches always
> very welcome.
> 
> Thank you!
> Bernie
> http://plugable.com/
> _______________________________________________
> Libdlo mailing list
> Libdlo at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/libdlo