From: Benjamin Herrenschmidt <bh40@calva.net>
To: Steven Hanley <sjh@wibble.net>,
Linux PPC Dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: agpgart? or how to use dri?
Date: Thu, 1 Feb 2001 12:29:39 +0100 [thread overview]
Message-ID: <19341227050123.16989@mailhost.mipsys.com> (raw)
In-Reply-To: <20010201184806.A5957@chiru.svana.org>
>
>Trying to get the dri stuff to build (this is an X 4.02 tree checked out
>from the branch Gareth announced two days ago)
>
>The problem seems to be the kernel module. When I have agpgart enabled in
>the kernel the r128 kernel module builds, when I dont have apgart enabled
>only the tdfx module will build, this is doing a make in the
>xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel/ directory in the
>X source
>
>The problem here of course is agpgart wont build on ppc
>
>in /usr/src/linux/drivers/char/agp/agpgart_be.c there is a flush_dcache
>function defined, and it is only defined for alpha, ia64 and i386.
>
>I dont know what the culprit is, but I assume thee dri stuff can be built
>without agpgart on ppc or some scuh, this kernel tree is the 2.4.1 bk
>rsynced about half an hour ago.
>
>Any hints on getting the dri kernel module to build to the extent that it
>can be insmod'd and used?
>
The current agpgart driver won't work on PPC, the Apple AGP host bridge
is not supported.
The new DRI support announced by Gareth is using the PCI GART which
doesn't need the AGP capabilities. Don't enable either AGP or DRI in your
kernel, and build the kernel r128 DRM module from XFree sources. You need
to use the CVS branch posted earlier by Gareth. I slightly hacked my own
to build since I lack the glide libs necessary for the 3dfx stuff to compile.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-02-01 11:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-01 7:48 agpgart? or how to use dri? Steven Hanley
2001-02-01 11:29 ` Benjamin Herrenschmidt [this message]
2001-02-01 22:53 ` Steven Hanley
2001-02-01 23:25 ` Michel Dänzer
2001-02-02 0:02 ` Benjamin Herrenschmidt
2001-02-02 15:27 ` 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=19341227050123.16989@mailhost.mipsys.com \
--to=bh40@calva.net \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=sjh@wibble.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).