From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 22317] New: Interlace does not work with Geforce 6200 / NV44a
Date: Tue, 16 Jun 2009 08:55:55 -0700 (PDT) [thread overview]
Message-ID: <bug-22317-8800@http.bugs.freedesktop.org/> (raw)
http://bugs.freedesktop.org/show_bug.cgi?id=22317
Summary: Interlace does not work with Geforce 6200 / NV44a
Product: xorg
Version: git
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
ReportedBy: a.j.buxton-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
Created an attachment (id=26856)
--> (http://bugs.freedesktop.org/attachment.cgi?id=26856)
Photo of the display failing to run interlace mode properly.
Using this modeline:
ModeLine "768x576pali" 14.750 768 789 858 944 576 600 605 625 -hsync
-vsync interlace
interlace mode fails; only the top half of each field is drawn, causing a
result which looks like the attached picture.
I was able to make it work by patching nv_crtc.c, and doubling the values in
mode->CrtcV* in the function nv_crtc_mode_set()
Additionally, when using this modeline and the double height patch:
ModeLine "720x576pali" 13.500 720 722 786 864 576 581 586 625 -hsync
-vsync interlace
there is a vertical black bar down the middle of the picture.
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2009-06-16 15:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-16 15:55 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-22317-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2009-06-16 16:00 ` [Bug 22317] Interlace does not work with Geforce 6200 / NV44a bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-06-16 16:07 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-06-16 16:58 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-06-18 16:46 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-06-18 17:09 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-06-21 11:22 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-06-26 16:10 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-06-26 17:04 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-18 18:09 ` 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-22317-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.