Re: [PATCH 27/36] m68k: add code to setup a ColdFire 54xx platform when MMU enabled

Geert Uytterhoeven
2011-10-30T13:39:11Z

On Tue, Oct 25, 2011 at 09:19, <gerg@snapgear.com> wrote:
> From: Greg Ungerer <gerg@uclinux.org>
>
> We use the same setup code for ColdFire MMU enabled platforms as
> standard m68k. So add support for it to setup our 54xx ColdFire
> platforms. They do not support the same bootinfo parsing as other
> m68k platforms.
>
> Signed-off-by: Greg Ungerer <gerg@uclinux.org>
> ---
>  arch/m68k/kernel/setup_mm.c |    8 +++++++-
>  1 files changed, 7 insertions(+), 1 deletions(-)
>
> diff --git a/arch/m68k/kernel/setup_mm.c b/arch/m68k/kernel/setup_mm.c
> index 52e17d1..b3938ad 100644
> --- a/arch/m68k/kernel/setup_mm.c
> +++ b/arch/m68k/kernel/setup_mm.c
> @@ -221,7 +221,8 @@ void __init setup_arch(char **cmdline_p)
>  #endif
>
>        /* The bootinfo is located right after the kernel bss */
> -       m68k_parse_bootinfo((const struct bi_record *)_end);
> +       if (!CPU_IS_COLDFIRE)
> +               m68k_parse_bootinfo((const struct bi_record *)_end);
>
>        if (CPU_IS_040)
>                m68k_is040or060 = 4;
> @@ -327,6 +328,11 @@ void __init setup_arch(char **cmdline_p)
>                config_sun3x();
>                break;
>  #endif
> +#ifdef CONFIG_COLDFIRE
> +       case MACH_M54XX:
> +               config_BSP(NULL, 0);

config_M54xx?

> +               break;
> +#endif
>        default:
>                panic("No configuration setup");
>        }

Gr{oetje,eeting}s,

Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds