From: Lucas Correia Villa Real <lucasvr@gobolinux.org>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: [PATCH] GeForce 5200 on rivafb
Date: Thu, 9 Dec 2004 23:46:18 -0200 [thread overview]
Message-ID: <200412092346.19189.lucasvr@gobolinux.org> (raw)
In-Reply-To: <200412082034.08852.adaplas@hotpop.com>
On Wednesday 08 December 2004 10:34, Antonino A. Daplas wrote:
> On Wednesday 08 December 2004 09:47, Lucas Correia Villa Real wrote:
> > Hi,
> >
> > I was trying to figure out why my GeForce FX 5200 wasn't being recognized
> > by rivafb, when I saw that its ID was not being included by the driver.
> >
> > The following patch (against 2.6.10-rc3) allows it to compile and switch
> > to graphics mode successfully.
>
> We haven't included the id's for NV30 chipsets and newer since the rivafb
> code was made for NV20 and older cards. So we add the id's only if users
> report that it works.
>
> > Just a note: the README file shipped with the NVIDIA driver has a
> > complete list of device ID's. While it's easy to add them all into riva.c
> > and pci_ids.h, I'm not very sure if it's okay to flood them with #defines
> > and by increasing heavily the rivafb_pci_tbl table.
> >
> > Is it ok to do that, or were you waiting to get a feedback from users
> > from those cards first? I can provide a patch to include all the missing
> > cards if there's no problem on doing that.
>
> Actually, I'm planning to replace/supplement the rivafb driver with
> nvidiafb which will support NV30 and NV40 chipsets, including full
> acceleration as well as better display detection. If you don't mind, I'm
> going to attach the patch for testing. Usage is:
>
> video=nvidiafb:<options>
>
> where options are quite similar to rivafb's.
>
> Patch should apply against recent 2.6 kernels, but it might choke on
> include/linux/pci_ids.h. Let me know if it works for you.
Hi Tony,
It worked perfectly fine here (after some adjusts on pci_ids.h):
nvidiafb: nVidia device/chipset 10DE0322
nvidiafb: nVidia Corporation NV34 [GeForce FX 5200]
nvidiafb: CRTC0 found
nvidiafb: CRTC1 not found
nvidiafb: EDID found from BUS1
nvidiafb: CRTC 0 appears to have a CRT attached
nvidiafb: Using CRT on CRTC 0
nvidiafb: MTRR set to ON
Console: switching to colour frame buffer device 90x25
nvidiafb: PCI nVidia NV32 framebuffer (128MB @ 0xF0000000)
Just let me know if you want to test something special on this driver (I'm
already subscribed to the mailing list) -- I volunteer to do that.
Cheers, and thanks for the good work :-)
Lucas
-------------------------------------------------------
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/
next prev parent reply other threads:[~2004-12-10 1:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-08 1:47 [PATCH] GeForce 5200 on rivafb Lucas Correia Villa Real
2004-12-08 12:34 ` Antonino A. Daplas
2004-12-10 1:46 ` Lucas Correia Villa Real [this message]
2004-12-10 20:43 ` Antonino A. Daplas
2004-12-11 3:34 ` Junio C Hamano
2004-12-23 20:48 ` Guido Guenther
-- strict thread matches above, loose matches on Subject: below --
2004-12-11 15:22 Antonino A. Daplas
2004-12-11 18:21 ` Junio C Hamano
2004-12-11 21:11 Antonino A. Daplas
2004-12-12 2:25 ` Junio C Hamano
2004-12-12 10:00 ` Junio C Hamano
2004-12-13 20:52 ` Antonino A. Daplas
2004-12-13 21:47 ` Antonino A. Daplas
2004-12-14 7:51 ` Junio C Hamano
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=200412092346.19189.lucasvr@gobolinux.org \
--to=lucasvr@gobolinux.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).