Re: Why is ARCH m68k hardwired into drivers/net/wan/Makefile?

From: Rob Landley
Date: Mon Dec 21 2009 - 17:46:40 EST


On Monday 21 December 2009 03:57:49 Geert Uytterhoeven wrote:
> On Mon, Dec 21, 2009 at 06:42, Rob Landley <rob@xxxxxxxxxxx> wrote:
> > Anyone have an opinion on this?
> >
> > From drivers/net/wan/Makefile:
>
> You cut one important line here:
> | ifeq ($(CONFIG_WANXL_BUILD_FIRMWARE),y)
> |
> >>ifeq ($(ARCH),m68k)
> >> AS68K = $(AS)
> >> LD68K = $(LD)
> >>else
> >> AS68K = as68k
> >> LD68K = ld68k
> >>endif
>
> The corresponding Kconfig entry reads:
>
> config WANXL_BUILD_FIRMWARE
> bool "rebuild wanXL firmware"
> depends on WANXL && !PREVENT_FIRMWARE_BUILD
> help
> Allows you to rebuild firmware run by the QUICC processor.
> It requires as68k, ld68k and hexdump programs.
>
> You should never need this option, say N.
>
> Gr{oetje,eeting}s,

Ah, the card has an onboard m68k processor, separate from the host CPU.

Rob
--
Latency is more important than throughput. It's that simple. - Linus Torvalds
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/