From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 13866] New: RandR 1.2 gives Xvideo tearing
Date: Sun, 30 Dec 2007 11:19:08 -0800 (PST) [thread overview]
Message-ID: <bug-13866-8800@http.bugs.freedesktop.org/> (raw)
http://bugs.freedesktop.org/show_bug.cgi?id=13866
Summary: RandR 1.2 gives Xvideo tearing
Product: xorg
Version: 7.3
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
ReportedBy: drzeus-bugzilla-p3sGCRWkH8CeZLLa646FqQ@public.gmane.org
QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
Enabling RandR 1.2 gives me a lot of video tearing on my Geforce 7300 GT. It
doesn't matter if two outputs are enabled or not, simply using the new RandR
1.2 stuff produces the problem.
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2007-12-30 19:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-30 19:19 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-13866-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2008-01-03 20:57 ` [Bug 13866] nouveau gives Xvideo tearing bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-01-03 22:57 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-01-04 6:32 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-01-05 9:55 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-01-05 11:27 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-01-05 19:30 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-01-20 14:32 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-01-20 16:17 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-01-20 18:08 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-01-20 18:40 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
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-13866-8800@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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 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.