[meta-intel] Meta-Intel NUC Support

[Mittal, Anuj]

Yes, a new machine would be an overkill in my opinion. I will add the
configurations in kernel cache and have this enabled by way of
KERNEL_FEATURES.

Thanks
Anuj

On Thu, 2018-11-01 at 11:05 -0700, Desone Burns wrote:
> Awesome, that worked for me perfectly. Would it be overkill to add
> this particular NUC as another machine? I'd be willing to pull the
> code together and hand it off to you to commit if it makes it easier.
> 
> Regards,
> 
> 	Desone Burns IISoftware EngineerNikola CorporationPhoenix,
> Arizona
> 
> 
> On Wed, Oct 31, 2018 at 5:43 PM Mittal, Anuj <anuj.mittal at intel.com>
> wrote:
> > I gave it a try on my Hades Canyon and this is what I enabled:
> > 
> > CONFIG_DRM_SCHED=m
> > CONFIG_DRM_AMDGPU=m
> > CONFIG_DRM_AMDGPU_SI=y
> > CONFIG_DRM_AMDGPU_CIK=y
> > CONFIG_DRM_AMDGPU_USERPTR=y
> > # CONFIG_DRM_AMDGPU_GART_DEBUGFS is not set
> > # CONFIG_DRM_AMD_ACP is not set
> > 
> > #
> > # Display Engine Configuration
> > #
> > CONFIG_DRM_AMD_DC=y
> > # CONFIG_DRM_AMD_DC_FBC is not set
> > # CONFIG_DRM_AMD_DC_DCN1_0 is not set
> > # CONFIG_DEBUG_KERNEL_DC is not set
> > CONFIG_CHASH=m
> > # CONFIG_CHASH_STATS is not set
> > # CONFIG_CHASH_SELFTEST is not set
> > CONFIG_HSA_AMD=m
> > 
> > And, with rest of current poky and meta-intel master defaults, it
> > looks
> > like everything is working okay.
> > 
> > Can you give this a try? No need to include meta-amd or any other
> > firmware ...
> > 
> > On Wed, 2018-10-31 at 17:06 -0700, Desone Burns wrote:
> > > That definitely makes a difference. At this point, its looking
> > like
> > > the problem is with switching from EFI VGA to amdgpudrmfb. From
> > my
> > > research, this could be due to missing firmware files. I added
> > the
> > > meta-amd layer in hopes that the firmware files would fall into
> > place
> > > but it does not seem to have helped. Is there another option
> > mapped
> > > to the firmware file that I should know about?
> > > Regards,
> > > 
> > >       Desone Burns IISoftware EngineerNikola CorporationPhoenix,
> > > Arizona
> > > 
> > > 
> > > On Tue, Oct 30, 2018 at 11:42 PM Mittal, Anuj <
> > anuj.mittal at intel.com>
> > > wrote:
> > > > On Tue, 2018-10-30 at 19:20 -0700, Desone Burns wrote:
> > > > > That is correct. I modified my image definition to include
> > > > version
> > > > > 4.18 of the Linux-yocto recipe and verified the kernel
> > version
> > > > > updated as well. The problem seems to be with X11 starting
> > up, it
> > > > > says something about not being able to run in framebuffer
> > mode.
> > > > Could
> > > > > this be a driver issue?
> > > > > 
> > > > 
> > > > If you haven't already, you will have to rebuild the linux-
> > yocto
> > > > kernel
> > > > with CONFIG_DRM_AMDGPU enabled (which is not enabled by
> > default).
> > > > 
> > > > Thanks,
> > > > Anuj
> >