<div dir="ltr">Ross and I were discussing that Nathan's patches in <a href="http://lists.openembedded.org/pipermail/openembedded-core/2017-January/131012.html">http://lists.openembedded.org/pipermail/openembedded-core/2017-January/131012.html</a> are equivalent and were introduced first.</div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jan 19, 2017 at 9:40 AM, Burton, Ross <span dir="ltr"><<a href="mailto:ross.burton@intel.com" target="_blank">ross.burton@intel.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote"><span class="">On 19 January 2017 at 17:37, Denys Dmytriyenko <span dir="ltr"><<a href="mailto:denis@denix.org" target="_blank">denis@denix.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div id="m_-6168700665141939843gmail-:1tg" class="m_-6168700665141939843gmail-a3s m_-6168700665141939843gmail-aXjCH m_-6168700665141939843gmail-m159b7cfb5b346700">Sometimes it's useful to load ramdisk in a specific location. Your patch<br>
unconditionally removes this support, which is not a desired change. I have<br>
a patch queued up to do it conditionally, which I'll try to submit shortly.<br></div></blockquote><div><br></div></span><div>Would that be the same as Nathan's "kernel-fitimage.bbclass: Allow unset load/entry addresses for ramdisks"?</div><span class="HOEnZb"><font color="#888888"><div><br></div><div>Ross </div></font></span></div><br></div></div>
</blockquote></div><br></div>