All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Ungerer <gerg@snapgear.com>
To: Philippe De Muyter <phdm@macqel.be>
Cc: uClinux development list <uclinux-dev@uclinux.org>,
	linux-m68k@vger.kernel.org, Greg Ungerer <gerg@uclinux.org>
Subject: Re: [uClinux-dev] Re: [PATCH 5/5] m68k: merge non-mmu and mmu	versions of m68k_ksyms.c
Date: Thu, 21 Apr 2011 19:28:38 +1000	[thread overview]
Message-ID: <4DAFF8C6.6080305@snapgear.com> (raw)
In-Reply-To: <20110421083234.GC23491@frolo.macqel>

On 21/04/11 18:32, Philippe De Muyter wrote:
> On Thu, Apr 21, 2011 at 10:16:01AM +0200, Geert Uytterhoeven wrote:
>> On Thu, Apr 21, 2011 at 02:48,<gerg@snapgear.com>  wrote:
>>> +#ifndef CONFIG_MMU
>>
>> While we're at it, that should also be a test for not '020-'060/CPU32?
>
> You beat me on this :)
>
> You're abolutely right, we may not test on CONFIG_MMU for mmu-capable
> coldfires, but which do lack 32x32->64 mulu and friends.

Yep, this should be the same. And I was trying to be careful
and get these right :-(

I'll fix it.

Thanks
Greg



>>> +/*
>>> + * Simpler 68k and ColdFire parts also need a few other gcc functions.
>>> + */
>>> +extern long long __divsi3(long long, long long);
>>> +extern long long __modsi3(long long, long long);
>>> +extern long long __mulsi3(long long, long long);
>>> +extern long long __udivsi3(long long, long long);
>>> +extern long long __umodsi3(long long, long long);
>>> +
>>> +EXPORT_SYMBOL(__divsi3);
>>> +EXPORT_SYMBOL(__modsi3);
>>> +EXPORT_SYMBOL(__mulsi3);
>>> +EXPORT_SYMBOL(__udivsi3);
>>> +EXPORT_SYMBOL(__umodsi3);
>>> á#endif
>
> Philippe
>
>
>


-- 
------------------------------------------------------------------------
Greg Ungerer  --  Principal Engineer        EMAIL:     gerg@snapgear.com
SnapGear Group, McAfee                      PHONE:       +61 7 3435 2888
8 Gardner Close                             FAX:         +61 7 3217 5323
Milton, QLD, 4064, Australia                WEB: http://www.SnapGear.com

      reply	other threads:[~2011-04-21  9:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-21  0:48 [PATCH 0/5] m68k: merge and clean up of arch/m68k/kernel/m68k_ksyms*.c files gerg
2011-04-21  0:48 ` [PATCH 1/5] m68knommu: move EXPORT of dump_fpu to function definition gerg
2011-04-21  0:48   ` [PATCH 2/5] m68knommu: move EXPORT of local checksumming functions to definitions gerg
2011-04-21  0:48     ` [PATCH 3/5] m68knommu: move EXPORT of kernel_thread to function definition gerg
2011-04-21  0:48       ` [PATCH 4/5] m68knommu: remove un-needed exporting of COLDFIRE symbols gerg
2011-04-21  0:48         ` [PATCH 5/5] m68k: merge non-mmu and mmu versions of m68k_ksyms.c gerg
2011-04-21  8:16           ` Geert Uytterhoeven
2011-04-21  8:32             ` Philippe De Muyter
2011-04-21  9:28               ` Greg Ungerer [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=4DAFF8C6.6080305@snapgear.com \
    --to=gerg@snapgear.com \
    --cc=gerg@uclinux.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=phdm@macqel.be \
    --cc=uclinux-dev@uclinux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.