All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] 83xx fails to boot with moderately sized kernels
Date: Mon, 13 Sep 2010 14:21:33 -0500	[thread overview]
Message-ID: <20100913142133.517b0ff9@schlenkerla.am.freescale.net> (raw)
In-Reply-To: <OF79829750.978FEF2E-ONC125779B.0027F49B-C125779B.00283E68@transmode.se>

On Sat, 11 Sep 2010 09:19:34 +0200
Joakim Tjernlund <joakim.tjernlund@transmode.se> wrote:

> >
> > Dear "Ira W. Snyder",
> >
> > In message <20100910181022.GA18510@ovro.caltech.edu> you wrote:
> > >
> > > Would you prefer a patch only for the MPC8349EMDS, or should I try and
> > > convert the other boards too? How should I know which boards are safe?
> > > Grep for CONFIG_E300?
> >
> > I think we should try and update all boards where this applies. I'm
> > not sure, but my wild guess is that this means all processors except
> > 40x and 8xx (probably 5xx as well, but AFAICT there is no Linux
> > available for these anyway, so it does not matter).
> 
> I think 8xx can be fixed quite easily to do 16 MB if needed. Probably
> won't be needed though.

Actually, I got a complaint a while ago (I think it was Ben H) about
problems with large kernels with debugging options on 8xx.

-Scott

  reply	other threads:[~2010-09-13 19:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-09 22:52 [U-Boot] 83xx fails to boot with moderately sized kernels Ira W. Snyder
2010-09-10 11:18 ` Wolfgang Denk
2010-09-10 11:29   ` Stefan Roese
2010-09-10 18:10     ` Ira W. Snyder
2010-09-10 18:26       ` Kim Phillips
2010-09-10 18:53         ` Wolfgang Denk
2010-09-10 19:11           ` Kim Phillips
2010-09-10 18:51       ` Wolfgang Denk
2010-09-11  7:19         ` Joakim Tjernlund
2010-09-13 19:21           ` Scott Wood [this message]
2010-09-13 21:52             ` Joakim Tjernlund
2010-09-13 22:00               ` Scott Wood

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=20100913142133.517b0ff9@schlenkerla.am.freescale.net \
    --to=scottwood@freescale.com \
    --cc=u-boot@lists.denx.de \
    /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.