linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Antonino A. Daplas" <adaplas@hotpop.com>
To: linux-fbdev-devel@lists.sourceforge.net,
	Andrew Walrond <andrew@walrond.org>
Subject: Re: Rivafb won't work with DVI connector
Date: Wed, 24 Nov 2004 01:07:11 +0800	[thread overview]
Message-ID: <200411240107.13362.adaplas@hotpop.com> (raw)
In-Reply-To: <200411231608.19517.andrew@walrond.org>

[-- Attachment #1: Type: text/plain, Size: 851 bytes --]

On Wednesday 24 November 2004 00:08, Andrew Walrond wrote:
> On Tuesday 23 Nov 2004 15:18, Antonino A. Daplas wrote:
> > On Tuesday 23 November 2004 23:09, Andrew Walrond wrote:
> > > On Tuesday 23 Nov 2004 14:28, Antonino A. Daplas wrote:
> > > > Okay, try the attached patch.
> > >
> > > Ok, booting on dsub without params now results in a good 1024x768
> > > (128x48) console and boots cleanly. (Note this was a 1600x1200
> > > (200xwhatever) before the patch, which is the preferred, native
> > > resolution of the screen.)
>
> Actually, I think this is die to having both dsub and dvi attached during
> that test. Just dsub boots to 1600x1200 as before
>

Okay, I think I this should fix the dvi misdetection, and I think it should
also fix the preferred timing of 1600x1200 even if both dsub and dvi are
attached.  Try the attached patch.

Tony

[-- Attachment #2: nvidiafb2-inc3.diff --]
[-- Type: text/x-diff, Size: 1571 bytes --]

diff -Nru a/drivers/video/nvidia/nv_setup.c b/drivers/video/nvidia/nv_setup.c
--- a/drivers/video/nvidia/nv_setup.c	2004-11-23 22:19:56 +08:00
+++ b/drivers/video/nvidia/nv_setup.c	2004-11-24 01:02:51 +08:00
@@ -400,7 +400,7 @@
 			printk("nvidiafb: EDID found from BUS1\n");
 			monA = &monitorA;
 			fb_edid_to_monspecs(edidA, monA);
-			FlatPanel = (monA->input == FB_DISP_DDI) ? 1 : 0;
+			FlatPanel = (monA->input & FB_DISP_DDI) ? 1 : 0;
 			
 			/* NV4 doesn't support FlatPanels */
 			if((par->Chipset & 0x0fff) <= 0x0020)
@@ -531,9 +531,9 @@
 			printk("nvidiafb: CRTC 1 is currently programmed for "
 			       "TV\n");
 		} else if (monA) {
-			FlatPanel = (monA->input == FB_DISP_DDI) ? 1 : 0;
+			FlatPanel = (monA->input & FB_DISP_DDI) ? 1 : 0;
 		} else if (monB) {
-			FlatPanel = (monB->input == FB_DISP_DDI) ? 1 : 0;
+			FlatPanel = (monB->input & FB_DISP_DDI) ? 1 : 0;
 		}
 		
 		if(par->FlatPanel == -1) {
@@ -574,9 +574,9 @@
 		}
 		
 		if (monA) {
-			if (((monA->input == FB_DISP_DDI) &&
+			if (((monA->input & FB_DISP_DDI) &&
 			     par->FlatPanel) ||
-			    ((monA->input != FB_DISP_DDI) &&
+			    ((!(monA->input & FB_DISP_DDI)) &&
 			     !par->FlatPanel)) {
 				if (monB) {
 					fb_destroy_modedb(monB->modedb);
@@ -589,9 +589,9 @@
 		}
 		
 		if (monB) {
-			if (((monB->input == FB_DISP_DDI) &&
+			if (((monB->input & FB_DISP_DDI) &&
 			     !par->FlatPanel) ||
-			    ((monB->input != FB_DISP_DDI) &&
+			    ((!(monB->input & FB_DISP_DDI)) &&
 			     par->FlatPanel)) {
 				fb_destroy_modedb(monB->modedb);
 				monB = NULL;

  reply	other threads:[~2004-11-23 17:07 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-19 11:37 Rivafb won't work with DVI connector Andrew Walrond
2004-11-19 22:08 ` Antonino A. Daplas
2004-11-20 15:52   ` Andrew Walrond
2004-11-22  0:11     ` Antonino A. Daplas
2004-11-22  9:23       ` Andrew Walrond
2004-11-22  9:43         ` Andrew Walrond
2004-11-22 22:13           ` Antonino A. Daplas
2004-11-22 23:47             ` Andrew Walrond
2004-11-22 23:54               ` Andrew Walrond
2004-11-23  1:50               ` Antonino A. Daplas
2004-11-23 12:32                 ` Andrew Walrond
2004-11-23 14:28                   ` Antonino A. Daplas
2004-11-23 15:09                     ` Andrew Walrond
2004-11-23 15:18                       ` Antonino A. Daplas
2004-11-23 16:08                         ` Andrew Walrond
2004-11-23 17:07                           ` Antonino A. Daplas [this message]
2004-11-23 18:01                             ` Andrew Walrond
2004-11-23 18:26                               ` Antonino A. Daplas
2004-11-23 19:00                                 ` Andrew Walrond
2004-11-23 19:07                                   ` Andrew Walrond
2004-11-23 19:23                                 ` Andrew Walrond
2004-11-23 19:59                                   ` Geert Uytterhoeven
2004-11-23 20:53                                     ` Andrew Walrond
2004-11-23 22:44                                       ` Antonino A. Daplas
2004-11-23 23:59                                         ` Andrew Walrond
2004-11-24 22:38                                         ` Andrew Walrond
2004-11-23 20:21                                   ` Chad Daelhousen
2004-11-24 23:01                                 ` Andrew Walrond
  -- strict thread matches above, loose matches on Subject: below --
2004-11-25  0:07 Antonino A. Daplas
2004-11-25 15:27 ` Andrew Walrond
2004-11-25 21:16   ` Antonino A. Daplas
2004-11-26 14:09   ` Antonino A. Daplas
2004-11-27 12:40     ` Andrew Walrond
2004-11-27 18:29       ` Michel Dänzer
2004-11-27 22:35         ` Andrew Walrond
2004-11-27 22:43       ` Antonino A. Daplas

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=200411240107.13362.adaplas@hotpop.com \
    --to=adaplas@hotpop.com \
    --cc=andrew@walrond.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    /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).