On Thu, Mar 01, 2012 at 09:12:17AM +1300, Andre Renaud wrote: > On 01/03/12 08:59, Stephen Warren wrote: > > Uwe Kleine-König wrote at Wednesday, February 29, 2012 12:44 PM: > > ... > >> If you want to give incentive for U-Boot to improve, drop the target > >> today. And note that at least people caring about boot time must not use > >> the kernel's uImage target anyhow. > > > > If you enable the new config option in this patch, then the performance > > issue is solved; U-Boot doesn't copy the kernel image any more, and the > > kernel decompressor can write directly to the appropriate location without > > moving the image first (assuming your board boot script loads the uImage > > to a non-conflicting address). > > I may have missed part of this, but isn't one of the points regarding > this that the zImage decompressor always runs with data cache disabled, Most certainly not. We've had the data cache enabled for years and years. And I mean 10+ years. We may have been lacking support on some CPUs, but that was because of lack of contributions. > resulting in a slow decompress, where as if the U-Boot decompressor is > used (ie, gzipping the Image, and telling U-Boot to decompress), then it > can run with caches enabled, improving boot speed? That's pure FUD. -- To unsubscribe from this list: send the line "unsubscribe linux-tegra" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
