From: Wolfgang Denk <wd@denx.de>
To: "Kerl, John" <John.Kerl@Avnet.com>
Cc: "'Ed Brady'" <mailinglist@ebrady.net>,
"'linuxppc-embedded@lists.linuxppc.org'"
<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Compiling 2.4.18 for Motorola MBX board
Date: Wed, 27 Mar 2002 22:08:38 +0100 [thread overview]
Message-ID: <20020327210843.8B325109F4@denx.denx.de> (raw)
In-Reply-To: Your message of "Wed, 27 Mar 2002 14:02:15 MST." <C08678384BE7D311B4D70004ACA371050B763357@amer22.avnet.com>
In message <C08678384BE7D311B4D70004ACA371050B763357@amer22.avnet.com> you wrote:
>
> The default PPC .config appears to be something that's
> appropriate to, say, running Linux on a Macintosh.
Well, the MBX is an embedded system, so you cannot really expect the
DEFAULT configuration to work on it, right?
> You should go into make menuconfig, & de-select PMAC
> and other Mac-type ethernet devices.
>
> In fact, I made sure to go through every (!) menu,
> sub-menu, sub-sub-menu, etc. in make menuconfig to
> de-select everything that wasn't appropriate for my
> system.
Why not just chosing a working default configuration?
$ make mbx_config
$ make oldconfig
$ make dep
$ make zImage
will do the Right Thing (TM) in a blink or two...
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
Landing: a controlled mid-air collision with a planet.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-03-27 21:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-27 21:02 Compiling 2.4.18 for Motorola MBX board Kerl, John
2002-03-27 21:08 ` Wolfgang Denk [this message]
[not found] <20020327210215.3A202109F4@denx.denx.de>
2002-03-28 4:59 ` Ed Brady
2002-04-01 18:41 ` Ed Brady
-- strict thread matches above, loose matches on Subject: below --
2002-03-27 20:47 Ed Brady
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=20020327210843.8B325109F4@denx.denx.de \
--to=wd@denx.de \
--cc=John.Kerl@Avnet.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=mailinglist@ebrady.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;
as well as URLs for NNTP newsgroup(s).