[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAOQxz3x=FYKJJA8LdDwLMBi0VNDvVO5OD--X2G=jTGqFxUM_gg@mail.gmail.com>
Date: Sat, 4 Feb 2012 22:05:58 -0500
From: Michael Labriola <michael.d.labriola@...il.com>
To: Alan Cox <alan@...rguk.ukuu.org.uk>
Cc: Alan Cox <alan@...ux.intel.com>, David Airlie <airlied@...ux.ie>,
Michael D Labriola <mlabriol@...b.com>,
dri-devel@...ts.freedesktop.org, linux-kernel@...r.kernel.org
Subject: Re: gma500: invalid frequency for monitor
On 2/4/12, Alan Cox <alan@...rguk.ukuu.org.uk> wrote:
*snip*
>> I think my setup is correct, because the vesa frambuffer seems to work
>> correctly. All is well unless I load the gma500_gfx driver and let it
>> set the mode.
>
> What mode is the vesa driver using and if you set the same mode what
> happens ?
The vesa driver was using a resolution of 1280x1024x32... is there a
way to get a whole modeline out of that?
*snip*
>> [ 110.586242] [drm:drm_helper_probe_single_connector_modes],
>> [CONNECTOR:7:LVDS-1] probed modes :
>> [ 110.586274] [drm:drm_mode_debug_printmodeline], Modeline 10:"1280x1024"
>> 40 71500 1280 1328 1440 1688 1024 1025 1028 1072 0x8 0x0
>
> And we probed a 1280x1024 mode with a clock of 71.5 (which might be a bit
> high for the panel ?)
I'm assuming the clock is at fault, yes.
*snip*
>
> Do you have a different monitor around to try and also hand setting lower
> modes ?
Compiling on my home system overnight (these atom boards are pretty
slick, but slow as dirt at compiling the kernel). I've got a
different monitor at home to try, so we'll see what happens. How do I
hand set the mode that gma500 uses?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists