From mboxrd@z Thu Jan  1 00:00:00 1970
From: Marek Vasut <marek.vasut@gmail.com>
Date: Sat, 5 Nov 2011 23:38:31 +0100
Subject: [U-Boot] [PATCH v2 1/3] image: Make image_get_fdt work like
	image_get_{ram_disk, kernel}
In-Reply-To: <20111105222416.3D3D01893014@gemini.denx.de>
References: <1320164902-24190-1-git-send-email-swarren@nvidia.com>
	<201111052306.23919.marek.vasut@gmail.com>
	<20111105222416.3D3D01893014@gemini.denx.de>
Message-ID: <201111052338.31576.marek.vasut@gmail.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

> Dear Marek Vasut,
> 
> In message <201111052306.23919.marek.vasut@gmail.com> you wrote:
> > Well you put out quite a good reason in the other mail for uImage. Now
> > the problem basically is the negotiation between linux and uboot as of
> > who has to wrap the image into what envelope. I don't see this happening
> > actually, which sucks.
> 
> Look at the PPC code.  There we have a plain simple uImage make target
> in Linux, and everything is fine.  In ARM, we only have a target which
> gives us a pre-wrapped image, i. e. which always includes the kernel's
> wrapper and decompressor.  How can we change this?  Patches are not
> accepted.
> 
> > > What exactly _is_ the problem of uImage?
> > 
> > The exact problem here is it loads the kernel to fixed address.
> 
> This has been addressed, and patches are queued.
> 

I went through the previous discussions, sorry for the noise.
> 
> Best regards,
> 
> Wolfgang Denk