mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Rob Landley <rob@landley.net>
Cc: kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Why is ARCH m68k hardwired into drivers/net/wan/Makefile?
Date: Mon, 21 Dec 2009 10:57:49 +0100	[thread overview]
Message-ID: <10f740e80912210157y7b506677q6a40b40435b4634f@mail.gmail.com> (raw)
In-Reply-To: <200912202342.16806.rob@landley.net>

On Mon, Dec 21, 2009 at 06:42, Rob Landley <rob@landley.net> 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,

						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

  reply	other threads:[~2009-12-21  9:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-21  5:42 Rob Landley
2009-12-21  9:57 ` Geert Uytterhoeven [this message]
2009-12-21 22:46   ` Rob Landley
     [not found] ` <73c1f2160912202306y8e3e394mb3b4ddcf24caacc1@mail.gmail.com>
     [not found]   ` <200912210204.08583.rob@landley.net>
2009-12-21 14:48     ` Brian Gerst
2009-12-21 22:54       ` Rob Landley
2009-12-22 15:45         ` Krzysztof Halasa

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=10f740e80912210157y7b506677q6a40b40435b4634f@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rob@landley.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®