linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Walrond <andrew@walrond.org>
To: adaplas@pol.net
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Rivafb won't work with DVI connector
Date: Mon, 22 Nov 2004 09:23:05 +0000	[thread overview]
Message-ID: <200411220923.05415.andrew@walrond.org> (raw)
In-Reply-To: <200411220807.23572.adaplas@hotpop.com>

On Monday 22 Nov 2004 00:11, Antonino A. Daplas wrote:
> On Saturday 20 November 2004 23:52, Andrew Walrond wrote:
> > On Friday 19 Nov 2004 22:08, Antonino A. Daplas wrote:
> > > On Friday 19 November 2004 19:37, Andrew Walrond wrote:
> > > > I have a TFT LCD screen (1600x1200) with both D-Sub and DVI inputs,
> > > > and a NV25 [GeForce4 Ti 4600] with same outputs.
>
> Can you try this driver rewrite for nVidia chipsets? I'm planning to add
> this driver because it's getting harder and harder to support newer
> chipsets with the old code.
>
> - based on the most recent Xorg nv driver
> - supports console acceleration via DMA instead of PIO
> - should support all chipsets supported by rivafb except for
>   Riva128 (NV_ARCH_03) and in theory should also support
>   NV_ARCH_30 and NV_ARCH_40 chipsets. I've already added
>   a few pci_ids for these newer chipsets.
>
> The reference file that I based the driver on seems to have better DVI
> support, so hopefully this works.
>
> You have to disable rivafb in your kernel config.  The module name is
> nvidiafb and boot options are very similar to rivafb:
>
> video=nvidiafb:<your options>
>
> This is a preliminary patch, but it should be almost as functional as
> rivafb.
>

Hi Tony,

Some results. I both cases I booted with
 video=nvidia:1600x1200-16@60
on an Iiuama AU4831D 1600x1200 TFT LCD with both dsub and dvi connectors.

Using the dsub connector, everything works fine. From dmesg:

 nvidiafb: nVidia device/chipset 10DE0250
 nvidiafb: nVidia Corporation NV25 [GeForce4 Ti 4600]
   ...can't find one
   ...found one
 nvidiafb: CRTC 0appears to have a CRT attached
 nvidiafb: Using CRT on CRTC 0
 nvidiafb: MTRR set to ON
 Console: switching to colour frame buffer device 200x75
 nvidiafb: PCI nVidia NV25 framebuffer (128MB @ 0xE0000000)

Using the dvi connector, I get lovely shade of green filling the whole screen. 
Dmesg is interesting:

 nvidiafb: nVidia device/chipset 10DE0250
 nvidiafb: nVidia Corporation NV25 [GeForce4 Ti 4600]
   ...can't find one
   ...can't find one
 nvidiafb: CRTC 1 is currently programmed for DFP
 nvidiafb: Using DFP on CRTC 1
 Panel size is 1024 x 768
 nvidiafb: MTRR set to ON
 warning: many lost ticks.
 Your time source seems to be instable or some driver is hogging interupts
 rip default_idle+0x20/0x30
 Console: switching to colour frame buffer device 200x75
 nvidiafb: PCI nVidia NV25 framebuffer (128MB @ 0xE0000000)

Notice in particular
 - "some driver hogging interrupts"
 - "Panel size is 1024x768" (should be 1600x1200)

I'll try to boot on dvi without and module parameters and report back shortly.

Anything else I can do to help, let me know.

Andrew


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

  reply	other threads:[~2004-11-22  9:23 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 [this message]
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
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=200411220923.05415.andrew@walrond.org \
    --to=andrew@walrond.org \
    --cc=adaplas@pol.net \
    --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).