From mboxrd@z Thu Jan 1 00:00:00 1970 From: Wolfgang Denk Date: Tue, 14 Aug 2007 09:50:35 +0200 Subject: [U-Boot-Users] [PATCH] Fix initrd/dtb interaction In-Reply-To: Your message of "Tue, 14 Aug 2007 02:00:13 CDT." <2acbd3e40708140000g1acdf9e3mf3d7f4f8c2788d1@mail.gmail.com> Message-ID: <20070814075035.4BF2724041@gemini.denx.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de In message <2acbd3e40708140000g1acdf9e3mf3d7f4f8c2788d1@mail.gmail.com> you wrote: > > > > > > +#define DEBUG > > Oops. That was a stupid oversight. OK. Please resubmit without this, then. > So we can add an environment variable to override the 16M limit for > u-boot, but if anyone sets it above 16M (on 85xx), it'll screw things > up. I don't have a fundamental issue with such a variable being > added, but I don't think I have time to figure it out this week, and I > don't think it solves the problem (though it would allow users to > solve it). > > In other words, I think we need both. BOOTMAPSZ is clearly meant to > serve as a ceiling for things like the blob (the bd_t, for instance, > is always put in that range if it exists). The environment variable > would give everyone more flexibility. Sadly, though, I only have time > to fix the obvious problem (leaving DEBUG defined). I'd be happy to > implement the environment variable for the *next* merge window, but > I'd really hate to let this bug sit in u-boot for another release. Agreed. So plese resubmit without the DEBUG thingy, and we'll discuss and fix the other thing next time. OK? Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de "If a computer can't directly address all the RAM you can use, it's just a toy." - anonymous comp.sys.amiga posting, non-sequitir