All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Porter <mporter@kernel.crashing.org>
To: Jacky Lam <jackylam@astri.org>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Queston about Walnut
Date: Sat, 4 Oct 2003 09:07:38 -0700	[thread overview]
Message-ID: <20031004090738.A12780@home.com> (raw)
In-Reply-To: <001501c389cc$3d1277a0$0202a8c0@homevl9biy3v7e>; from jackylam@astri.org on Sat, Oct 04, 2003 at 12:34:37AM +0800


On Sat, Oct 04, 2003 at 12:34:37AM +0800, Jacky Lam wrote:
> > On Fri, Oct 03, 2003 at 05:40:46PM +0800, Jacky Lam wrote:
> > >
> > > > the kernel you use - vanilla+ppc-patch - is based on linuxppc-2.4,
> which
> > > > is not appropriate for your system. [At least it was like that some
> time
> > > > ago. Tom, could you please comment.] Try using the linuxppc_2_4_devel
> > > > tree from Bitkeeper or from our FTP server (see http://www.denx.de).
> > >
> > >     I just tried. The result is the same. Using the original
> walnut_config,
> > > it hangs in mapin_ram().
> > >     If I use minimal config, it hangs in __sti().
> > >
> > >     Does anyone still working on Walnut platform and successfully boot
> up
> > > 2.4 kernel on that? If no, could someone remember what is the last known
> > > working toolchain and kernel on Walnut?
> >
> > I noticed this about a week ago.  It is some kind of merge problem
> > between linux-2.4 and linuxppc-2.4.  linux-2.4 boot fine on walnut
> > for me.  I didn't have time to investigate but might take a look at
> > it again soon.
>
>     Really? That's so great! Do you have any idea about this? Maybe I can
> try to investigate as well. Also, do you remember what is the version just
> before this merge problem occurs? Thanks.

Well, maybe I should have cleaned my tree from a 440 build, I had
an old CONFIG_440 hanging around causing the kernel to not be
happy.  At any rate, I verified that current linuxppc-2.4 boots
on walnut from stock openbios.

-Matt

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2003-10-04 16:07 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <000e01c388dc$eb525510$0202a8c0@homevl9biy3v7e>
2003-10-02 12:17 ` Queston about Walnut Wolfgang Denk
2003-10-03  1:18   ` Jacky Lam
     [not found]     ` <3F7D3238.2090400@bluewin.ch>
2003-10-03  9:40       ` Jacky Lam
2003-10-03 15:07         ` Matt Porter
2003-10-03 16:34           ` Jacky Lam
2003-10-04 16:07             ` Matt Porter [this message]
2003-10-03 16:10         ` Dan Kegel
2003-10-03 16:45           ` Jacky Lam
2003-10-03 17:31             ` Dan Kegel
     [not found]       ` <20031003151729.GC21468@ip68-0-152-218.tc.ph.cox.net>
2003-10-03 23:36         ` Kernel versions Gary Thomas
2003-10-07 13:37           ` Tom Rini
2003-10-03  4:11   ` Queston about Walnut Jacky Lam
2003-10-03  7:44     ` Jacky Lam
2003-10-03 13:51 ARIBAUD Albert
  -- strict thread matches above, loose matches on Subject: below --
2003-10-03  7:57 ARIBAUD Albert
2003-10-03  8:26 ` Jacky Lam
2003-10-02  9:17 Jacky Lam
2003-10-02 10:13 ` 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=20031004090738.A12780@home.com \
    --to=mporter@kernel.crashing.org \
    --cc=jackylam@astri.org \
    --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.