On Sun, Feb 16, 2014 at 2:15 PM, Rafa? Mi?ecki wrote:
> 2014-02-16 19:55 GMT+01:00 Ilia Mirkin :
>> On Sun, Feb 16, 2014 at 10:17 AM, Rafa? Mi?ecki wrote:
>>> 2014-02-11 11:41 GMT+01:00 Ilia Mirkin :
(b) bisect. you can (almost) definitely restrict the bisect to
2014-02-16 19:55 GMT+01:00 Ilia Mirkin :
> On Sun, Feb 16, 2014 at 10:17 AM, Rafa? Mi?ecki wrote:
>> 2014-02-11 11:41 GMT+01:00 Ilia Mirkin :
>>> (b) bisect. you can (almost) definitely restrict the bisect to
>>> drivers/gpu/drm/nouveau. if you have additional computational power, i
>>> would
2014-02-11 11:41 GMT+01:00 Ilia Mirkin :
> (b) bisect. you can (almost) definitely restrict the bisect to
> drivers/gpu/drm/nouveau. if you have additional computational power, i
> would recommend looking into distcc for speeding up the compiles. it
> may be interesting to also try 3.6.x since 3.7
2014-02-11 11:41 GMT+01:00 Ilia Mirkin :
> On Mon, Feb 10, 2014 at 3:05 PM, Rafa? Mi?ecki wrote:
>> 2014-02-10 20:06 GMT+01:00 Ilia Mirkin :
>>> There was also an issue with libdrm_nouveau for pre-nv50 chips, when
>>> compiled with gcc-4.8 some time back... fixed in... 2.4.48 or so?
>>
>> I use
On Sun, Feb 16, 2014 at 10:17 AM, Rafa? Mi?ecki wrote:
> 2014-02-11 11:41 GMT+01:00 Ilia Mirkin :
>> (b) bisect. you can (almost) definitely restrict the bisect to
>> drivers/gpu/drm/nouveau. if you have additional computational power, i
>> would recommend looking into distcc for speeding up the
2014-02-11 11:41 GMT+01:00 Ilia Mirkin :
> (b) bisect. you can (almost) definitely restrict the bisect to
> drivers/gpu/drm/nouveau. if you have additional computational power, i
> would recommend looking into distcc for speeding up the compiles. it
> may be interesting to also try 3.6.x since 3.7
2014-02-10 20:06 GMT+01:00 Ilia Mirkin :
> Lastly, it may be worth trying 3.11.x and 3.12.x to get a better
> handle on when problems happened. The commits you cite are in the
> middle of releases, and may have various badness associated with them
> (e.g. 3.12-rc had a later-disabled MSI
On Tue, Feb 11, 2014 at 6:09 AM, Rafa? Mi?ecki wrote:
> 2014-02-11 11:41 GMT+01:00 Ilia Mirkin :
>> (b) bisect. you can (almost) definitely restrict the bisect to
>> drivers/gpu/drm/nouveau. if you have additional computational power, i
>> would recommend looking into distcc for speeding up the
On Mon, Feb 10, 2014 at 3:05 PM, Rafa? Mi?ecki wrote:
> 2014-02-10 20:06 GMT+01:00 Ilia Mirkin :
>> There was also an issue with libdrm_nouveau for pre-nv50 chips, when
>> compiled with gcc-4.8 some time back... fixed in... 2.4.48 or so?
>
> I use openSUSE 12.2 (x86_64) which provides gcc 4.7.1
2014-02-10 20:06 GMT+01:00 Ilia Mirkin :
> On Mon, Feb 10, 2014 at 10:12 AM, Rafa? Mi?ecki wrote:
>> 2014-02-09 23:12 GMT+01:00 Ilia Mirkin :
>>> On Sun, Feb 9, 2014 at 5:08 PM, Rafa? Mi?ecki wrote:
Last week I've switched from my old & good 3.4.63 to 3.14-rc1 and
noticed nasty display
2014-02-09 23:12 GMT+01:00 Ilia Mirkin :
> On Sun, Feb 9, 2014 at 5:08 PM, Rafa? Mi?ecki wrote:
>> Last week I've switched from my old & good 3.4.63 to 3.14-rc1 and
>> noticed nasty display corruptions when using nouveau. It seems that
>> changing parts of the screen are appearing for a fraction
On Mon, Feb 10, 2014 at 10:12 AM, Rafa? Mi?ecki wrote:
> 2014-02-09 23:12 GMT+01:00 Ilia Mirkin :
>> On Sun, Feb 9, 2014 at 5:08 PM, Rafa? Mi?ecki wrote:
>>> Last week I've switched from my old & good 3.4.63 to 3.14-rc1 and
>>> noticed nasty display corruptions when using nouveau. It seems that
Hi guys,
Last week I've switched from my old & good 3.4.63 to 3.14-rc1 and
noticed nasty display corruptions when using nouveau. It seems that
changing parts of the screen are appearing for a fraction of second in
random places. I've recorded this behavior:
On Sun, Feb 9, 2014 at 5:08 PM, Rafa? Mi?ecki wrote:
> Hi guys,
>
> Last week I've switched from my old & good 3.4.63 to 3.14-rc1 and
> noticed nasty display corruptions when using nouveau. It seems that
> changing parts of the screen are appearing for a fraction of second in
> random places.
14 matches
Mail list logo
