From: Francisco Jerez <currojerez-sGOZH3hwPm2sTnJN9+BGXg@public.gmane.org>
To: Patrick Baggett
<baggett.patrick-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: Older Nvidia hardware driver state
Date: Mon, 14 Nov 2011 12:48:50 +0100 [thread overview]
Message-ID: <877h32c4bh.fsf@riseup.net> (raw)
In-Reply-To: <CAEk2StnHM+Gr_GZkg=RJP5ooJR02YJFMmxQXq8rqc8SeCDC_rg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> (Patrick Baggett's message of "Sun, 13 Nov 2011 19:34:35 -0600")
[-- Attachment #1.1.1: Type: text/plain, Size: 1513 bytes --]
Patrick Baggett <baggett.patrick-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
> Hi all!
>
Hi,
> I read that the older Nvidia hardware (maybe < GF8) is in a different driver
> and no longer maintained. Is that the case?
Yes and no. If you're talking about the 3d drivers, I've done pretty
much nothing as maintainer of the nv04-nv20 driver in the last few
months, and the same goes for the nv30-nv40 driver, mostly because of
lack of time of the people involved. If you're talking about 2d, the
situation is considerably better.
And of course there's hardware-specific code different for each card
generation, but IMHO calling them different separate drivers would be
wrong, there's a significant amount of shared code.
> I have a GeForce 4000 MX that I'm trying to get to work on
> debian/sparc64, which I admit is a bit of longshot, but I was
> wondering how much effort it would take to even get the driver to
> build, and then to function. I'm very proficient in C but don't have
> much experience writing drivers.
>
It *should* be functional to a large extent, it's just that it might
have bred a few bugs while we weren't looking :). In any case your help
is very welcome if you know how to program, feel free to address any
questions to this mailing list or to the #nouveau IRC channel.
> Patrick Baggett
> _______________________________________________
> Nouveau mailing list
> Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
> http://lists.freedesktop.org/mailman/listinfo/nouveau
[-- Attachment #1.2: Type: application/pgp-signature, Size: 229 bytes --]
[-- Attachment #2: Type: text/plain, Size: 181 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
prev parent reply other threads:[~2011-11-14 11:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-14 1:34 Older Nvidia hardware driver state Patrick Baggett
[not found] ` <CAEk2StnHM+Gr_GZkg=RJP5ooJR02YJFMmxQXq8rqc8SeCDC_rg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-11-14 11:48 ` Francisco Jerez [this message]
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=877h32c4bh.fsf@riseup.net \
--to=currojerez-sgozh3hwpm2stnjn9+bgxg@public.gmane.org \
--cc=baggett.patrick-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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 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.