<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On 29 January 2015 at 10:10, Nicolas Dechesne <span dir="ltr"><<a href="mailto:nicolas.dechesne@linaro.org" target="_blank">nicolas.dechesne@linaro.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":20z" class="a3s" style="overflow:hidden">well, i am not sure this is right... at least probably not the right<br>
argument. oe-core is not meant to be tied to specific intel stable<br>
releases, whether it is about content or schedule..<br>
<br>
i would believe our goal is to provide the most recent stable release<br>
instead. so that each OE (well, Yocto) release ends up with the most<br>
recent versions.<br>
<br>
fwiw, for the boards/platforms i care about, 10.4.3 would be fine.</div></blockquote><div><br></div><div>Agreed. The Intel driver release is tested with 10.4.0 but 10.4.3 is a newer point release so should work, and Intel's aim of ensuring that the latest driver stack is supported doesn't trump having the latest upstream releases in oe-core.</div><div><br></div><div>If it turns out that 10.4.3 is critically broken with the Intel driver then *meta-intel* can ship 10.4.0.</div><div><br></div><div>Please re-submit this with 10.4.3 instead of 10.4.0.</div><div><br></div><div>Ross</div></div></div></div>