On Fri, Oct 21, 2011 at 09:04, <[email protected]> wrote:
> The selection of the CONFIG_HAVE_GENERIC_HARDIRQS option is not specific
> to the MMU being present and enabled. It is dependant on what CPU we are
> compiling for. The non-MMU 68000 and ColdFire family CPUs use generic
> interrupts, so enable it for them only.
>
> Signed-off-by: Greg Ungerer <[email protected]>
> ---
> arch/m68k/Kconfig | 1 -
> arch/m68k/Kconfig.cpu | 3 +++
> 2 files changed, 3 insertions(+), 1 deletions(-)
>
> diff --git a/arch/m68k/Kconfig b/arch/m68k/Kconfig
> index 26ed01b..9829235 100644
> --- a/arch/m68k/Kconfig
> +++ b/arch/m68k/Kconfig
> @@ -3,7 +3,6 @@ config M68K
> default y
> select HAVE_IDE
> select HAVE_AOUT if MMU
> - select HAVE_GENERIC_HARDIRQS if !MMU
> select GENERIC_IRQ_SHOW if !MMU
> select ARCH_HAVE_NMI_SAFE_CMPXCHG if RMW_INSNS
This will be fixed Really Soon Now (TM).
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]
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
--
To unsubscribe from this list: send the line "unsubscribe linux-m68k" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
