XFree86 DRM, kernel versioning, and make World
ken at kenmoffat.uklinux.net
Fri Apr 11 16:15:16 PDT 2003
On Fri, 11 Apr 2003, Kelledin wrote:
> On Friday 11 April 2003 04:15 pm, Ken Moffat wrote:
> > On Fri, 11 Apr 2003, Dominik Pluemacher wrote:
> > > its possible to compile the appropriate driver in the
> > > DRM-Source-Dir
> > > (xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel/
> > >). Simply issue the command "make -f Makefile.linux" and copy
> > > "radeon.o" to your Linux-Module-Tree.
> > Didn't work for me, I got a large number of references to an
> > undefined symbol in the variants of the mga module (g200,
> > g400, etc) - I didn't write it down, but it seemed to be
> > card-specific prefixes for the same function. FWIW, this is
> > 2.4.21-pre7 with variants of a radeon patch.
> > I'm assuming it's the lack of the built X tree because I
> > built it yesterday with an earlier radeon patch, and the patch
> > only affects the radeon framebuffer code, not the dri module.
> > Building X as I write, I'll know tomorrow whether something
> > else has got screwed!
> Sorry I didn't get to you sooner, else I could have saved you
> some recompiling. :(
> I found out some time ago exactly how to go about building
> XFree86 DRM modules separate from the xc tree. I extracted the
> relevant portions of the xc tree, packaged them in a smaller
> tarball, and patched said tarball to correct the mga compilation
> issues you're facing. The stuff is here:
> Untar the sources, apply the patch, and then do the following:
> cd linux/drm/kernel &&
> make -f Makefile.linux
> It should build within a few minutes, and then you should have
> all the DRI modules you need.
Thanks, but too late ;-) Must get my eyes tested, I didn't notice this
reply (I'm not using a threaded MUA) when I just replied to my own
posting. I'll review this tomorrow, cos rebuilding X every time I
recompile a kernel is *not* wonderful.
Out of the darkness a voice spake unto me, saying "smile, things could be
worse". So I smiled, and lo, things became worse.
Unsubscribe: send email to listar at linuxfromscratch.org
and put 'unsubscribe blfs-dev' in the subject header of the message
More information about the blfs-dev