<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, May 24, 2017 at 10:46 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:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Wed, May 24, 2017 at 7:40 PM, Bruce Ashfield<br>
<div><div class="h5"><<a href="mailto:bruce.ashfield@gmail.com">bruce.ashfield@gmail.com</a>> wrote:<br>
><br>
><br>
> On Tue, May 23, 2017 at 3:36 PM, Bruce Ashfield <<a href="mailto:bruce.ashfield@gmail.com">bruce.ashfield@gmail.com</a>><br>
> wrote:<br>
>><br>
>><br>
>><br>
>> On Mon, May 22, 2017 at 1:06 PM, Khem Raj <<a href="mailto:raj.khem@gmail.com">raj.khem@gmail.com</a>> wrote:<br>
>>><br>
>>> >> +SRC_URI += "file://drm.cfg"<br>
>>> ><br>
>>> ><br>
>>> ><br>
>>> > If anything gets added to the default configurations, they need to go<br>
>>> > 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>
>>> yes please.<br>
>><br>
>><br>
>> Will do. I'll make it available to all active kernel versions + future<br>
>> ones.<br>
><br>
><br>
> As it turns out, we already have a similar fragment for vmware guests:<br>
><br>
> cfg/vmware-guest.cfg<br>
><br>
> --------------------<br>
><br>
> CONFIG_VMWARE_BALLOON=m<br>
><br>
> CONFIG_VMWARE_PVSCSI=y<br>
><br>
> CONFIG_VMWARE_VMCI=m<br>
><br>
> CONFIG_VSOCKETS=m<br>
><br>
> CONFIG_VMWARE_VMCI_VSOCKETS=m<br>
><br>
> CONFIG_VMXNET3=y<br>
><br>
> CONFIG_DRM_VMWGFX=m<br>
><br>
> CONFIG_DRM_VMWGFX_FBCON=y<br>
><br>
> CONFIG_FUSION=y<br>
><br>
> CONFIG_FUSION_SPI=y<br>
><br>
> CONFIG_FUSION_FC=y<br>
><br>
> CONFIG_FUSION_SAS=y<br>
><br>
> CONFIG_FUSION_MAX_SGE=128<br>
><br>
> CONFIG_FUSION_CTL=y<br>
><br>
> CONFIG_FUSION_LAN=y<br>
><br>
> CONFIG_FUSION_LOGGING=y<br>
><br>
> CONFIG_SCSI_MPT2SAS=y<br>
><br>
> CONFIG_SCSI_MPT2SAS_MAX_SGE=<wbr>128<br>
><br>
> CONFIG_SCSI_MPT2SAS_LOGGING=y<br>
><br>
> CONFIG_SCSI_MPT3SAS=y<br>
><br>
> CONFIG_SCSI_MPT3SAS_MAX_SGE=<wbr>128<br>
><br>
> CONFIG_SCSI_MPT3SAS_LOGGING=y<br>
><br>
> -------------<br>
><br>
> To stay consistent with that naming, I'll call this virtual-box-guest.cfg,<br>
> and it can be enabled<br>
> via KERNEL_FEATURES when needed.<br>
><br>
> I'm hesitant to globally enable it, since we don't need those modules on all<br>
> linux-yocto<br>
> kernels, just ones that are going to run on virtual box.<br>
><br>
> I could enable them for qemux86*, since those already have virtio configs<br>
> enabled by<br>
> default and these have a similar goal.<br>
><br>
> Thoughts ? I'd like to make sure that sounds reasonable, before spending the<br>
> time to<br>
> make the changes and test.<br>
><br>
<br>
</div></div>I would suggest to enable them by default since these are modules they<br>
dont impact the size of kernel itself. Then we can use recommends to<br>
choose them in machine configs.<br></blockquote><div><br></div><div>We've never done that before, there's hundreds of modules we could turn on </div><div>just in case, but instead only enable them for machines that can actually use</div><div>them.</div><div><br></div><div>Many users use the meta package for modules and expect the build to be as</div><div>minimal as possible.</div><div><br></div><div>So I'm balancing both those use cases.</div><div><br></div><div>I'll complete the fragment and we can enable it in a second commit to keep the</div><div>options open.</div><div><br></div><div>Bruce</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb"><div class="h5"><br>
> Bruce<br>
><br>
>><br>
>> Cheers,<br>
>><br>
>> Bruce<br>
>><br>
>><br>
>><br>
>> --<br>
>> "Thou shalt not follow the NULL pointer, for chaos and madness await thee<br>
>> at its end"<br>
><br>
><br>
><br>
><br>
> --<br>
> "Thou shalt not follow the NULL pointer, for chaos and madness await thee at<br>
> its end"<br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature">"Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end"</div>
</div></div>