From: Oded Shimon <ods15@ods15.dyndns.org>
To: linux-kernel@vger.kernel.org
Subject: Re: RivaFB and GeForce FX
Date: Fri, 4 Mar 2005 01:03:05 +0200 [thread overview]
Message-ID: <200503040103.05479.ods15@ods15.dyndns.org> (raw)
In-Reply-To: <1109890416.6974.12.camel@host-172-19-5-120.sns.york.ac.uk>
On Friday 04 March 2005 00:53, Alan Jenkins wrote:
> Having a GeForce FX 5200 which I expected to work under rivafb (kernel
> version 2.6.11), I found the attached message on google groups.
>
> I know it is a little later now, but would you think about getting the
> work you've done committed?
>
> I recognise that updating the driver to work with more recent kernels
> would involve a reasonable amount of work. I don't need the driver
> personally (although it would be nice). I wouldn't be able to take
> advantage of TV out either, but if you can get the code into the kernel
> then more people are likely to look at it.
>
> If you're not going to do anything, could you send me the latest
> version? I don't promise to do anything but as a student I should have
> the time to do so. Actuall skill is another matter :)
Wow, it's been ages.. I eventually stopped caring about this patch because i
realized with my skills TV out would be utterly impossible, which was very
important for me.. So for now I am STILL using VesaFB and the binary nvidia X
driver...
The patch I did prepare were a few strategic copy pastes from the X "nv"
driver which "works" (without TV out) for Geforce FX... I hardly understand
at all what I have done (hardware, just ain't my thing :).
You're free to have the patch though.. I'd advise cleaning it up though, there
is still some debugging stuff in there...
Also, this is actually a common trait for Any rivafb output, the cursor is
horribly broken.. I had a hack in the patch to fix this, but this probably
not welcome for the official driver...
- ods15
next parent reply other threads:[~2005-03-03 23:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1109890416.6974.12.camel@host-172-19-5-120.sns.york.ac.uk>
2005-03-03 23:03 ` Oded Shimon [this message]
2005-03-03 23:03 ` Oded Shimon
2005-03-05 11:53 Alan Jenkins
[not found] ` <f470889705030505089a4d8df@mail.gmail.com>
2005-03-05 15:57 ` Alan Jenkins
[not found] ` <1110043216.6780.14.camel@host-172-19-5-120.sns.york.ac.uk>
2005-03-05 21:14 ` Alan Jenkins
-- strict thread matches above, loose matches on Subject: below --
2004-11-24 21:47 Oded Shimon
2004-11-27 22:01 ` Lee Revell
2004-11-27 22:43 ` Oded Shimon
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=200503040103.05479.ods15@ods15.dyndns.org \
--to=ods15@ods15.dyndns.org \
--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
all inboxes | Powered by JetHome®