Comment 55 for bug 1849484
Revision history for this message
|
|
#55 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
demo site
(Get the code!)
(In reply to Maxim from comment #12)
> (In reply to Ville Syrjala from comment #11)
> > (In reply to Maxim from comment #10)
> >
> > Nothing particularly interesting in the log. There is a normal looking
> > disable->do nothing for ~26 minutes->re-enable modeset sequence (presuambly
> > the display was just blanked for that period of time?). Also a ton of some
> > ASLE junk but presumably that should be harmless.
> >
> > Given the evidence we have I'd lean towards the DP++ dongle simply being
> > garbage.
>
> Okay, I'm OK with that, as long as it works with 10kHz patch :) Are you
> going to commit it or at least make configurable?
We definitely don't want to put that patch in as is since it'll slow down things for everyone. Making it configurable is an option I suppose. Possibly a better option would be to introduce some kind of fallback mechanism where we try to reduce the i2c bus speed when encountering errors. We might want something like that for DDC/CI as well. Or at least I have one monitor here where the DDC/CI isn't happy with the 100KHz speed either.