From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Marcin Owsiany <marcin@owsiany.pl>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: Can recent i915 support more than 8192x8192 screen?
Date: Fri, 20 Jul 2018 14:35:52 -0700 [thread overview]
Message-ID: <20180720213552.GO16907@intel.com> (raw)
In-Reply-To: <CAFsGsxK8wVFy5TkAfKjzhM1eP9zB2-05km8ObShhTD7Hsk9-tQ@mail.gmail.com>
On Fri, Jul 20, 2018 at 11:01:38PM +0200, Marcin Owsiany wrote:
> 2018-07-20 22:22 GMT+02:00 Rodrigo Vivi <[1]rodrigo.vivi@intel.com>:
>
> On Thu, Jul 19, 2018 at 11:31:19PM +0200, Marcin Owsiany wrote:
> > $ xrandr --fb 8960x2880
> > xrandr: screen cannot be larger than 8192x8192 (desired size
> > 8960x2880)
>
> I'm afraid that it is a hardware limitation that you won't be able
> to
> workaround.
>
> Interestingly, just yesterday Ville Syrjälä posted a patch series for
> "GTT remapping for display",
> which concludes in this hopeful-looking patch called "Bump gen4+ fb
> size limits to 32kx32k:
> [2]https://lists.freedesktop.org/archives/intel-gfx/2018-July/171922.ht
> ml
> Which looks oddly similar to what I encountered on reddit.
> I don't pretend to even understand what "GTT remapping" is, but maybe
> there is hope after all? ;-)
cool... I have that series on my todo list here to take a look but I
haven't yet. I'm glad to hear that there's hope.
>
> But a log would be interesting anyway... (both dmesg and xorg.0.log)
>
> I'll try digging up that patched kernel sometime and get the messages.
>
> > My current workaround is to pretend that the displays are
> arranged
> > vertically, but even after a few months I'm sometimes having
> trouble
> > remembering that I need to move mouse cursor UP when I want to
> go to
> > LEFT display :-)
> This is another bug.... And probably the right (only?) fixable fr
> your
> setup.
>
> Why is this a bug? What I meant is that two wide monitors fit
> within 8192x8192
> when using xrandr's --above but not --left-of, so I'm just using the
> former despite
> having a different physical arrangement.
> Marcin
> PS: Sorry for the initial double-post, I thought my first email was
> blackholed
np... I approved it as soon as I saw it there.
list is open, but I have to filter the non-subscribed emails because of
so many spams...
> while I was not yet subscribed to the list.
>
> References
>
> 1. mailto:rodrigo.vivi@intel.com
> 2. https://lists.freedesktop.org/archives/intel-gfx/2018-July/171922.html
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-07-20 21:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-19 21:31 Can recent i915 support more than 8192x8192 screen? Marcin Owsiany
2018-07-20 20:22 ` Rodrigo Vivi
2018-07-20 21:01 ` Marcin Owsiany
2018-07-20 21:35 ` Rodrigo Vivi [this message]
2018-07-21 7:43 ` Marcin Owsiany
2018-07-24 18:37 ` Rodrigo Vivi
2018-07-24 20:23 ` Marcin Owsiany
2018-07-24 20:31 ` Rodrigo Vivi
2018-07-21 8:20 ` Chris Wilson
2018-07-21 9:20 ` Marcin Owsiany
2018-07-21 9:22 ` Marcin Owsiany
-- strict thread matches above, loose matches on Subject: below --
2018-07-20 5:21 Marcin Owsiany
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=20180720213552.GO16907@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=marcin@owsiany.pl \
/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).