From: Dave Hylands <dhylands@gmail.com>
To: "Mr. James W. Laferriere" <babydr@baby-dragons.com>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
linux-fbdev@vger.kernel.org,
Linux Kernel Maillist <linux-kernel@vger.kernel.org>
Subject: Re: drivers/gpu/drm/radeon/radeon_test.c:45: undefined reference to `__udivdi3'
Date: Sat, 19 Dec 2009 18:07:24 -0800 [thread overview]
Message-ID: <c32efac40912191807o7f7b7c2dw2259721e6c0635f6@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.01.0912191405460.12202@filesrv1.baby-dragons.com>
Hi Jim,
> Thank you , For replying . Now I being a kernel level nothing ,
> How does this help me get past the 'ld' time undefined reference ? So we
> can have a kernel build complete (hopefully) successfully .
>
> I've another ? as well how is it that the drm/radeon_test.c is using
> (well at least referencing) a non-kernel symbol ? That alone is rather
> interesting .
>
> But all I had to do is Disable DRM in the kernel . Since this system
> is a remote device without a real need for DRI/DRM support that should cure
> my problem . But someone else is going to need that support & I am sure
> they'll hit that same bug .
I'm not familiar with the source code in question, but presumably,
someone will need to change the source to remove the 64-bit divide and
do it using the do_div macro or something equivalent.
--
Dave Hylands
Shuswap, BC, Canada
http://www.DaveHylands.com/
next prev parent reply other threads:[~2009-12-20 2:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-18 20:54 Mr. James W. Laferriere
2009-12-19 9:13 ` Dave Hylands
2009-12-20 1:02 ` Mr. James W. Laferriere
2009-12-20 2:07 ` Dave Hylands [this message]
2009-12-20 6:11 ` Dave Airlie
2009-12-20 21:10 ` Mr. James W. Laferriere
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=c32efac40912191807o7f7b7c2dw2259721e6c0635f6@mail.gmail.com \
--to=dhylands@gmail.com \
--cc=babydr@baby-dragons.com \
--cc=benh@kernel.crashing.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®