<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, May 23, 2017 at 3:36 PM, Bruce Ashfield <span dir="ltr"><<a href="mailto:bruce.ashfield@gmail.com" target="_blank">bruce.ashfield@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><div><div class="gmail-h5"><br><div class="gmail_quote">On Mon, May 22, 2017 at 1:06 PM, Khem Raj <span dir="ltr"><<a href="mailto:raj.khem@gmail.com" target="_blank">raj.khem@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span>>> +SRC_URI += "file://drm.cfg"<br>
><br>
><br>
><br>
> If anything gets added to the default configurations, they need to go into<br>
> the kernel-cache<br>
> and then be included by the relevant kernel types there.<br>
><br>
> If you want, I can take care of switching things to that format.<br>
><br>
<br>
</span>yes please.<br>
</blockquote></div><div class="gmail_extra"><br></div></div></div><div class="gmail_extra">Will do. I'll make it available to all active kernel versions + future ones.</div></div></div></blockquote><div><br></div><div>As it turns out, we already have a similar fragment for vmware guests:</div><div><br></div><div>cfg/vmware-guest.cfg<br></div><div><br></div><div>--------------------</div><div>
<p class="gmail-p1"><span class="gmail-s1">CONFIG_VMWARE_BALLOON=</span><span class="gmail-s2">m</span></p><p class="gmail-p1"><span class="gmail-s1">CONFIG_VMWARE_PVSCSI=</span><span class="gmail-s2">y</span><br></p>
<p class="gmail-p1"><span class="gmail-s1">CONFIG_VMWARE_VMCI=</span><span class="gmail-s2">m</span></p>
<p class="gmail-p1"><span class="gmail-s1">CONFIG_VSOCKETS=</span><span class="gmail-s2">m</span></p>
<p class="gmail-p1"><span class="gmail-s1">CONFIG_VMWARE_VMCI_VSOCKETS=</span><span class="gmail-s2">m</span></p>
<p class="gmail-p1"><span class="gmail-s1">CONFIG_VMXNET3=</span><span class="gmail-s2">y</span></p>
<p class="gmail-p1"><span class="gmail-s1">CONFIG_DRM_VMWGFX=</span><span class="gmail-s2">m</span></p>
<p class="gmail-p1"><span class="gmail-s1">CONFIG_DRM_VMWGFX_FBCON=</span><span class="gmail-s2">y</span></p>
<p class="gmail-p1"><span class="gmail-s1">CONFIG_FUSION=</span><span class="gmail-s2">y</span></p>
<p class="gmail-p1"><span class="gmail-s1">CONFIG_FUSION_SPI=</span><span class="gmail-s2">y</span></p>
<p class="gmail-p1"><span class="gmail-s1">CONFIG_FUSION_FC=</span><span class="gmail-s2">y</span></p>
<p class="gmail-p1"><span class="gmail-s1">CONFIG_FUSION_SAS=</span><span class="gmail-s2">y</span></p>
<p class="gmail-p1"><span class="gmail-s1">CONFIG_FUSION_MAX_SGE=</span><span class="gmail-s2">128</span></p>
<p class="gmail-p1"><span class="gmail-s1">CONFIG_FUSION_CTL=</span><span class="gmail-s2">y</span></p>
<p class="gmail-p1"><span class="gmail-s1">CONFIG_FUSION_LAN=</span><span class="gmail-s2">y</span></p>
<p class="gmail-p1"><span class="gmail-s1">CONFIG_FUSION_LOGGING=</span><span class="gmail-s2">y</span></p>
<p class="gmail-p1"><span class="gmail-s1">CONFIG_SCSI_MPT2SAS=</span><span class="gmail-s2">y</span></p>
<p class="gmail-p1"><span class="gmail-s1">CONFIG_SCSI_MPT2SAS_MAX_SGE=</span><span class="gmail-s2">128</span></p>
<p class="gmail-p1"><span class="gmail-s1">CONFIG_SCSI_MPT2SAS_LOGGING=</span><span class="gmail-s2">y</span></p>
<p class="gmail-p1"><span class="gmail-s1">CONFIG_SCSI_MPT3SAS=</span><span class="gmail-s2">y</span></p>
<p class="gmail-p1"><span class="gmail-s1">CONFIG_SCSI_MPT3SAS_MAX_SGE=</span><span class="gmail-s2">128</span></p>
<p class="gmail-p1"><span class="gmail-s1">CONFIG_SCSI_MPT3SAS_LOGGING=</span><span class="gmail-s2">y</span></p></div><div>------------- <br></div><div><br></div><div>To stay consistent with that naming, I'll call this virtual-box-guest.cfg, and it can be enabled</div><div>via KERNEL_FEATURES when needed. </div><div><br></div><div>I'm hesitant to globally enable it, since we don't need those modules on all linux-yocto</div><div>kernels, just ones that are going to run on virtual box. </div><div><br></div><div>I could enable them for qemux86*, since those already have virtio configs enabled by</div><div>default and these have a similar goal.</div><div><br></div><div>Thoughts ? I'd like to make sure that sounds reasonable, before spending the time to </div><div>make the changes and test.</div><div><br></div><div>Bruce</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_extra"><br></div><div class="gmail_extra">Cheers,</div><div class="gmail_extra"><br></div><div class="gmail_extra">Bruce</div><span class="gmail-"><br><br clear="all"><div><br></div>-- <br><div class="gmail-m_-5351939124826968667gmail_signature">"Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end"</div>
</span></div></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature">"Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end"</div>
</div></div>