Re: [PATCH v2 1/6] m68k: merge mmu and non-mmu versions of muldi3

Philippe De Muyter
2011-04-20T09:12:16Z

On Wed, Apr 20, 2011 at 10:55:15AM +0200, Geert Uytterhoeven wrote:
> On Wed, Apr 20, 2011 at 10:06, Sam Ravnborg <sam@ravnborg.org> wrote:
> > Hi Greg.
> >
> >> +
> >> +#if defined(__mc68020__) || defined(__mc68030__) || \
> >> +    defined(__mc68040__) || defined(__mc68060__)
> >
> > Why use these to decide if this is MMU or not?
> > This code is not exposed to user-space so we can rely on CONFIG_* symbols.
> > IMO the CONIFG_* symbols is easier to read/maintain.
>
> Because technically it doesn't depend on having a MMU or not, but on having
> the full 32-bit multiplication instruction or not.
>
> Does Coldfire-with-MMU (for which we haven't integrated the support
> yet) have that
> instruction?

Actually, MCF547x & MCF548x (CFv4e family) are integrated but without their
limited MMU functionality.

freescale had even written an mmu port for 2.6.25 but has not pushed it
upstream. This port can be found on their site or in the openwrt repository.

MCF547x & MCF548x do not have that instruction.

Philippe
_______________________________________________
uClinux-dev mailing list
uClinux-dev@uclinux.org
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by uclinux-dev@uclinux.org