From: Matt Porter <porter@cox.net>
To: brian.auld@adic.com
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Trying to use ELDK to build Ebony/440GP
Date: Thu, 30 Jan 2003 13:37:43 -0700 [thread overview]
Message-ID: <20030130133743.A25221@home.com> (raw)
In-Reply-To: <995FF289C9D69747A09E42992644595405B23634@penguin.adic.com>; from brian.auld@adic.com on Thu, Jan 30, 2003 at 11:06:12AM -0800
On Thu, Jan 30, 2003 at 11:06:12AM -0800, brian.auld@adic.com wrote:
> (2) What's the best method to successfully build a kernel for the ebony
> board using the ELDK tools:
> - Port ebony support into e-new?
> - Try and work out build issues with 2_4_d configured for 'ebony'.
>
> Wanted to solicit some feedback before I go into tangent land.
I can't imagine why any ppc4xx toolchain couldn't build a properly
configured linuxppc_2_4_devel ebony kernel. It's working right now
for my toolchain (mvista)...I haven't used ELDK for a little while now.
I take you have done the following?:
make ebony_config
make oldconfig
make dep zImage
Where you have hacked ARCH and CROSS_COMPILE in the top-level Makefile
or have a script which passes in the appropriate prefix for your
toolchain. i.e. "make ARCH=ppc CROSS_COMPILE=ppc_405- <rule>"
Regards,
--
Matt Porter
porter@cox.net
This is Linux Country. On a quiet night, you can hear Windows reboot.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-01-30 20:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-30 19:06 Trying to use ELDK to build Ebony/440GP brian.auld
2003-01-30 20:37 ` Matt Porter [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-30 21:02 brian.auld
2003-01-30 21:16 ` Matt Porter
2003-01-30 21:59 ` Wolfgang Denk
2003-01-30 21:27 brian.auld
2003-01-30 21:47 ` Wolfgang Grandegger
2003-01-30 21:53 xiaogeng_jin
2003-01-30 21:56 brian.auld
2003-01-30 22:34 brian.auld
2003-01-31 0:12 ` Wolfgang Denk
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=20030130133743.A25221@home.com \
--to=porter@cox.net \
--cc=brian.auld@adic.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
/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.