From: Chris Wilson <chris@chris-wilson.co.uk>
Cc: David Airlie <airlied@linux.ie>,
intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Alex Tu <alex.tu@canonical.com>
Subject: Re: [PATCH] drm/i915: Increase max texture to 16k for gen9+
Date: Thu, 07 Dec 2017 11:11:27 +0000 [thread overview]
Message-ID: <151264508723.25422.2847732124413259330@mail.alporthouse.com> (raw)
In-Reply-To: <20171207092600.3727-1-alex.tu@canonical.com>
Quoting Alex Tu (2017-12-07 09:26:00)
> Rrefer to another patch [1] on mesa to extend width/height to 16384.
> For issue :
> - https://bugs.freedesktop.org/show_bug.cgi?id=102508
> - LP: #1714178 Triple monitor display failed with Dell Dock (HiDPI)
>
> [1] https://patchwork.freedesktop.org/patch/124918/
>
> Signed-off-by: Alex Tu <alex.tu@canonical.com>
For -intel, I just used RandR to split the fb into per-crtc-pixmaps.
However, Kristian has suggested another approach where we carve
per-crtc-pixmaps/-fb out of the global frontbuffer, which allows us to
completely get around the stride limits of scanout and have no
synchronisation penalty. We still have to create new per-crtc-fb for a
flip, just like with RandR but we can avoid the extra blit.
How one feeds such details through gbm into -modesetting, I have no
idea.
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-12-07 11:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-07 9:26 [PATCH] drm/i915: Increase max texture to 16k for gen9+ Alex Tu
2017-12-07 9:26 ` Alex Tu
2017-12-07 9:32 ` [Intel-gfx] " Chris Wilson
2017-12-07 10:09 ` Alex Tu
2017-12-07 11:03 ` [Intel-gfx] " Daniel Vetter
2017-12-07 11:03 ` Daniel Vetter
2017-12-07 11:11 ` Chris Wilson [this message]
2017-12-07 11:59 ` ✓ Fi.CI.BAT: success for " Patchwork
2017-12-07 13:25 ` [PATCH] " Joonas Lahtinen
2017-12-07 13:25 ` Joonas Lahtinen
2017-12-07 15:32 ` [Intel-gfx] " Ville Syrjälä
2017-12-08 3:24 ` Alex Tu
2017-12-07 16:16 ` ✓ Fi.CI.IGT: success for " Patchwork
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=151264508723.25422.2847732124413259330@mail.alporthouse.com \
--to=chris@chris-wilson.co.uk \
--cc=airlied@linux.ie \
--cc=alex.tu@canonical.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rodrigo.vivi@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.