From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] mpc885ads: Don't define CONFIG_BZIP2.
Date: Wed, 15 Aug 2007 17:16:28 -0500 [thread overview]
Message-ID: <46C37B3C.7070805@freescale.com> (raw)
In-Reply-To: <20070815215957.656BD24713@gemini.denx.de>
Wolfgang Denk wrote:
> in message <46C36D49.20301@freescale.com> you wrote:
>>There's no device tree support yet, so the wrapper is being used, and
>>that expects to be loaded at 0x400000. Even if that were changed,
>
> Well, there are probably folks out there who continue to use 2.4
> kernels (which on 8xx makes perfect sense to me).
IIRC, 2.4 also had 0x400000 as the default load address, though maybe
those kernels were small enough that they managed to fit.
> Well, let's face it: if 0x200000 doesn't work as load address any
> more because your kernel is too big, then you won't get lucky with it
> at all on a 8 MB system.
The kernel I tested on the board goes to 0x210d84, and that's without
any initramfs... Sure, it's going to be tight, but it's not completely
out of the question.
> I don't really care about the mpc885ads, but I feel you remove a
> feature which might be useful for some to overcome a restriction
> which does not really solve a problem, because you will just hang
> again in the next step.
It solves the problem of not tying up over 1/4 of the board's RAM for
what AFAICT is a not-very-frequently used feature (Linux doesn't use it,
at least). It solves the problem of not being able to load a current
Linux kernel on this board. The user can always re-enable bzip2 support
if they really need it.
-Scott
next prev parent reply other threads:[~2007-08-15 22:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-15 20:46 [U-Boot-Users] [PATCH] mpc885ads: Don't define CONFIG_BZIP2 Scott Wood
2007-08-15 21:12 ` Wolfgang Denk
2007-08-15 21:16 ` Scott Wood
2007-08-15 21:59 ` Wolfgang Denk
2007-08-15 22:16 ` Scott Wood [this message]
2007-08-16 10:05 ` Wolfgang Denk
2007-08-16 10:06 ` 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=46C37B3C.7070805@freescale.com \
--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.