On Thu, Nov 22, 2012 at 05:23:03AM -0500, Egbert Eich wrote:
> According the the VESA specs there can be up to 254 EEDID extension blocks.
> Since we may read the EDID (including extensions) in 10 second intervals to
> probe for display hotplugging (at least in cases where no hardware hotplug
> det
Ville Syrj?l? writes:
> On Thu, Nov 22, 2012 at 05:23:03AM -0500, Egbert Eich wrote:
> >
> > - /* if there's no extensions, we're done */
> > + /* if there are no extensions, we're done - don't bother caching */
> >if (block[EDID_EXTENSION_FLAG_OFFSET] == 0)
> >return bloc
Ville Syrj?l? writes:
> On Thu, Nov 22, 2012 at 05:23:03AM -0500, Egbert Eich wrote:
> >
> > - /* if there's no extensions, we're done */
> > + /* if there are no extensions, we're done - don't bother caching */
> >if (block[EDID_EXTENSION_FLAG_OFFSET] == 0)
> >return bloc
On Thu, Nov 22, 2012 at 05:23:03AM -0500, Egbert Eich wrote:
> According the the VESA specs there can be up to 254 EEDID extension blocks.
> Since we may read the EDID (including extensions) in 10 second intervals to
> probe for display hotplugging (at least in cases where no hardware hotplug
> det
According the the VESA specs there can be up to 254 EEDID extension blocks.
Since we may read the EDID (including extensions) in 10 second intervals to
probe for display hotplugging (at least in cases where no hardware hotplug
detection exists) and I2C transfer is rather slow we may end up consumin
According the the VESA specs there can be up to 254 EEDID extension blocks.
Since we may read the EDID (including extensions) in 10 second intervals to
probe for display hotplugging (at least in cases where no hardware hotplug
detection exists) and I2C transfer is rather slow we may end up consumin
