From: Krzysztof Halasa <khc@pm.waw.pl>
To: Rob Landley <rob@landley.net>
Cc: Brian Gerst <brgerst@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Why is ARCH m68k hardwired into drivers/net/wan/Makefile?
Date: Tue, 22 Dec 2009 16:45:38 +0100 [thread overview]
Message-ID: <m3eimngggt.fsf@intrepid.localdomain> (raw)
In-Reply-To: <200912211654.43710.rob@landley.net> (Rob Landley's message of "Mon, 21 Dec 2009 16:54:43 -0600")
Rob Landley <rob@landley.net> writes:
> 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..."
QUICC = QUad Integrated Communications Controller (Morotola 68360) chip
and is based on m68020 IIRC. There is no "normal" m68k CPU on this board.
PowerQUICC is a different thing.
--
Krzysztof Halasa
prev parent reply other threads:[~2009-12-22 15:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-21 5:42 Why is ARCH m68k hardwired into drivers/net/wan/Makefile? Rob Landley
2009-12-21 9:57 ` Geert Uytterhoeven
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 [this message]
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=m3eimngggt.fsf@intrepid.localdomain \
--to=khc@pm.waw.pl \
--cc=brgerst@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.