From: "Paul Richards" <greytek@lycos.com>
To: linux-kernel@vger.kernel.org
Subject: [PATCH] 2.4.19 rivafb updates
Date: Mon, 11 Nov 2002 08:05:58 -0500 [thread overview]
Message-ID: <EPBOCLHMEDKLABAA@mailcity.com> (raw)
This patch provides the ability to work with LCDs, bug fixes to cleanup code, Mac support, and support for more nvidia cards. The Mac code was added from a patch Ani Joshi sent me.
The core of the riva framebuffer driver lies in riva_hw.c, a file from the xfree86 source tree. The original riva_hw.c in 2.4.19 is dated 2/2000, I have updated this file from xfree86's cvs and made the necessary changes to the other source and header files and so the flatpanel code will work properly. Since the riva_hw.c with flatpanel support from xfree86's cvs has not reached an official stable release, this would obviously make this patch experimental. However, the feedback from the xfree86 cvs driver has been good and I've carefully "ported" all the necessary changes over.
Its been tested with DirectFB demo programs called df_stress and df_window on a Pentium3/GeForce2MX with a regular CRT monitor and with a LCD flatpanel that works off a DVI connection. Unless your on a Mac or a notebook with a chipset that works specifically with LCDs like the GeForce2Go, you will most likely have to pass flatpanel=1 to the module when its loading because there is no x86 code yet that looks for DVI flatpanels. There looks to be some code for twinview but I have not had any success with this on my box with xfree86 cvs driver or this new riva framebuffer module. LCDs that use analog connections and hookup to the standard VGA card connections should not need to pass flatpanel=1, this is for digital connections only.
Below is a link to the patch. I have not pasted it because I'm not sure if it will be accepted in the 2.4 branch. I'm also worried that a few of the entries I added in include/linux/pci_ids.h might be to long for some versions of gcc.
i.e. #define PCI_DEVICE_ID_NVIDIA_GEFORCE4_420_GO_M32 0x0176
/* largest define I added, 40 characters long */
http://rain.prohosting.com/scftpd/rivafb-richards1.diff.gz
Paul F. Richards
__________________________________________________________
Outgrown your current e-mail service? Get 25MB Storage, POP3 Access,
Advanced Spam protection with LYCOS MAIL PLUS.
http://login.mail.lycos.com/brandPage.shtml?pageId=plus&ref=lmtplus
next reply other threads:[~2002-11-11 12:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-11 13:05 Paul Richards [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-03 15:06 [PATCH] 2.4.19 rivafb updates Rob Shortt
2002-12-22 1:08 Paul Richards
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=EPBOCLHMEDKLABAA@mailcity.com \
--to=greytek@lycos.com \
--cc=linux-kernel@vger.kernel.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 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).