How to setup DRI with radeonhd
I've just created a wiki page, which hopefully(!) resembles the steps to
get working DRI on radeonhd:
http://wiki.x.org/wiki/radeonhd:DRI
It's still in its infant state, so please correct the page, and if
unsure, send a comment to the mailing list.
CU all
Matthias
--
Matthias Hopf
Matthias> I've just created a wiki page, which hopefully(!) resembles Matthias> the steps to get working DRI on radeonhd: Thanks for doing this Matthias! Matthias> http://wiki.x.org/wiki/radeonhd:DRI Matthias> It's still in its infant state, so please correct the page, Matthias> and if unsure, send a comment to the mailing list. I've gone through and make one needed fix, and then some possibly gratuitious changes to the proceedure. 1. The URL for the xorg/xserver part needed to be fixed, you had .../xorg/server which didn't work. 2. I put in a bit more about putting all these into their own build area, and then to use the build/ directory inside each area as well. 3. When building the linux-core part of DRM, I suggest building only the radeon module to be installed as a kernel module. Why build all the rest when we don't need them? I'm still working my way through all the steps and seeing how it works out. I doubt I'll get done tonight unfortunately. John -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org
"John" == John Stoffel
writes:
= 1.1 xcmiscproto xextproto >= 7.0.3 xproto >= 7.0.13 xtrans scrnsaverproto >= 1.1 bigreqsproto resourceproto fontsproto inputproto = 1.9.99.1 kbproto >= 1.0.3 videoproto compositeproto >= 0.4
John> I'm still working my way through all the steps and seeing how it John> works out. I doubt I'll get done tonight unfortunately. Ok, I've just hit a stumbling block, while following the updated instructions I edited earlier tonight. While building on an x86_64 Hardy Heron system, I get the following during my autogen.sh --prefix=/usr of the xserver stuff: checking for XSERVERCFLAGS... configure: error: Package requirements (randrproto >= 1.2 renderproto >= 0.9.3 fixesproto >= 4.0 damageproto trapproto resourceproto xineramaproto evieproto xkbfile xfont xau fontenc pixman-1 >= 0.9.5 xdmcp) were not met: Requested 'xextproto >= 7.0.3' but version of XExtProto is 7.0.2 Requested 'xproto >= 7.0.13' but version of Xproto is 7.0.11 Requested 'inputproto >= 1.9.99.1' but version of InputProto is 1.4.2 Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix. Alternatively, you may set the environment variables XSERVERCFLAGS_CFLAGS and XSERVERCFLAGS_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. So are there other libraries I need to install or pull down? I've got the feeling I'm going to be an *extremely* bleeding edge setup here. G'night all, I'll check back in tomorrow and see what's up. Thanks, John -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org
On May 28, 08 23:55:08 -0400, John Stoffel wrote:
Ok, I've just hit a stumbling block, while following the updated instructions I edited earlier tonight. While building on an x86_64 Hardy Heron system, I get the following during my autogen.sh --prefix=/usr of the xserver stuff:
I updated the wiki page quite a bit - you might want go over the page once more and clear up some things I haven't explained enough. I really had to reduce the building instructions again, there are too many subsystems to be built now.
Requested 'xextproto >= 7.0.3' but version of XExtProto is 7.0.2 Requested 'xproto >= 7.0.13' but version of Xproto is 7.0.11 Requested 'inputproto >= 1.9.99.1' but version of InputProto is 1.4.2
Added those. Also added input drivers (which I simply forgot), also added pixman because that is often a problem as well.
So are there other libraries I need to install or pull down? I've got the feeling I'm going to be an *extremely* bleeding edge setup here.
We'll see :-]
Yes, you are, definitely.
Seriously, I'm not sure what the typical preconditions are. I only added
those that I ran into myself. Then again, I'm not exactly a typical user
;-)
CU
Matthias
--
Matthias Hopf
Matthias Hopf wrote:
Requested 'xextproto >= 7.0.3' but version of XExtProto is 7.0.2 Requested 'xproto >= 7.0.13' but version of Xproto is 7.0.11 Requested 'inputproto >= 1.9.99.1' but version of InputProto is 1.4.2
Added those. Also added input drivers (which I simply forgot), also added pixman because that is often a problem as well.
The updated instructions on the wiki helped quite a bit, but even after installing the newer prototypes and libraries I'm left with this: Requested 'inputproto >= 1.9.99.1' but version of InputProto is 1.4.3 I looked around on ftp://ftp.freedesktop.org/pub/individual/proto/ and inputproto-1.4.3.tar.bz2 seems to be the latest released version (dated 3/06/2008). gitweb shows that the version on inputproto was bumped to 1.9.99.1 in the last day or so. Installing inputproto from git seemed to work (at least as far as allowing xserver to configure successfully). Regards, Dave -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org
"David" == David Morrison
writes:
David> Matthias Hopf wrote:
Requested 'xextproto >= 7.0.3' but version of XExtProto is 7.0.2 Requested 'xproto >= 7.0.13' but version of Xproto is 7.0.11 Requested 'inputproto >= 1.9.99.1' but version of InputProto is 1.4.2
Added those. Also added input drivers (which I simply forgot), also added pixman because that is often a problem as well.
David> The updated instructions on the wiki helped quite a bit, but even after David> installing the newer prototypes and libraries I'm left with this: David> Requested 'inputproto >= 1.9.99.1' but version of InputProto is 1.4.3 David> I looked around on David> ftp://ftp.freedesktop.org/pub/individual/proto/ and David> inputproto-1.4.3.tar.bz2 seems to be the latest released David> version (dated 3/06/2008). gitweb shows that the version on David> inputproto was bumped to 1.9.99.1 in the last day or so. David> Installing inputproto from git seemed to work (at least as far David> as allowing xserver to configure successfully). Details? Or could you update the wiki please? I'm at work, so I don't have the dedicated time to hack my home system. :] John -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org
John Stoffel wrote:
Details? Or could you update the wiki please? I'm at work, so I don't have the dedicated time to hack my home system. :]
OK - % git clone git://anongit.freedesktop.org/git/xorg/proto/inputproto % cd inputproto % ./autogen.sh --prefix=/usr % make % make install Regards, Dave -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org
On May 29, 08 09:42:58 -0400, John Stoffel wrote:
Details? Or could you update the wiki please? I'm at work, so I don't have the dedicated time to hack my home system. :]
Sure. Updated the wiki accordingly.
I expect that we will run into additional issues, though.
Matthias
--
Matthias Hopf
On May 28, 08 23:18:44 -0400, John Stoffel wrote:
Matthias> It's still in its infant state, so please correct the page, Matthias> and if unsure, send a comment to the mailing list.
I've gone through and make one needed fix, and then some possibly gratuitious changes to the proceedure.
Thanks. I'll redo some of the stuff, though, because I had to add more and more repros to be built, so it really doesn't make sense to hand hold every step. Exchanging drivers and the Xserver is for advanced users anyway.
2. I put in a bit more about putting all these into their own build area, and then to use the build/ directory inside each area as well.
Using build dirs is something for developers or really advanced users (there are subtle side effects sometimes, and sometimes it's just not possible like with kernel modules or Mesa). Also your description missed the 'build' directory, so the commands weren't working.
3. When building the linux-core part of DRM, I suggest building only the radeon module to be installed as a kernel module. Why build all the rest when we don't need them?
Rational thought. For drm this doesn't really matter, because it builds
fast, but for Mesa, this is actually *very* important. Adding this.
I'm also adding the additional prerequisits you ran into.
CU
Matthias
--
Matthias Hopf
participants (3)
-
David Morrison
-
John Stoffel
-
Matthias Hopf