<div dir="ltr"><div style>And also staging firmware files just once to resolve</div><div style><br></div>> WARNING: The recipe linux-firmware is trying to install files into a shared area when those files already exist. Those files are:<br>
<div><br></div><div style>when building linux-firmware after kernel was built and vice-versa.</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sat, Apr 6, 2013 at 12:26 PM, Koen Kooi <span dir="ltr"><<a href="mailto:koen@dominion.thruhere.net" target="_blank">koen@dominion.thruhere.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
Op 5 apr. 2013, om 19:06 heeft Ross Burton <<a href="mailto:ross.burton@intel.com">ross.burton@intel.com</a>> het volgende geschreven:<br>
<div class="im"><br>
> Whilst splitting out specific large firmware blobs is a good move for space<br>
> saving, it makes installing "all the firmware" tricky.<br>
><br>
> Make linux-firmware depend on all of the separated packages so that installing<br>
> that pulls in all of the sub-packages.<br>
<br>
</div>Speaking of firmwares, is anybody working on fixing the clashes between kernel-firmware-foo and linux-firmware-foo? It should only be a matter of adding RREPLACES to the linux-firmware subpackages.<br>
<span class="HOEnZb"><font color="#888888"><br>
Koen<br>
</font></span><div class="HOEnZb"><div class="h5">_______________________________________________<br>
Openembedded-core mailing list<br>
<a href="mailto:Openembedded-core@lists.openembedded.org">Openembedded-core@lists.openembedded.org</a><br>
<a href="http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core" target="_blank">http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core</a><br>
</div></div></blockquote></div><br></div>