From: Alexey Fisher <bug-track@fisher-privat.net>
To: intel-gfx@lists.freedesktop.org
Subject: [regression] drm/i915: cleanup per-pipe reg usage
Date: Fri, 11 Feb 2011 21:59:23 +0100 [thread overview]
Message-ID: <1297457963.28522.12.camel@zwerg> (raw)
Hi,
i have regression on asus eeepc 1005, intel 945gm
It is some sort of video noise, skewed looking ... hard do describe.
I'll send a video of it tomorrow (if you need)
intel_stepping
Vendor: 0x8086, Device: 0x27ae, Revision: 0x03 (??)
apt-cache policy xserver-xorg-video-intel
xserver-xorg-video-intel:
Installiert: 2:2.14.0-1ubuntu6
Kandidat: 2:2.14.0-1ubuntu6
commit 9db4a9c7b2a3bd5b4952846bc0c2f58daa80ddd7
Author: Jesse Barnes <jbarnes@virtuousgeek.org>
Date: Mon Feb 7 12:26:52 2011 -0800
drm/i915: cleanup per-pipe reg usage
We had some conversions over to the _PIPE macros, but didn't get
everything. So hide the per-pipe regs with an _ (still used in a
few
places for legacy) and add a few _PIPE based macros, then make sure
everyone uses them.
[update: remove usage of non-existent no-op macro]
[update 2: keep modesetting suspend/resume code, update to new reg
names]
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
[ickle: stylistic cleanups for checkpatch and taste]
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
--
Regards,
Alexey
next reply other threads:[~2011-02-11 20:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-11 20:59 Alexey Fisher [this message]
[not found] ` <1297520176.10989.1.camel@zwerg>
[not found] ` <b9dded$hu5fo8@orsmga002.jf.intel.com>
2011-02-12 21:02 ` [regression] drm/i915: cleanup per-pipe reg usage Alexey Fisher
2011-02-16 18:42 ` Jesse Barnes
2011-02-16 18:57 ` Jesse Barnes
2011-02-17 7:26 ` Alexey Fisher
2011-02-17 18:32 ` Jesse Barnes
2011-02-17 20:54 ` Alexey Fisher
2011-02-17 21:09 ` Jesse Barnes
2011-02-17 21:24 ` Alexey Fisher
2011-02-17 21:26 ` Alexey Fisher
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=1297457963.28522.12.camel@zwerg \
--to=bug-track@fisher-privat.net \
--cc=intel-gfx@lists.freedesktop.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;
as well as URLs for NNTP newsgroup(s).