From: Riccardo Magliocchetti <riccardo.magliocchetti@gmail.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Keith Packard <keithp@keithp.com>
Subject: Re: i915 regression with 3.3-rc3+git
Date: Thu, 23 Feb 2012 19:48:59 +0100 [thread overview]
Message-ID: <4F468A1B.9080408@gmail.com> (raw)
In-Reply-To: <20120223084106.4b132532@jbarnes-desktop>
Hello,
Il 23/02/2012 17:41, Jesse Barnes ha scritto:
> On Fri, 17 Feb 2012 21:48:13 +0100
> Riccardo Magliocchetti<riccardo.magliocchetti@gmail.com> wrote:
>
>> Hello,
>>
>> i've upgraded from 3.2.0-rc7 to post 3.3.0-rc3 git
>> 4903062b5485f0e2c286a23b44c9b59d9b017d53, attached you can find dmesg
>> with drm.debug=0xfff
>>
>> This started to appear in logs:
>>
>> [drm:intel_framebuffer_init] *ERROR* unsupported pixel format
>>
>> X is getting a wrong resolution (log attached) and there's a lot of
>> flickering, if i try to play a video the desktop turns black, the other
>> ttys still works fine though.
>>
>>
>
> Can you check the drm-intel-fixes branch at
> git://git.kernel.org/pub/scm/linux/kernel/git/jbarnes/drm-intel.git?
> It has a fix for laod detection that might help.
3.3-rc4 plus these two patches from drm-intel-fixes works great.
4e9bb47bd29e02f2daaa7bdb2a8ddf977bf76f06 [PATCH 2/2] drm/i915: fix a
sprite watermark computation to avoid divide by zero if xpos<0
5ca0c34ae28344b6b4ca3036bc82f89c8db16a59 [PATCH 1/2] drm/i915: fix mode
set on load pipe. (v2)
Thanks!
riccardo
next prev parent reply other threads:[~2012-02-23 18:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-17 20:48 i915 regression with 3.3-rc3+git Riccardo Magliocchetti
2012-02-23 16:41 ` Jesse Barnes
2012-02-23 18:16 ` Sven Joachim
2012-02-23 18:48 ` Riccardo Magliocchetti [this message]
2012-02-23 18:55 ` Jesse Barnes
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=4F468A1B.9080408@gmail.com \
--to=riccardo.magliocchetti@gmail.com \
--cc=jbarnes@virtuousgeek.org \
--cc=keithp@keithp.com \
--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