From: "Michel Dänzer" <michel@tungstengraphics.com>
To: Dave Airlie <airlied@linux.ie>
Cc: linuxppc-dev@ozlabs.org, dri-devel@lists.sourceforge.net
Subject: Re: DRM git vs. Linux 2.6.17
Date: Wed, 26 Jul 2006 09:43:07 +0200 [thread overview]
Message-ID: <1153899787.20778.99.camel@thor.lorrainebruecke.local> (raw)
In-Reply-To: <Pine.LNX.4.64.0607251030220.30301@skynet.skynet.ie>
On Tue, 2006-07-25 at 10:31 +0100, Dave Airlie wrote:
> Did you build you kernel with CONFIG_DRM=y? if so don't.
>
> to use DRM CVS you need to make sure in-kernel DRM isn't built-in.
Thanks, but I'm quite aware of that. :)
I suspect this might be a PPC specific kernel build system issue related
to Modules.symvers, so I'm CC'ing linuxppc-dev and including the
original post below for reference. Any hints appreciated.
> On Tue, 25 Jul 2006, Michel Dnzer wrote:
>
> Building DRM git against 2.6.17, I get:
>
> Building modules, stage 2.
> MODPOST
> *** Warning: "drm_addbufs_agp" [/home/michdaen/src/mesa-git/drm/linux-core/drm] duplicated symbol!
>
> and the same for a lot of DRM core symbols (possibly all of them). The
> resulting DRM core module loads, but the driver doesn't:
>
> Jul 24 13:47:27 thor kernel: radeon: disagrees about version of symbol drm_open
> Jul 24 13:47:27 thor kernel: radeon: Unknown symbol drm_open
>
> Removing Module.symvers from the DRM and kernel trees before building
> the DRM avoids these problems. Any ideas where the root of this lies?
--
Earthling Michel Dänzer | http://tungstengraphics.com
Libre software enthusiast | Debian, X and DRI developer
next parent reply other threads:[~2006-07-26 8:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1153818665.20778.82.camel@thor.lorrainebruecke.local>
[not found] ` <Pine.LNX.4.64.0607251030220.30301@skynet.skynet.ie>
2006-07-26 7:43 ` Michel Dänzer [this message]
2006-07-26 14:38 ` DRM git vs. Linux 2.6.17 Michel Dänzer
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=1153899787.20778.99.camel@thor.lorrainebruecke.local \
--to=michel@tungstengraphics.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.sourceforge.net \
--cc=linuxppc-dev@ozlabs.org \
/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).