From: Michel Dänzer <michdaen@iiic.ethz.ch>
To: "William H. Schultz" <whschult@uncc.edu>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: XFree86 4.0 Generic VGA
Date: Thu, 23 Mar 2000 21:52:29 +0100 [thread overview]
Message-ID: <38DA840D.D6BE805E@iiic.ethz.ch> (raw)
In-Reply-To: 38DA24A5.D3FC9BA9@uncc.edu
"William H. Schultz" wrote:
> > Have you tried the tdfx driver? IIRC Kostas has it working.
> >
> Forgive me for being slow, but where can I get it? I was
> under the impression that the tdfx driver, unlike most of
> the others, was compiled straight into the kernel. I know
> I haven't gotten that to work.
No, it's part of the XFree86 4.0 sources. Do you mean the DRM kernel module
(for DRI hardware accelerated 3D) for it? You don't need that for 2D, but if
you'd like it to work, contact Kostas.
> XFree86 -configure definately doesn't work. I know I should
> be paying more attention to the errors, but I get fewer by
> running xf86configure instead of the other way.
What does it do?
Michel
--
Software is like sex; it's better when it's free
-- Linus Torvalds
______________________________________________________________________________
Michel Dänzer /// mdaenzer@earthling.net
__ /// AmigaOS/Linux(Debian/PPC)
Student of computer science at the \\\/// Team *AMIGA* ICQ #: 5675698
Swiss Federal Institute of Technology \\\/ AUGS member #163 IRC: CoOpER
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-03-23 20:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200003210600.AAA05535@lists.linuxppc.org>
2000-03-23 5:43 ` XFree86 4.0 Generic VGA William H. Schultz
[not found] ` <38D9D30C.478C4E55@iiic.ethz.ch>
[not found] ` <38DA24A5.D3FC9BA9@uncc.edu>
2000-03-23 20:52 ` Michel Dänzer [this message]
[not found] <B5002664.69%whschult@uncc.edu>
2000-03-24 9:06 ` Michael Schmitz
2000-03-24 9:19 ` Kostas Gewrgiou
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=38DA840D.D6BE805E@iiic.ethz.ch \
--to=michdaen@iiic.ethz.ch \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=whschult@uncc.edu \
/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).