public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: David Ward <david.ward@gatech.edu>
To: Michael Krufky <mkrufky@kernellabs.com>
Cc: linux-media@vger.kernel.org, Andy Walls <awalls@radix.net>
Subject: Re: "Unknown symbol __udivdi3" with rev >= 11873
Date: Thu, 28 May 2009 17:43:32 -0400	[thread overview]
Message-ID: <4A1F0584.6040001@gatech.edu> (raw)
In-Reply-To: <37219a840905281212i6707a718t3b1e3c9b03d4ac3b@mail.gmail.com>

On 05/28/2009 03:12 PM, Michael Krufky wrote:
> On Thu, May 28, 2009 at 12:05 AM, David Ward<david.ward@gatech.edu>  wrote:
>    
>> Revision 11873 (committed earlier today) has broken the cx18 driver for me,
>> with the line "cx18: Unknown symbol __udivdi3" appearing in dmesg when the
>> module tries to load.  I'm using Ubuntu 8.04.2 which uses kernel 2.6.24 and
>> gcc 4.2.4.
>>
>> I also wanted to express my appreciation to Mauro for fixing the build for
>> older kernels today, as it is very desirable for me to use a
>> distribution/kernel which has long-term support and updates, but I simply
>> need to add a DVB driver that wasn't part of the older kernel.
>>
>> Thanks so much.
>>
>> David Ward
>>      
> Let it be known that this issue only affects 32bit kernels.  I believe
> the offending line of code is here:
>
> fsc = ((((u64)sc) * 28636360)/src_decimation)>>  13L;
>
> (cc added to Andy Walls)
>
> -Mike Krufky
>    
Some Google searching seems to suggest that the correct thing to do here 
is to use the 'do_div' macro for the division, which is declared in 
<asm/div64.h>:

http://www.captain.at/howto-udivdi3-umoddi3.php

David

  reply	other threads:[~2009-05-28 21:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-28  4:05 "Unknown symbol __udivdi3" with rev >= 11873 David Ward
2009-05-28 19:12 ` Michael Krufky
2009-05-28 21:43   ` David Ward [this message]
2009-05-28 21:50     ` Michael Krufky

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=4A1F0584.6040001@gatech.edu \
    --to=david.ward@gatech.edu \
    --cc=awalls@radix.net \
    --cc=linux-media@vger.kernel.org \
    --cc=mkrufky@kernellabs.com \
    /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