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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 21 Dec 2009 16:54:43 -0600
From:	Rob Landley <rob@...dley.net>
To:	Brian Gerst <brgerst@...il.com>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Why is ARCH m68k hardwired into drivers/net/wan/Makefile?

On Monday 21 December 2009 08:48:31 Brian Gerst wrote:
> On Mon, Dec 21, 2009 at 3:04 AM, Rob Landley <rob@...dley.net> wrote:
> > On Monday 21 December 2009 01:06:38 Brian Gerst wrote:
> >> On Mon, Dec 21, 2009 at 12:42 AM, Rob Landley <rob@...dley.net> wrote:
> >> > Anyone have an opinion on this?
> >> >
> >> > From drivers/net/wan/Makefile:
> >> >>ifeq ($(ARCH),m68k)
> >> >>  AS68K = $(AS)
> >> >>  LD68K = $(LD)
> >> >>else
> >> >>  AS68K = as68k
> >> >>  LD68K = ld68k
> >> >>endif
> >>
> >> Looks like it's to build firmware to run on the card.
> >
> > Sure, I'm just wondering why such obvious arch-specific code is outside
> > the arch/m68k directory.
> >
> > In theory, when you're building for m68k, you supply appropriate AS and
> > LD values already (or the rest of the kernel won't build).  If you're not
> > building for m68k and this driver only supports m68k, then the config
> > should prevent you from selecting it.  So why is on earth is
> > architecture-specific tool selection being done in drivers/net/wan?
>
> The m68k processor that this firmware is being built for is embedded
> on the device, not the main system cpu.  You can have one of these
> cards on any system, not just m68k.
>
> PS. always CC the list with replies.

Happy to, but your message to me didn't cc the list, and I thought cc-ing 
private mail back to the list was impolite.

Explicitly saying somewhere "this card has an onbaord m68k processor even if 
the host doesn't" might be nice.  I eventually figured it out, but neither the 
makefile nor the firmware source actually said the card had an onboard 
processor, and my first glance at the kconfig help text just went "it's code for 
a QUICC processor, that's one of those freescale SoCs isnt it?  I vaguely 
recall booting Linux on one of those back in 2006..."

(Possibly I've been doing a bit too much embedded development lately. :)

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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/