From mboxrd@z Thu Jan 1 00:00:00 1970 From: Scott Wood Date: Wed, 15 Aug 2007 17:16:28 -0500 Subject: [U-Boot-Users] [PATCH] mpc885ads: Don't define CONFIG_BZIP2. In-Reply-To: <20070815215957.656BD24713@gemini.denx.de> References: <20070815215957.656BD24713@gemini.denx.de> Message-ID: <46C37B3C.7070805@freescale.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.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