From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: Andy Walls <awalls@radix.net>
Cc: "David Härdeman" <david@hardeman.nu>,
linux-input@vger.kernel.org, linux-media@vger.kernel.org
Subject: Re: [PATCH] Teach drivers/media/IR/ir-raw-event.c to use durations
Date: Fri, 09 Apr 2010 21:43:10 -0300 [thread overview]
Message-ID: <4BBFC99E.6010707@infradead.org> (raw)
In-Reply-To: <1270848998.3038.47.camel@palomino.walls.org>
Andy Walls wrote:
> On Thu, 2010-04-08 at 18:10 +0200, David Härdeman wrote:
>
>> With this patch:
>>
>> s64 int's are used to represent pulse/space durations in ns
>
> If performing divides on 64 bit numbers, please check to make sure your
> code compiles, links, and loads on a 32-bit system.
>
> We've had problems in the past in where gcc will build the module to
> reference __udivdi3 under 32-bit kernels; but that symbol is not in the
> kernel.
Good catch!
> Search for 'do_div' in:
>
> linux/drivers/media/video/cx18/cx18-av-core.c
>
> for a simple example divide that works on both 64 and 32 bit machines.
Unfortunately, not all gcc versions complain about the lack of the __udivi32
library. Some (like the one I run on my desktop), will add some inlined
assembler code for it, instead of requiring some library to do the division.
We'll likely only discover such bugs only after sending the code to linux-next
(done later yesterday - but I suspect that it were pulled only today from
my tree) and receiving a complain for the ones that run those robots that
test hundreds of different CONFIG_foo options.
So, I suspect that we'll have some of such complaints by tomorrow...
--
Cheers,
Mauro
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2010-04-10 0:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-08 16:10 [PATCH] Teach drivers/media/IR/ir-raw-event.c to use durations David Härdeman
2010-04-09 21:36 ` Andy Walls
2010-04-10 0:43 ` Mauro Carvalho Chehab [this message]
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=4BBFC99E.6010707@infradead.org \
--to=mchehab@infradead.org \
--cc=awalls@radix.net \
--cc=david@hardeman.nu \
--cc=linux-input@vger.kernel.org \
--cc=linux-media@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;
as well as URLs for NNTP newsgroup(s).