From: Matt Porter <mporter@kernel.crashing.org>
To: Dan Malek <dan@embeddededge.com>
Cc: Matt Porter <mporter@kernel.crashing.org>,
Stuart Vivian <stuartvivian@domo.co.uk>,
linuxppc-embedded@lists.linuxppc.org
Subject: Re: Linux 2_4_devel kernel hangs after control transferred from u-boot
Date: Thu, 2 Oct 2003 12:33:56 -0700 [thread overview]
Message-ID: <20031002123356.C29772@home.com> (raw)
In-Reply-To: <3F7C59AA.8090707@embeddededge.com>; from dan@embeddededge.com on Thu, Oct 02, 2003 at 01:00:26PM -0400
On Thu, Oct 02, 2003 at 01:00:26PM -0400, Dan Malek wrote:
>
> Matt Porter wrote:
>
> > Hrm, it used to be that everybody said their board was "just like
> > a Sandpoint". I guess walnut is like that in the 4xx world. :)
>
> I did the port for this board over a year ago and gave it to a
> few people that were going to "finish it and check it in"....I
> guess that didn't happen. Lemme see what I can do about getting
> ftp running on my server again and I'll point you to the tarball....
That should save him some time. Any other ports to standard boards
you have laying around? :)
> The only thing similar to a Walnut is it uses a 405GP, there is
> nothing else similar to a Walnut......
Yup, that makes it just like a Walnut similar to the way that every
MPC750/MPC107 board is just like a Sandpoint.
-Matt
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-10-02 19:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-02 13:29 Linux 2_4_devel kernel hangs after control transferred from u-boot Stuart Vivian
2003-10-02 13:43 ` Wolfgang Denk
2003-10-02 15:12 ` Matt Porter
2003-10-02 17:00 ` Dan Malek
2003-10-02 19:33 ` Matt Porter [this message]
2003-10-02 19:54 ` 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=20031002123356.C29772@home.com \
--to=mporter@kernel.crashing.org \
--cc=dan@embeddededge.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=stuartvivian@domo.co.uk \
/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).