Re: [linux-yocto] [PATCH 0/1] Fix i915 merge

to the KERNEL_FEATURES variable allowed me to built -tiny successfully for intel-quark. --- Cal From: Bruce Ashfield [bruce.ashfi...@windriver.com] Sent: Monday, August 22, 2016 12:06 PM To: Sullivan, California L; linux-yocto@yoctoproject.org Cc: Ernst, Eric Subject: Re

Re: [linux-yocto] [PATCH 1/3] features: Fix dependencies and =m vs =y discrepancies for corei7

On 08/20/2016 08:45 PM, Wold, Saul wrote: > On Fri, 2016-08-19 at 20:40 -0700, California Sullivan wrote: >> I missed these in my first pass. This should fix the remaining >> warnings >> that occur with the intel-corei7-64 configurations. The ISDN >> configurations might need to be broken out into

Re: [linux-yocto] [PATCH 0/1] Fix i915 merge

Hmm, the patches apply directly just fine. Preempt-rt has a few specific changes, but tiny has a zero diff for i915. I'm not sure why the default merge strategy isn't working. In any case, using 'git merge strategy=resolve' seems to work, we get the expected diff, and preempt-rt compiles again.

Re: [linux-yocto] [PATCH 5/6] [UPSTREAMED] acpi: add support for configfs

In an allmodconfig build I found that configfs (CONFIG_ACPI_CONFIGFS=m introduced in this patch) fails to compile on both standard/intel/base and standard/intel/bxt-rebase branches. Sebastien, could you look into what it takes to fix this? Thanks, Cal Sullivan On 07/11/2016 03:35 PM, Sebastien

Re: [linux-yocto] [yocto-kernel-cache] [PATCH] Fix bitbake warnings on build

Ack'd. It looks like we need this for 4.4 and master as well. Thanks, Cal On 06/27/2016 12:14 AM, rebecca.swee.fun.ch...@intel.com wrote: > From: Rebecca Chang Swee Fun > > Hi Bruce, > > With a build test run on Intel Common BSP, some warning messages poped >

Re: [linux-yocto] [PATCH 0/4] mmc backports for linux-yocto-4.4 standard/base and standard/intel

It looks like "mmc: sdhci-pci: Remove MMC_CAP_BUS_WIDTH_TEST for Intel controller" was brought in by the 4.4.12 update. Drop that one and they should apply. Thanks, Cal On 06/03/2016 09:17 AM, Bruce Ashfield wrote: > On 2016-06-02 11:08 PM, California Sullivan wrote: >> Hi Bruce, >> >> This set

Re: [linux-yocto] [yocto-kernel-cache][PATCHv2 0/4] Enable kernel configuration for Skylake

Ack'd. Please merge quickly. Thanks, Cal On 04/29/2016 02:02 AM, chun.weng@intel.com wrote: > From: Ong Chun Weng > > Hi, > > These patch is to enable the kernel configuration for Skylake. > And these patch is tested on Saddlebrook platform. > > Please review and

Re: [linux-yocto] [yocto-kernel-cache][PATCH 0/6] Enable kernel configuration for Skylake

An overarching problem with this patch series is that the commit format isn't correct. The general commit format is: area/modified: What the commit does Explanation of why this commit is needed/wanted. Signed-off-by: Your Name One-line commit messages should be avoided, and

Re: [linux-yocto] [yocto-kernel-cache][PATCH 4/6] intel-common-drivers: enable EG20T platform controller hub

Minor nitpick: Including this in intel-common-drivers.scc means it will be included in both 32 and 64 bit BSPs, meaning we no longer need it in intel-common-drivers-32.scc. --- Cal On 04/27/2016 09:24 PM, chun.weng@intel.com wrote: > From: Ong Chun Weng > > --- >

Re: [linux-yocto] [yocto-kernel-cache][PATCH 1/6] features: soc: enable configurations for skylake

What is the rational for CONFIG_DRM_LOAD_EDID_FIRMWARE=y? From my understanding it is to manually load monitor information for monitors that don't provide it itself. If my understanding is correct this option shouldn't be necessary for general Skylake enabling. --- Cal On 04/27/2016 09:24 PM,

Re: [linux-yocto] [yocto-kernel-cache][PATCH 3/6] intel-common: add support for more driver features for 32-bit system

I don't think this patch is necessary, as other than sound these options are all in intel-common-drivers.scc. intel-common-drivers-32.scc should be limited to 32-bit specific features. --- Cal On 04/27/2016 09:24 PM, chun.weng@intel.com wrote: > From: Ong Chun Weng

Re: [linux-yocto] [PATCH 1/1] drm/i915/skl: Fix DMC load on Skylake J0 and K0

Hi Bruce, This is for 4.4 and master. Thanks, Cal On 03/29/2016 10:56 AM, Bruce Ashfield wrote: > This is for 4.4 or 4.1 ? .. or both ? > > Bruce > > On 2016-03-28 5:15 PM, California Sullivan wrote: >> NUC6 (Skylake) graphics firmware fails to load without this patch. >> >> From: Mat Martineau

Re: [linux-yocto] [PATCH v2 00/12] intel-common: add intel-developer-drivers.scc to preempt-rt BSPS

On 02/12/2016 07:48 PM, Paul Gortmaker wrote: > [[PATCH v2 00/12] intel-common: add intel-developer-drivers.scc to preempt-rt > BSPS] On 12/02/2016 (Fri 17:42) California Sullivan wrote: > >> Since we include the developer ktype we should include developer drivers. >> >> Signed-off-by: California

Re: [linux-yocto] [PATCH 04/13] base.cfg: disable some HIDs

On 02/07/2016 03:21 PM, Paul Gortmaker wrote: > [[linux-yocto] [PATCH 04/13] base.cfg: disable some HIDs] On 04/02/2016 (Thu > 16:25) California Sullivan wrote: > >> These options default to !EXPERT. Since we removed EXPERT from base, >> these became enabled, adding functionality and size that we

Re: [linux-yocto] [PATCH 03/13] ktypes/base: Disable EMBEDDED and DEBUG_KERNEL

On 02/07/2016 03:17 PM, Paul Gortmaker wrote: > [[linux-yocto] [PATCH 03/13] ktypes/base: Disable EMBEDDED and DEBUG_KERNEL] > On 04/02/2016 (Thu 16:25) California Sullivan wrote: > >> DEBUG_KERNEL should not be in the base ktype, as a production kernel >> may not necessarily want any debug

Re: [linux-yocto] [PATCH 11/13] CONFIG_I2C_I801: set option to yes in intel-core* bsps

On 02/07/2016 03:33 PM, Paul Gortmaker wrote: > [[linux-yocto] [PATCH 11/13] CONFIG_I2C_I801: set option to yes in > intel-core* bsps] On 04/02/2016 (Thu 16:25) California Sullivan wrote: > >> Without EXPERT, we hit a select on I2C_I801, forcing it to yes and >> causing a warning. Set I2C_I801 to

Re: [linux-yocto] [PATCH] intel_pwm: refactor and use the feature fragment

This is only targeted at master/4.4 by the way. In 4.1 CONFIG_PWM_PCA9685 has additional dependencies that we do not want to enable. Thanks, Cal Sullivan On 01/05/2016 02:04 PM, Sullivan, California L wrote: > From: California Sullivan <california.l.sulli...@intel.com> > >