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: Mon, 22 Nov 2004 08:11:52 +0800 [thread overview]
Message-ID: <200411220807.23572.adaplas@hotpop.com> (raw)
In-Reply-To: <200411201552.53919.andrew@walrond.org>
[-- Attachment #1: Type: text/plain, Size: 1804 bytes --]
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.
Tony
drivers/video/Kconfig | 7
drivers/video/Makefile | 4
drivers/video/nvidia/Makefile | 11
drivers/video/nvidia/nv_accel.c | 342 ++++++++
drivers/video/nvidia/nv_dma.h | 180 ++++
drivers/video/nvidia/nv_local.h | 91 ++
drivers/video/nvidia/nv_proto.h | 59 +
drivers/video/nvidia/nv_setup.c | 626 +++++++++++++++
drivers/video/nvidia/nv_type.h | 171 ++++
drivers/video/nvidia/nvidia-i2c.c | 229 +++++
drivers/video/nvidia/nvidia.c | 1221 ++++++++++++++++++++++++++++++
drivers/video/nvidia/nvidia_hw.c | 1509 ++++++++++++++++++++++++++++++++++++++
include/linux/pci_ids.h | 49 +
[-- Attachment #2: nvidiafb.diff.gz --]
[-- Type: application/x-gzip, Size: 30961 bytes --]
next prev parent reply other threads:[~2004-11-22 0:50 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 [this message]
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
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=200411220807.23572.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 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.