<p dir="ltr"><br></p>
<p dir="ltr">I feel we gain the greatness of unified kernel but we make separate images that handle the u-boot quirks. We push down the stack so to speak. The only diff of each image being load addr's.</p>
<p dir="ltr">The exynos5 kernel requires FIT images, so an extra dimension of complexity. Well, at least for chromebook. Anyhow, fit images is a move in the right direction but not all u-boot support that so....<br></p>
<p dir="ltr">The problem statement is different u-boot are different, and we cannot have unified images. </p>
<p dir="ltr">We have a rootfs and make images for boards based on uboot quirks. Lucky if we can simplify load addr's, but we just have to test.<br></p>
<p dir="ltr">-Jon Disnard<br>
Fas: parasense<br>
Irc: masta</p>
<div class="gmail_quote">On Mar 26, 2013 8:31 PM, "Graeme Russ" <<a href="mailto:graeme.russ@gmail.com">graeme.russ@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Brendan,<br>
<br>
On Wed, Mar 27, 2013 at 12:13 PM, Brendan Conoboy <<a href="mailto:blc@redhat.com">blc@redhat.com</a>> wrote:<br>
> On 03/26/2013 06:09 PM, Graeme Russ wrote:<br>
>><br>
>> I've had a quick glance at the U-Boot source and I think the newer<br>
>> 'FIT' image may be a better path to follow. In common/image.c you will<br>
>> find fit_image_get_load() and in common/cmd_bootm.c you will find<br>
>> bootm_start() and bootm_load_os(). Teasing apart these functions, it<br>
>> looks like fit_image_get_load() looks for a "load" property<br>
>> (FIT_LOAD_PROP) in the FDT first, then in the FIT image (if the FDT<br>
>> returns a NULL load address).<br>
>><br>
>> Now you can set properties in the FDT in U-Boot (fdt set <path> <prop><br>
>> [<val>])<br>
>><br>
>> So have a common FIT image with a common FDT and use U-Boot to tweak<br>
>> the FDT properties such as the kernel load address<br>
><br>
><br>
> I'd love to, but we don't ship uboot for a number of our boards. We are<br>
> limited to the functionality provided by the firmware provided. FIT is not<br>
> universal.<br>
<br>
Well at least you can have a common image for all U-Boot boards :)<br>
<br>
I suppose the 64-byte header per-board would work. Ugly, but not as<br>
ugly as some of the other options.<br>
<br>
You could also make a small mod to U-Boot to allow the load address of<br>
legacy images to be changed via a command to make the hack slightly<br>
less ugly<br>
<br>
Regards,<br>
<br>
Graeme<br>
_______________________________________________<br>
arm mailing list<br>
<a href="mailto:arm@lists.fedoraproject.org">arm@lists.fedoraproject.org</a><br>
<a href="https://admin.fedoraproject.org/mailman/listinfo/arm" target="_blank">https://admin.fedoraproject.org/mailman/listinfo/arm</a></blockquote></div>