From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 63933] Error in r300_set_framebuffer_state if use Dual-Head setup
Date: Fri, 26 Apr 2013 22:29:34 +0000 [thread overview]
Message-ID: <bug-63933-502-dUQwtveoxZ@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-63933-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 885 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=63933
--- Comment #5 from Alex Deucher <agd5f@yahoo.com> ---
(In reply to comment #4)
> (In reply to comment #3)
> > (In reply to comment #2)
> > > Ok, if i use Xinerama (with same resolutions) will exceed hardware limit or
> > > not ?
> >
> > xinerama does not support 3D acceleration.
>
> ok, sorry my stupid question.
>
> if isn't bothered, i've other question, only way for i get 3D
> acceleration(without change resolution) is buy a new hw, or exists another
> way ?
If you want to use 3D effects across a desktop larger than the hw limits of the
GPU, you either need a newer GPU with larger hw limits or someone has to make
major changes to the xserver to allocate separate surfaces for each monitor
rather than a single large surface for all monitors.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1922 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2013-04-26 22:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-25 21:40 [Bug 63933] New: Error in r300_set_framebuffer_state if use Dual-Head setup bugzilla-daemon
2013-04-25 21:47 ` [Bug 63933] " bugzilla-daemon
2013-04-26 21:57 ` bugzilla-daemon
2013-04-26 22:21 ` bugzilla-daemon
2013-04-26 22:25 ` bugzilla-daemon
2013-04-26 22:29 ` bugzilla-daemon [this message]
2013-04-26 22:32 ` bugzilla-daemon
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=bug-63933-502-dUQwtveoxZ@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@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