From: "René Herman" <rene.herman@gmail.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG 2.6.38] drm/i915: rampant video-corruption on Intel 865G
Date: Thu, 24 Mar 2011 09:19:18 +0100 [thread overview]
Message-ID: <4D8AFE86.7050803@gmail.com> (raw)
In-Reply-To: <849307$c4rj51@azsmga001.ch.intel.com>
On 03/24/2011 09:00 AM, Chris Wilson wrote:
>> I do suppose that one [ the kernel one] should fix things even
>> without the X11 changes? If not, I'd still have a problem until
>> those have made their way through the distributions...
>
> No, the bugs are distinct, but very similar in appearance, and both
> updates are required.
That won't do then, will it? Kernel 2.6.38 then requires a new and not
even released user space whereas 2.6.37 works fine. I suppose the fix
will from the kernel side then need to be reverting to .37 behaviour, at
least on the affected hardware? (855 and 865 at least).
Regards,
Rene
prev parent reply other threads:[~2011-03-24 8:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-23 21:30 [BUG 2.6.38] drm/i915: rampant video-corruption on Intel 865G René Herman
[not found] ` <849307$c4qsv5@azsmga001.ch.intel.com>
2011-03-24 7:56 ` René Herman
[not found] ` <849307$c4rj51@azsmga001.ch.intel.com>
2011-03-24 8:19 ` René Herman [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D8AFE86.7050803@gmail.com \
--to=rene.herman@gmail.com \
--cc=chris@chris-wilson.co.uk \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox