From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH 2/5] drm/i915: preserve swizzle settings if necessary v3
Date: Wed, 11 Jun 2014 08:41:13 -0700 [thread overview]
Message-ID: <20140611084113.4c1089af@jbarnes-desktop> (raw)
In-Reply-To: <CAKMK7uGjCQVcyq_y0hzKUEN-rpcn08KcyANjFR7fcSix4ZLHxA@mail.gmail.com>
On Wed, 11 Jun 2014 17:39:29 +0200
Daniel Vetter <daniel@ffwll.ch> wrote:
> On Wed, Jun 11, 2014 at 5:13 PM, Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
> >> - If you have a machine which uses tiled framebuffers and enables
> >> swizzling in the BIOS your code will a) drop the swizzle setup in
> >> gem_init_hw, breaking resume b) not set the swizzle settings correctly
> >> in swizzle_detect, breaking swap in/out and pwrite/pread. Not sure such
> >> a machine exists, but still.
> >
> > This would affect krh's MBA, which is why I wanted testing here...
> > anyway I'll spin a new one and ask krh to test again.
>
> Hm, I've thought the issue with the MBA is that it used tiled fbs, but
> non-swizzled. And then a mess ensued when we've enabled it. But yeah,
> unfortunately with the new logic we need to retest :(
Ah yeah I think you're right, either way, need more testing.
Maybe we should have just gone with the first patch to never enable
swizzling based on Art's assertion that it didn't matter.
--
Jesse Barnes, Intel Open Source Technology Center
next prev parent reply other threads:[~2014-06-11 15:41 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-05 18:24 [PATCH 1/5] drm/i915: preserve SSC if previously set v2 Jesse Barnes
2014-06-05 18:24 ` [PATCH 2/5] drm/i915: preserve swizzle settings if necessary v3 Jesse Barnes
2014-06-10 14:02 ` Daniel Vetter
2014-06-10 17:27 ` Jesse Barnes
2014-06-10 19:33 ` Daniel Vetter
2014-06-10 19:45 ` Jesse Barnes
2014-06-11 9:23 ` Daniel Vetter
2014-06-11 15:13 ` Jesse Barnes
2014-06-11 15:39 ` Daniel Vetter
2014-06-11 15:41 ` Jesse Barnes [this message]
2014-06-27 16:15 ` Steve Aarnio
2014-07-07 9:03 ` [Intel-gfx] " Daniel Vetter
2014-06-05 18:24 ` [PATCH 3/5] drm: add drm_mode_same_size function Jesse Barnes
2014-06-05 18:24 ` [PATCH 4/5] drm/i915: use current mode if the size matches the preferred mode Jesse Barnes
2014-06-10 14:05 ` [Intel-gfx] " Daniel Vetter
2014-06-10 17:29 ` Jesse Barnes
2014-06-05 18:24 ` [PATCH 5/5] drm/i915: enable fastboot by default Jesse Barnes
2014-06-06 11:12 ` Jani Nikula
2014-06-10 14:10 ` Daniel Vetter
2014-06-10 14:07 ` [Intel-gfx] " Daniel Vetter
2014-06-10 17:31 ` Jesse Barnes
2014-06-10 18:01 ` Stéphane Marchesin
2014-06-10 18:42 ` [Intel-gfx] " Jesse Barnes
2014-06-11 9:30 ` Daniel Vetter
2014-06-06 11:04 ` [PATCH 1/5] drm/i915: preserve SSC if previously set v2 Jani Nikula
2014-06-06 11:06 ` Chris Wilson
2014-06-10 14:00 ` [Intel-gfx] " Daniel Vetter
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=20140611084113.4c1089af@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--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