On Wed, 2011-09-21 at 11:29 -0400, Alex Deucher wrote:
> On Wed, Sep 21, 2011 at 10:12 AM, Adam Jackson wrote:
> > If hardware does require composite sync for a mode, it's out of luck
> > with current drivers, since none support that. Just skip the mode
> > instead, there'll be others in the EDID
On Wed, Sep 21, 2011 at 10:12 AM, Adam Jackson wrote:
> If hardware does require composite sync for a mode, it's out of luck
> with current drivers, since none support that. ?Just skip the mode
> instead, there'll be others in the EDID. ?(Unless there's not, in which
> case, failing is correct any
If hardware does require composite sync for a mode, it's out of luck
with current drivers, since none support that. Just skip the mode
instead, there'll be others in the EDID. (Unless there's not, in which
case, failing is correct anyway.)
While we're at it, hush the other mode support messages
On Wed, 2011-09-21 at 11:29 -0400, Alex Deucher wrote:
> On Wed, Sep 21, 2011 at 10:12 AM, Adam Jackson wrote:
> > If hardware does require composite sync for a mode, it's out of luck
> > with current drivers, since none support that. Just skip the mode
> > instead, there'll be others in the EDID
On Wed, Sep 21, 2011 at 10:12 AM, Adam Jackson wrote:
> If hardware does require composite sync for a mode, it's out of luck
> with current drivers, since none support that. Just skip the mode
> instead, there'll be others in the EDID. (Unless there's not, in which
> case, failing is correct any
If hardware does require composite sync for a mode, it's out of luck
with current drivers, since none support that. Just skip the mode
instead, there'll be others in the EDID. (Unless there's not, in which
case, failing is correct anyway.)
While we're at it, hush the other mode support messages
