From: Guido Guenther <agx@sigxcpu.org>
To: Andrew Walrond <andrew@walrond.org>
Cc: linux-fbdev-devel@lists.sourceforge.net,
"Antonino A. Daplas" <adaplas@hotpop.com>,
Wolfram Quester <wolfi@mittelerde.physik.uni-konstanz.de>
Subject: Re: rivafb: finally enable NV30 based pbooks/cleanup probe errors
Date: Fri, 19 Nov 2004 14:33:14 +0100 [thread overview]
Message-ID: <20041119133314.GG6409@bogon.ms20.nix> (raw)
In-Reply-To: <200411191224.00921.andrew@walrond.org>
On Fri, Nov 19, 2004 at 12:24:00PM +0000, Andrew Walrond wrote:
> On Friday 19 Nov 2004 11:09, Antonino A. Daplas wrote:
> >
> > Anyway, I'm planning to write another driver for nvidia, based on xorg
> > sources, as nvidiafb. The rivafb uses programmed io, whereas the newer
> > chipsets uses DMA, and without docs, that's the only way we can support
> > newer chipsets (use X sources).
> >
>
> How come xorg have more information than you? Is their (open source) driver
> provided by NVidia?
The driver was originally written by Mark Vojkovich who had access to
the documentation.
-- Guido
-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
prev parent reply other threads:[~2004-11-19 13:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-18 16:49 rivafb: finally enable NV30 based pbooks/cleanup probe errors Guido Guenther
2004-11-18 23:19 ` Antonino A. Daplas
2004-11-19 8:09 ` Guido Guenther
2004-11-19 9:20 ` Andrew Walrond
2004-11-19 11:09 ` Antonino A. Daplas
2004-11-20 0:42 ` Guido Guenther
2004-11-19 11:09 ` Antonino A. Daplas
2004-11-19 11:58 ` Guido Guenther
2004-11-19 12:24 ` Andrew Walrond
2004-11-19 13:33 ` Guido Guenther [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=20041119133314.GG6409@bogon.ms20.nix \
--to=agx@sigxcpu.org \
--cc=adaplas@hotpop.com \
--cc=andrew@walrond.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=wolfi@mittelerde.physik.uni-konstanz.de \
/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).