Patrik Jakobsson wrote:
> I've sent in a patch for this:
> http://lists.freedesktop.org/archives/dri-devel/2013-February/034990.html
> it is slightly different to what I proposed earlier. Would be nice if you
> could
> give it a spin and report back.
Seems to be ok.
Tested-by:
Patrik Jakobsson wrote:
> I've sent in a patch for this:
> http://lists.freedesktop.org/archives/dri-devel/2013-February/034990.html
> it is slightly different to what I proposed earlier. Would be nice if you
> could
> give it a spin and report back.
Seems to be ok.
Tested-by:
__
On Mon, Feb 11, 2013 at 11:18 PM, Patrik Jakobsson
wrote:
> On Mon, Feb 11, 2013 at 2:15 PM, "David M?ller (ELSOFT AG)"
> wrote:
>> Hi Patrik
>>
>> Patrik Jakobsson wrote:
>>> The value of VCO_MIN comes from the Intel PRM for similar GPUs.
>>>
>>> Instead of changing VCO_MIN, could you try settin
On Mon, Feb 11, 2013 at 11:18 PM, Patrik Jakobsson
wrote:
> On Mon, Feb 11, 2013 at 2:15 PM, "David Müller (ELSOFT AG)"
> wrote:
>> Hi Patrik
>>
>> Patrik Jakobsson wrote:
>>> The value of VCO_MIN comes from the Intel PRM for similar GPUs.
>>>
>>> Instead of changing VCO_MIN, could you try settin
On Mon, Feb 11, 2013 at 2:15 PM, "David M?ller (ELSOFT AG)"
wrote:
> Hi Patrik
>
> Patrik Jakobsson wrote:
>> The value of VCO_MIN comes from the Intel PRM for similar GPUs.
>>
>> Instead of changing VCO_MIN, could you try setting N_MIN=1, N_MAX=6 and
>> M1_MAX=22? I'll test it on my own hardware
On Mon, Feb 11, 2013 at 2:15 PM, "David Müller (ELSOFT AG)"
wrote:
> Hi Patrik
>
> Patrik Jakobsson wrote:
>> The value of VCO_MIN comes from the Intel PRM for similar GPUs.
>>
>> Instead of changing VCO_MIN, could you try setting N_MIN=1, N_MAX=6 and
>> M1_MAX=22? I'll test it on my own hardware
Hi Patrik
Patrik Jakobsson wrote:
> The value of VCO_MIN comes from the Intel PRM for similar GPUs.
>
> Instead of changing VCO_MIN, could you try setting N_MIN=1, N_MAX=6 and
> M1_MAX=22? I'll test it on my own hardware tomorrow.
Thanks for your suggestion.
With "N_MIN=1, N_MAX=6 and M1_MAX=22
Hi Patrik
Patrik Jakobsson wrote:
> The value of VCO_MIN comes from the Intel PRM for similar GPUs.
>
> Instead of changing VCO_MIN, could you try setting N_MIN=1, N_MAX=6 and
> M1_MAX=22? I'll test it on my own hardware tomorrow.
Thanks for your suggestion.
With "N_MIN=1, N_MAX=6 and M1_MAX=22
On Fri, Feb 8, 2013 at 2:51 PM, "David M?ller (ELSOFT AG)"
wrote:
>
> Hello
>
> I have a problem using a 1024x768 Eizo Monitor attached by DVI-D to a
> system with GMA500 based graphics and running under Linux-3.7.
>
> As soon as the GMA500 driver is taking over control, the refresh
> rate raises
On Fri, Feb 8, 2013 at 2:51 PM, "David Müller (ELSOFT AG)"
wrote:
>
> Hello
>
> I have a problem using a 1024x768 Eizo Monitor attached by DVI-D to a
> system with GMA500 based graphics and running under Linux-3.7.
>
> As soon as the GMA500 driver is taking over control, the refresh
> rate raises
Hello
I have a problem using a 1024x768 Eizo Monitor attached by DVI-D to a
system with GMA500 based graphics and running under Linux-3.7.
As soon as the GMA500 driver is taking over control, the refresh
rate raises to 64.5Hz and the monitor reports a "signal error".
For me i looks like the GMA5
Hello
I have a problem using a 1024x768 Eizo Monitor attached by DVI-D to a
system with GMA500 based graphics and running under Linux-3.7.
As soon as the GMA500 driver is taking over control, the refresh
rate raises to 64.5Hz and the monitor reports a "signal error".
For me i looks like the GMA5
12 matches
Mail list logo