All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jon Loeliger <jdl@freescale.com>
To: nanda <nanda74pg@rediffmail.com>
Cc: Linuxppc-dev@ozlabs.org, Ltib@nongnu.org, seh@zee2.com
Subject: Re: Re :Re: [Ltib] ltib error -linux2.6.20.6 with MPC8360E MDS
Date: Fri, 21 Nov 2008 08:42:10 -0600	[thread overview]
Message-ID: <4926C8C2.60802@freescale.com> (raw)
In-Reply-To: <DFTSgh6rR4.old.1227276970.57828@webmail.rediffmail.com>

nanda wrote:
> Hi Stuart,
>    Thanks for the information.   gpp access was resolved.
>    I was successful in building the linux 2.6.11 using the ltib and able 
> to bring up the MPC8360 EMDS.
> But, I still face the problem for linux kernel 2.6.19 and 2.6.20.   When 
> I tried using ltib in the bringing up the board. 
>   The MPC 8360 board keeps rebooting after downloading the image Power 
> PC Kernel Image(uImage) and Power PC RAMDisk 
> Image(rootfs.ext2.gz.uboot)  build by the "ltib" 
>     Please clarrify on the same.
> 

I'm not a kernel expert and don't know what failure you
are seeing here, but I might observe that 2.6.19 and .20
are two years old, and 2.6.11 is more than 3 years old.

If you think we, collectively, haven't improved things in
that time period, please, complain about 2.6.11, .19, and .20.

If on the off chance you think things *might* have gotten
better due to a *bit* of development effort over the past
three years, you might try installing a modern U-Boot and
a modern Kernel.

Thanks,
jdl

  parent reply	other threads:[~2008-11-21 14:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-21 14:16 Re :Re: [Ltib] ltib error -linux2.6.20.6 with MPC8360E MDS nanda
2008-11-21 14:19 ` Stuart Hughes
2008-11-21 14:42 ` Jon Loeliger [this message]
2008-11-26  3:33   ` Jerry Van Baren

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=4926C8C2.60802@freescale.com \
    --to=jdl@freescale.com \
    --cc=Linuxppc-dev@ozlabs.org \
    --cc=Ltib@nongnu.org \
    --cc=nanda74pg@rediffmail.com \
    --cc=seh@zee2.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 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.