From: Dan Malek <dan@mvista.com>
To: Kent Borg <kentborg@borg.org>
Cc: linuxppc-embedded@lists.linuxppc.org, pbarada@wm.sps.mot.com
Subject: Re: 405 Walnut Status?
Date: Tue, 04 Sep 2001 17:18:48 -0400 [thread overview]
Message-ID: <3B954538.786491A3@mvista.com> (raw)
In-Reply-To: 20010830161812.A4855@borg.org
Kent Borg wrote:
>
> What kind of shape is the 405 Walnut code in ppc.bitkeeper.com:5000
> linuxppc_2_4_devel kernel?
As of last week, it should build and boot. There have been some
updates to the bootloader I haven't verified, but it should work.
> I can't figure out how to even config and compile it.
Are you actually using the BK tools? If so, you should 'bk clone',
then go into the directory and 'bk -r get', 'make walnut_config',
'make oldconfig', 'make dep', 'make zImage'.......
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-09-04 21:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-30 20:18 405 Walnut Status? Kent Borg
2001-09-04 21:18 ` Dan Malek [this message]
2001-09-05 14:50 ` Peter Barada
2001-09-05 15:57 ` Dan Malek
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=3B954538.786491A3@mvista.com \
--to=dan@mvista.com \
--cc=kentborg@borg.org \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=pbarada@wm.sps.mot.com \
/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).