On 2/4/12, Alan Cox 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 driv
On 2/4/12, Alan Cox 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 driv
> My system boots up, loads drm, loads gma500_gfx, and then my monitor's
> OSD says "Out of Frequency". Pretty much the same behavior with the
> old psb_gfx module and the new gma500_gfx module.
They are all basically the same logic until the most recent release which
at least queries the monitor
I've got a VersaLogic Ocelot (Atom Z530, Menlow) and I've been test
driving the new GMA500 driver w/out much luck. I tried the old
staging driver a few times, and just compiled and tested a checkout
from Linus' tree (d12566). I've got the gma500 driver compiled as a
module, with the optional part
> My system boots up, loads drm, loads gma500_gfx, and then my monitor's
> OSD says "Out of Frequency". Pretty much the same behavior with the
> old psb_gfx module and the new gma500_gfx module.
They are all basically the same logic until the most recent release which
at least queries the monitor
I've got a VersaLogic Ocelot (Atom Z530, Menlow) and I've been test
driving the new GMA500 driver w/out much luck. I tried the old
staging driver a few times, and just compiled and tested a checkout
from Linus' tree (d12566). I've got the gma500 driver compiled as a
module, with the optional part
