[meta-intel] [ANNOUNCEMENT] meta-intel 6.0 for Skylake Halo DDR4 RVP11 (Kabylake) support on Yocto Project "morty" 2.2 is now available

[Chang, Rebecca Swee Fun]

Hi all,

We are pleased to announce the following meta-intel BSP layers for Skylake Halo 
DDR4 RVP 11 is now available for download.

Intel Skylake Halo DDR4 RVP11 (Kabylake) Yocto Project Version 2.2 - Morty.
It is supported by Intel Common Core BSP.

Features supported in this release:
- Linux kernel version 4.8.0
- Support integrated graphics (i915)
- Support I/O devices - SATA, USB Host v2.0&3.0, HD Audio, EC UART
- Support Saddle Brook platform in-chip Ethernet driver: e1000e
- Support single displays (HDMI or DP)
- Support resolution for DP & HDMI (3840x2160@30Hz/4096x2160@24Hz)
- Support 2 Independent Displays (HDMI, DP)
- Support 2D HW acceleration (Cairo)
- Support 3D HW acceleration (GL4.3 and GLES2.0/3.1)
- Support HW Media acceleration (H.264, HEVC, MPEG-2, VC-1, WMV, VP8, VP9)
- Support HW Media encoding (H.264, HEVC, MPEG-2, VP8)
- Support Media Players (Gstreamer-VAAPI)

Download Link: 
https://www.yoctoproject.org/downloads/bsps/morty22/skylake-halo-ddr4-rvp11-kabylake

Thank you.

Regards,
Rebecca Chang
-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

Re: [meta-intel] [jethro] [PATCH 0/2] Update on kernel v4.1 recipe for Leaf Hill BSP

[Chang, Rebecca Swee Fun]

Sorry, I just noticed it was merged. Thank you very much.

Regards,
Rebecca

-Original Message-
From: meta-intel-boun...@yoctoproject.org 
[mailto:meta-intel-boun...@yoctoproject.org] On Behalf Of Chang, Rebecca Swee 
Fun
Sent: Wednesday, November 16, 2016 4:42 PM
To: meta-intel@yoctoproject.org; Saul Wold <s...@linux.intel.com>; Wold, Saul 
<saul.w...@intel.com>
Cc: Ashfield, Bruce (Wind River) <bruce.ashfi...@windriver.com>
Subject: Re: [meta-intel] [jethro] [PATCH 0/2] Update on kernel v4.1 recipe for 
Leaf Hill BSP

Hi Saul,

Is this change for Jethro being reviewed?
We need this fix to be merge as soon as possible in order to be able to 
customize kernel configs in our custom meta layers.

Thanks.

Regards,
Rebecca

-Original Message-
From: meta-intel-boun...@yoctoproject.org 
[mailto:meta-intel-boun...@yoctoproject.org] On Behalf Of Rebecca Chang Swee Fun
Sent: Thursday, November 3, 2016 4:21 PM
To: meta-intel@yoctoproject.org
Cc: Ashfield, Bruce (Wind River) <bruce.ashfi...@windriver.com>
Subject: [meta-intel] [jethro] [PATCH 0/2] Update on kernel v4.1 recipe for 
Leaf Hill BSP

Hi,

I have found some issue where I can't override the existing kernel configs on 
kernel-meta using my custom .cfg and .scc files in my custom layer.
We have been using KERNEL_FEATURES in the recipe to parse .scc from 
yocto-kernel-cache and this has caused the issue of configs unable to override 
with custom layer.

I have shared my issue with Bruce Ashfield (maintainer of linux-yocto) and he 
suggested the following fix in the kernel recipe.

I have verified the fix and I am able to change the kernel configs by supplying 
my own .cfg and .scc file in my custom meta layer.

The second patch is to update the SRCREV of machine branch for Leaf Hill BSP.

Please review and provide your feedback if you have any.
This patch is targeted for meta-intel branch jethro only.

Thank you.

Regards,
Rebecca


Rebecca Chang Swee Fun (2):
  linux-yocto_4.1: use BSP_SUBTYPE for BSP specific configuration
  linux-yocto_4.1: bump up machine branch source revision to latest

 common/recipes-kernel/linux/linux-yocto_4.1.bbappend | 8 
 conf/machine/intel-corei7-64.conf| 2 +-
 2 files changed, 5 insertions(+), 5 deletions(-)

--
1.9.1

--
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel
-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel
-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

Re: [meta-intel] [jethro] [PATCH 0/2] Update on kernel v4.1 recipe for Leaf Hill BSP

[Chang, Rebecca Swee Fun]

Hi Saul,

Is this change for Jethro being reviewed?
We need this fix to be merge as soon as possible in order to be able to 
customize kernel configs in our custom meta layers.

Thanks.

Regards,
Rebecca

-Original Message-
From: meta-intel-boun...@yoctoproject.org 
[mailto:meta-intel-boun...@yoctoproject.org] On Behalf Of Rebecca Chang Swee Fun
Sent: Thursday, November 3, 2016 4:21 PM
To: meta-intel@yoctoproject.org
Cc: Ashfield, Bruce (Wind River) 
Subject: [meta-intel] [jethro] [PATCH 0/2] Update on kernel v4.1 recipe for 
Leaf Hill BSP

Hi,

I have found some issue where I can't override the existing kernel configs on 
kernel-meta using my custom .cfg and .scc files in my custom layer.
We have been using KERNEL_FEATURES in the recipe to parse .scc from 
yocto-kernel-cache and this has caused the issue of configs unable to override 
with custom layer.

I have shared my issue with Bruce Ashfield (maintainer of linux-yocto) and he 
suggested the following fix in the kernel recipe.

I have verified the fix and I am able to change the kernel configs by supplying 
my own .cfg and .scc file in my custom meta layer.

The second patch is to update the SRCREV of machine branch for Leaf Hill BSP.

Please review and provide your feedback if you have any.
This patch is targeted for meta-intel branch jethro only.

Thank you.

Regards,
Rebecca


Rebecca Chang Swee Fun (2):
  linux-yocto_4.1: use BSP_SUBTYPE for BSP specific configuration
  linux-yocto_4.1: bump up machine branch source revision to latest

 common/recipes-kernel/linux/linux-yocto_4.1.bbappend | 8 
 conf/machine/intel-corei7-64.conf| 2 +-
 2 files changed, 5 insertions(+), 5 deletions(-)

--
1.9.1

--
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel
-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

Re: [meta-intel] [jethro] [PATCHv3 0/2] Add new bsp consolidated with Intel Common BSP

[Chang, Rebecca Swee Fun]

Hi all,

Any update on this patchset? Any feedback?

Regards,
Rebecca

-Original Message-
From: meta-intel-boun...@yoctoproject.org 
[mailto:meta-intel-boun...@yoctoproject.org] On Behalf Of Rebecca Chang Swee Fun
Sent: Tuesday, September 13, 2016 9:18 AM
To: meta-intel@yoctoproject.org
Cc: Zhang, Jianxun 
Subject: [meta-intel] [jethro] [PATCHv3 0/2] Add new bsp consolidated with 
Intel Common BSP

Hi,

PATCHv3 Change log:
- Remove runlevel 3 settings from machine conf

The v3 changes are tested working on both Leaf Hill (Broxton) and Cherry Hill 
(Braswell) that has different console port setup.

Regards,
Rebecca

PATCHv2 Change log:
- Changed machine configuration settings based on reviewers' feedback
  and comments.
- Append more console settings to SERIAL_CONSOLES
- Added SERIAL_CONSOLES_CHECK to stop getty from trying to enable
  non-existent serial consoles.

PATCHv1 Cover Letter:
This is to add leafhill as one of the BSP supported by Intel Common.
Since we need leafhill bsp to have a fixed kernel version base, we have setup a 
kernel branch in linux-yocto-4.1 dedicated for leafhill.

On the meta recipe side, we have used bb.utils.contains() to enable leafhill as 
KERNEL_FEATURES which to be set in local.conf by leaf hill BSP users.

This implementation has allow us to enable more settings without creating new 
machines conf file.

This change has been verified with build test and boot up test on Leaf Hill 
boards.

Please review and provide feedback if you have any.
The patches are targeted for merging into meta-intel Jethro branch.

Thanks and regards,
Rebecca

Rebecca Chang Swee Fun (2):
  intel-corei7-64: add machine configurations specific to leafhill bsp
  linux-yocto_4.1: use bb.utils.contains for KERNEL_FEATURES selection

 common/recipes-kernel/linux/linux-yocto_4.1.bbappend | 11 +--
 conf/machine/intel-corei7-64.conf|  6 --
 2 files changed, 9 insertions(+), 8 deletions(-)

--
1.9.1

--
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel
-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

Re: [meta-intel] [jethro] [PATCHv2 1/2] intel-corei7-64: add machine configurations specific to leafhill bsp

[Chang, Rebecca Swee Fun]

After checking with the developers, runlevel 3 is meant for internal testing 
purposes.
I will push another version of patchset to fix this. Thank you.

Rebecca

-Original Message-
From: Saul Wold [mailto:s...@linux.intel.com] 
Sent: Friday, September 9, 2016 10:34 PM
To: Chang, Rebecca Swee Fun <rebecca.swee.fun.ch...@intel.com>; 
meta-intel@yoctoproject.org
Cc: Sullivan, California L <california.l.sulli...@intel.com>; Zhang, Jianxun 
<jianxun.zh...@intel.com>
Subject: Re: [jethro] [PATCHv2 1/2] intel-corei7-64: add machine configurations 
specific to leafhill bsp

On Fri, 2016-09-09 at 09:39 +0800, Rebecca Chang Swee Fun wrote:
> We would like to enable new BSP for Intel Atom E3900 SoC based 
> platforms.
> This will help us to consolidate BSP into intel-common and we can use 
> KERNEL_FEATURES to select target BSP to compile.
> 
> Leaf Hill uses different serial console port setup. Hence this 
> mechanism are in place to enable new bsp with existing machine 
> configurations file.
> 
> Signed-off-by: Rebecca Chang Swee Fun <rebecca.swee.fun.chang@intel.c
> om>
> ---
>  conf/machine/intel-corei7-64.conf | 6 --
>  1 file changed, 4 insertions(+), 2 deletions(-)
> 
> diff --git a/conf/machine/intel-corei7-64.conf b/conf/machine/intel- 
> corei7-64.conf index cc16d62..aac14d1 100644
> --- a/conf/machine/intel-corei7-64.conf
> +++ b/conf/machine/intel-corei7-64.conf
> @@ -30,5 +30,7 @@ XSERVER ?= "${XSERVER_X86_BASE} \
> "
>  
>  SYSLINUX_OPTS = "serial 0 115200"
> -SERIAL_CONSOLE = "115200 ttyS0"
> -APPEND += "console=ttyS0,115200 console=tty0"
> +SERIAL_CONSOLES = "115200;ttyS2 115200;ttyS0"
> +SERIAL_CONSOLES_CHECK = "ttyS2 ttyS0"
Thanks for looking into this and using this paradigm here, this makes it more 
flexible to multiple boards and devices.

> +APPEND += "console=ttyS2,115200n8 console=ttyS0,115200 console=tty0"
> +APPEND += "${@bb.utils.contains('KERNEL_FEATURES', 'leafhill', '3
> reboot=efi kmemleak=off i915.enable_ipc=1', '', d)}"
Do you intend to hardcode  runlevel 3 for this device, this is the default 
runlevel, why is this needed?

Sau!

-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

Re: [meta-intel] [master] [krogoth] [PATCH] Fix QA issue on intel-gpu-tools

[Chang, Rebecca Swee Fun]

I have double checked and found this issue were only reproducible with Jethro.
So, I guess this patch will not be accepted for master/krogoth. Thanks.

Regards,
Rebecca

-Original Message-
From: Zanussi, Tom 
Sent: Wednesday, June 8, 2016 4:01 AM
To: Chang, Rebecca Swee Fun <rebecca.swee.fun.ch...@intel.com>; 
meta-intel@yoctoproject.org
Cc: Wold, Saul <saul.w...@intel.com>; Sullivan, California L 
<california.l.sulli...@intel.com>
Subject: Re: [meta-intel] [master] [krogoth] [PATCH] Fix QA issue on 
intel-gpu-tools

Hi Rebecca,

On 06/07/2016 01:19 AM, Chang, Rebecca Swee Fun wrote:
> Hi all,
> 
> Any comments on this patch?
> 

Can you please send detailed info on how to reproduce this build?  I can't see 
the QA error you mention in either krogoth or master.

In fact, I don't see a packages-split/intel-gpu-tools-benchmarks/usr/lib
directory at all, not to mention a .debug directory there.

Thanks,

Tom

> Regards,
> Rebecca
> 
> -Original Message-
> From: meta-intel-boun...@yoctoproject.org 
> [mailto:meta-intel-boun...@yoctoproject.org] On Behalf Of Rebecca 
> Chang Swee Fun
> Sent: Monday, May 30, 2016 3:41 PM
> To: meta-intel@yoctoproject.org
> Cc: california.sulli...@intel.com; Wold, Saul <saul.w...@intel.com>
> Subject: [meta-intel] [master] [krogoth] [PATCH] Fix QA issue on 
> intel-gpu-tools
> 
> Hi,
> 
> I have encountered bitbake QA issue error when compiling IGT v1.14 into image.
> 
> I have it fixed by declaring that .debug goes to ${PN}-dbg package.
> 
> ...
> ERROR: QA Issue: non debug package contains .debug directory: 
> intel-gpu-tools-benchmarks path 
> work/corei7-64-poky-linux/intel-gpu-tools/1.14-r0/packages-split/intel
> -gpu-tools-benchmarks/usr/lib/intel-gpu-tools/intel-gpu-tools/benchmar
> ks/.debug/gem_mmap [debug-files]
> ERROR: QA run found fatal errors. Please consider fixing them.
> ERROR: Function failed: do_package_qa
> ...
> 
> Please review whether this fix is proper and feedback for rework if 
> necessary. Else, please merge this fix for master and krogoth branch.
> 
> Thank you very much.
> 
> Regards,
> Rebecca
> 
> Rebecca Chang Swee Fun (1):
>   intel-gpu-tools_1.14: fix bitbake QA issue on debug-files
> 
>  common/recipes-graphics/intel-gpu-tools/intel-gpu-tools_1.14.bb | 2 
> ++
>  1 file changed, 2 insertions(+)
> 
> --
> 1.9.1
> 
> --
> ___
> meta-intel mailing list
> meta-intel@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-intel
> 

-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

Re: [meta-intel] [master] [krogoth] [PATCH] Fix QA issue on intel-gpu-tools

[Chang, Rebecca Swee Fun]

Hi all,

Any comments on this patch?

Regards,
Rebecca

-Original Message-
From: meta-intel-boun...@yoctoproject.org 
[mailto:meta-intel-boun...@yoctoproject.org] On Behalf Of Rebecca Chang Swee Fun
Sent: Monday, May 30, 2016 3:41 PM
To: meta-intel@yoctoproject.org
Cc: california.sulli...@intel.com; Wold, Saul 
Subject: [meta-intel] [master] [krogoth] [PATCH] Fix QA issue on intel-gpu-tools

Hi,

I have encountered bitbake QA issue error when compiling IGT v1.14 into image.

I have it fixed by declaring that .debug goes to ${PN}-dbg package.

...
ERROR: QA Issue: non debug package contains .debug directory: 
intel-gpu-tools-benchmarks path 
work/corei7-64-poky-linux/intel-gpu-tools/1.14-r0/packages-split/intel-gpu-tools-benchmarks/usr/lib/intel-gpu-tools/intel-gpu-tools/benchmarks/.debug/gem_mmap
 [debug-files]
ERROR: QA run found fatal errors. Please consider fixing them.
ERROR: Function failed: do_package_qa
...

Please review whether this fix is proper and feedback for rework if necessary. 
Else, please merge this fix for master and krogoth branch.

Thank you very much.

Regards,
Rebecca

Rebecca Chang Swee Fun (1):
  intel-gpu-tools_1.14: fix bitbake QA issue on debug-files

 common/recipes-graphics/intel-gpu-tools/intel-gpu-tools_1.14.bb | 2 ++
 1 file changed, 2 insertions(+)

--
1.9.1

--
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel
-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

Re: [meta-intel] Intel Atom E3845: Backlight control

[Chang, Rebecca Swee Fun]

Hi Vincent/ Azril,

Can you help to provide advice to Pj?
Thanks.

Regards,
Rebecca

From: meta-intel-boun...@yoctoproject.org 
[mailto:meta-intel-boun...@yoctoproject.org] On Behalf Of Prasant J
Sent: Wednesday, November 25, 2015 8:46 PM
To: meta-intel@yoctoproject.org
Subject: [meta-intel] Intel Atom E3845: Backlight control

Hi,
I'm using Intel Atom E3845 with my custom hardware. I have an LVDS display and 
I would like to control the brightness from the linux shell.
I used the command:
xrandr --output DP2 --brightness 
This command (I think) changes the gamma factor of the display but the actual 
back light intensity is not changed.

I tried changing the value of:
/sys/devices/pci:00/:00:02.0/backlight/acpi_video0/brightness
but still no change in the back light intensity.

Any inputs on how can I control the back light intensity of my LVDS display?

Regards, Pj


-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

[meta-intel] [PATCH] linux-yocto-3.19: update SRCREV for linux-yocto-3.19

[Chang Rebecca Swee Fun]

Hi,

This patch is to update the current linux-yocto-3.19 kernel recipe
bbappend file to include commits submitted to standard/base.
The patches will enable S3 power management for i915 driver and
enable idle driver for Cherry Hill.

We have tested the SRCREV on our Cherry Hill setup and verified that
the features to be included are enabled.

This patch is targeted to be merge into fido branch. Please provide
feedback if you have any.

Thank you very much.

Regards,
Rebecca

Chang Rebecca Swee Fun (1):
  linux-yocto_3.19: Update SRCREV to include driver update

 common/recipes-kernel/linux/linux-yocto_3.19.bbappend | 8 
 1 file changed, 4 insertions(+), 4 deletions(-)

-- 
1.9.1

-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

[meta-intel] [PATCH] linux-yocto_3.19: Update SRCREV to include driver update

[Chang Rebecca Swee Fun]

Update SRCREV for linux-yocto-3.19 to include the following commits:

e152349 drm/i915: Reset CSB read pointer in ring init
a87a6ff drm/i915/bdw: Enable execlists by default where supported
6c21811 fs: aufs: fix a build error for archs which doesn't support MUTEX_SPIN_
f7e6e36 fs: yaffs2: kill f_dentry uses
2a5e3b1 intel_idle: Add support for the Airmont Core in the Cherrytrail and Bra
28c0578 intel_idle: Update support for Silvermont Core in Baytrail SOC
77bec57 intel_idle: Add -enter_freeze callbacks
ae682f3 intel_idle: support additional Broadwell model
3c88608 PM / sleep: Make it possible to quiesce timers during suspend-to-idle
cd240b6 PM / sleep: Re-implement suspend-to-idle handling
d3c0b95 drm/i915: New offset for reading frequencies on CHV.
dac6bab drm/i915/chv: Populate total EU count on Cherryview
a3f6f39 arm64: psci: move psci firmware calls out of line
374b5d0 drm/i915: Only wait for required lanes in vlv_wait_port_ready()
fca99e8 Revert drm/i915: Hack to tie both common lanes together on chv
00682f3 drm/i915: Work around DISPLAY_PHY_CONTROL register corruption on CHV
654b1a4 drm/i915: Implement chv display PHY lane stagger setup

Signed-off-by: Chang Rebecca Swee Fun rebecca.swee.fun.ch...@intel.com
---
 common/recipes-kernel/linux/linux-yocto_3.19.bbappend | 8 
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/common/recipes-kernel/linux/linux-yocto_3.19.bbappend 
b/common/recipes-kernel/linux/linux-yocto_3.19.bbappend
index acdf5ef..36cec32 100644
--- a/common/recipes-kernel/linux/linux-yocto_3.19.bbappend
+++ b/common/recipes-kernel/linux/linux-yocto_3.19.bbappend
@@ -5,16 +5,16 @@ KERNEL_FEATURES_INTEL_COMMON += features/amt/mei/mei.scc
 
 LINUX_VERSION_core2-32-intel-common = 3.19.5
 COMPATIBLE_MACHINE_core2-32-intel-common = ${MACHINE}
-SRCREV_meta_core2-32-intel-common = 7215fe431391a322c7e39f410e7b8f2a2b507892
-SRCREV_machine_core2-32-intel-common = 
0befa35f40997c90936047e57fbbdd7edbf7e525
+SRCREV_meta_core2-32-intel-common = 118f27167f4626fc7c71cefbec7c55a41d3a6d62
+SRCREV_machine_core2-32-intel-common = 
e152349de59b43b2a75f2c332b44171df461d5a0
 KMACHINE_core2-32-intel-common = intel-core2-32
 KBRANCH_core2-32-intel-common = standard/base
 KERNEL_FEATURES_append_core2-32-intel-common = 
${KERNEL_FEATURES_INTEL_COMMON}
 
 LINUX_VERSION_corei7-64-intel-common = 3.19.5
 COMPATIBLE_MACHINE_corei7-64-intel-common = ${MACHINE}
-SRCREV_meta_corei7-64-intel-common = 7215fe431391a322c7e39f410e7b8f2a2b507892
-SRCREV_machine_corei7-64-intel-common = 
0befa35f40997c90936047e57fbbdd7edbf7e525
+SRCREV_meta_corei7-64-intel-common = 118f27167f4626fc7c71cefbec7c55a41d3a6d62
+SRCREV_machine_corei7-64-intel-common = 
e152349de59b43b2a75f2c332b44171df461d5a0
 KMACHINE_corei7-64-intel-common = intel-corei7-64
 KBRANCH_corei7-64-intel-common = standard/base
 KERNEL_FEATURES_append_corei7-64-intel-common = 
${KERNEL_FEATURES_INTEL_COMMON}
-- 
1.9.1

-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

Re: [meta-intel] Building Haswell BSP

[Chang, Rebecca Swee Fun]

Hi,

Haswell layer has moved into meta-isg since Yocto Project v1.5 (Dora).

You can download the latest version for Haswell support from the link below:
https://www.yoctoproject.org/downloads/bsps/daisy161/haswell

It is based on Yocto Project v1.6.1.

Regards,
Rebecca

From: meta-intel-boun...@yoctoproject.org 
[mailto:meta-intel-boun...@yoctoproject.org] On Behalf Of Chris Trobridge
Sent: 20 May, 2015 5:19 PM
To: meta-intel@yoctoproject.org
Subject: [meta-intel] Building Haswell BSP

Hi,

I've just received some new hardware with a Sharkbay motherboard and I am 
trying to get the Haswell BSP (meta-haswell) built for it.

I can see this BSP was introduced in Dylan but was not maintained in later 
branches so it does not appear in any currently active branch, although it is 
still referenced in patches.

Hob fails to parse the Haswell layer as it includes tune-x86_64.inc.

This was removed in http://patchwork.openembedded.org/patch/65457/ .

As a start I am considering how the other intel BSPs have changed in the most 
recent branch and applying those changes to the Haswell BSP.

What's the recommended way to use a BSP that's no longer supported, and why was 
Haswell only supported in one branch?

Regards,
Chris

Ultra Electronics AEP is a trading name of Ultra Electronics Ltd. This email 
and any attachments to it are confidential to the intended recipient and may 
also be privileged. If you have received it in error please notify the sender 
and delete it from your system. If you are not the intended recipient you must 
not copy it or use it for any purpose nor disclose or distribute its contents 
to any other person. All communications may be subject to interception or 
monitoring for operational and/or security purposes. Please rely on your own 
virus checking as the sender cannot accept any liability for any damage arising 
from any bug or virus infection. Ultra Electronics Ltd is a company registered 
in England and Wales, registration number 02830644. The Registered office 
address is 417 Bridport Road, Greenford, Middlesex, UB6 8UA.


This email message has been delivered safely and archived online by Mimecast.
For more information please visit http://www.mimecast.com

-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

[meta-intel] FW: [meta-intel-iot-devkit] [PATCH 0/5] Adding missing kernel configurations for meta-intel-iot-devkit

[Chang, Rebecca Swee Fun]

Hi Brendan,

Have you got the chance to review this patchset? We have enhanced the 
configurations to include some missing kernel config we found in our tests.

Regards,
Rebecca

-Original Message-
From: meta-intel-boun...@yoctoproject.org 
[mailto:meta-intel-boun...@yoctoproject.org] On Behalf Of Chang Rebecca Swee Fun
Sent: 30 April, 2015 6:45 PM
To: meta-intel@yoctoproject.org
Cc: Ramajayam, Yugeraj
Subject: [meta-intel] [meta-intel-iot-devkit] [PATCH 0/5] Adding missing kernel 
configurations for meta-intel-iot-devkit

This patchset was intended to add in some important kernel configurations that 
are found missing in the final configuration
(.config) file of linux-yocto-quark kernel.
Some kernel modules were not loaded properly due to these missing kernel 
configurations.

The missing kernel configurations in the final .config was cross-checked with 
LTSI kernel version 3.14 to track their dependencies.

The root cause is due to missing dependent kernel config that was excluded from 
the .cfg files under meta-intel-iot-devkit/
recipes-kernel/linux/linux-yocto-quark/iot-devkit*

This patches were build tested and verified that the feature provided by the 
kernel configurations are now functioning.

This patchset was target to be merge into master if there is no further concern.

Thanks.

Regards,
Rebecca

YUGERAJ RAMAJAYAM (5):
  linux-yocto-quark: Added CONFIG_USB_NET_RNDIS_WLAN=m to usb-net.cfg
  linux-yocto-quark: Added CONFIG_HW_RANDOM=m and CONFIG_B43_BCMA=m
  linux-yocto-quark: Added CONFIG_IP_ADVANCED_ROUTER=m to
netfilter-small-3.8.cfg
  linux-yocto-quark: Added CONFIG_USB_MASS_STORAGE=m to
usb-eth-gadget.cfg
  linux-yocto-quark: Added CONFIG_RTL_CARDS=m to wlan-realtek.cfg

 .../linux/linux-yocto-quark/iot-devkit-spi/netfilter-small-3.8.cfg  | 1 +
 recipes-kernel/linux/linux-yocto-quark/iot-devkit-spi/usb-net.cfg   | 1 +
 recipes-kernel/linux/linux-yocto-quark/iot-devkit-spi/wlan-broadcom.cfg | 2 ++ 
 recipes-kernel/linux/linux-yocto-quark/iot-devkit-spi/wlan-realtek.cfg  | 1 +
 .../linux/linux-yocto-quark/iot-devkit/netfilter-small-3.8.cfg  | 1 +
 recipes-kernel/linux/linux-yocto-quark/iot-devkit/usb-eth-gadget.cfg| 2 +-
 recipes-kernel/linux/linux-yocto-quark/iot-devkit/usb-net.cfg   | 1 +
 recipes-kernel/linux/linux-yocto-quark/iot-devkit/wlan-broadcom.cfg | 2 ++
 recipes-kernel/linux/linux-yocto-quark/iot-devkit/wlan-realtek.cfg  | 1 +
 9 files changed, 11 insertions(+), 1 deletion(-)

--
1.9.1

--
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel
-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

Re: [meta-intel] [meta-intel-galileo] [PATCH 2/3] launcher.sh: start clloader only on galileo

[Chang, Rebecca Swee Fun]

Hi Brendan,

Has this series of patches being merged? Sorry if I sounded a bit pushing you. 
If you have any concern about the patchset, please feedback to us so that we 
can revert it as soon as possible.

Thanks.

Regards,
Rebecca

 -Original Message-
 From: Le Foll, Brendan
 Sent: 02 May, 2015 12:46 AM
 To: Chang, Rebecca Swee Fun
 Cc: meta-intel@yoctoproject.org; Ong, Boon Leong; Ahmad, Josef
 Subject: Re: [meta-intel] [meta-intel-galileo] [PATCH 2/3] launcher.sh: start
 clloader only on galileo
 
 On Thu, Apr 30, 2015 at 07:32:10PM +0800,
 rebecca.swee.fun.ch...@intel.com wrote:
  From: Josef Ahmad josef.ah...@intel.com
 
  Add the dmidecode logic that comes from galileod.sh to launcher.sh.
  At the moment this is pure duplication.
 
  Signed-off-by: Josef Ahmad josef.ah...@intel.com
  Reviewed-by: Ong Boon Leong boon.leong@intel.com
  Tested-by: Ong Boon Leong boon.leong@intel.com
  Signed-off-by: Chang Rebecca Swee Fun
  rebecca.swee.fun.ch...@intel.com
  ---
   recipes-galileo/galileo-target/files/launcher.sh | 32
  ++--
   1 file changed, 25 insertions(+), 7 deletions(-)
 
  diff --git a/recipes-galileo/galileo-target/files/launcher.sh
  b/recipes-galileo/galileo-target/files/launcher.sh
  index 50fa378..a166345 100755
  --- a/recipes-galileo/galileo-target/files/launcher.sh
  +++ b/recipes-galileo/galileo-target/files/launcher.sh
  @@ -11,11 +11,29 @@ mytrap()
 
   trap 'mytrap' USR1
 
  -keepgoing=true
  -while $keepgoing
  -do
  -  $CLLOADER $CLLOADER_OPTS  /dev/ttyGS0  /dev/ttyGS0  clPID=$!
  -  wait $clPID
  -  usleep 20
  -done
  +arduino_services()
  +{
  +  keepgoing=true
  +  while $keepgoing
  +  do
  +  $CLLOADER $CLLOADER_OPTS  /dev/ttyGS0  /dev/ttyGS0  clPID=$!
  +  wait $clPID
  +  usleep 20
  +  done
  +}
  +
  +galileo_board=false
  +type dmidecode  /dev/null 21 || die dmidecode not installed
  +board=$(dmidecode -s baseboard-product-name) case $board in
  +*Galileo )
  +   galileo_board=true
  +   ;;
  +*GalileoGen2 )
  +   galileo_board=true
  +   ;;
  +esac
 
 This logic is duplicated in so many places it's untrue. I wish someone would 
 go
 through and remove them so we just do this kind of hack once.
 Also you don't need to call dmidecode, you can just read in sysfs...
 
 Anyways for the sake of time I applied the series anyways.
 
 Cheers,
 Brendan
-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

[meta-intel] [meta-intel-iot-devkit] [PATCH 0/5] Adding missing kernel configurations for meta-intel-iot-devkit

[Chang Rebecca Swee Fun]

This patchset was intended to add in some important kernel
configurations that are found missing in the final configuration
(.config) file of linux-yocto-quark kernel.
Some kernel modules were not loaded properly due to these
missing kernel configurations.

The missing kernel configurations in the final .config was
cross-checked with LTSI kernel version 3.14 to track their
dependencies.

The root cause is due to missing dependent kernel config that
was excluded from the .cfg files under meta-intel-iot-devkit/
recipes-kernel/linux/linux-yocto-quark/iot-devkit*

This patches were build tested and verified that the feature
provided by the kernel configurations are now functioning.

This patchset was target to be merge into master if there
is no further concern.

Thanks.

Regards,
Rebecca

YUGERAJ RAMAJAYAM (5):
  linux-yocto-quark: Added CONFIG_USB_NET_RNDIS_WLAN=m to usb-net.cfg
  linux-yocto-quark: Added CONFIG_HW_RANDOM=m and CONFIG_B43_BCMA=m
  linux-yocto-quark: Added CONFIG_IP_ADVANCED_ROUTER=m to
netfilter-small-3.8.cfg
  linux-yocto-quark: Added CONFIG_USB_MASS_STORAGE=m to
usb-eth-gadget.cfg
  linux-yocto-quark: Added CONFIG_RTL_CARDS=m to wlan-realtek.cfg

 .../linux/linux-yocto-quark/iot-devkit-spi/netfilter-small-3.8.cfg  | 1 +
 recipes-kernel/linux/linux-yocto-quark/iot-devkit-spi/usb-net.cfg   | 1 +
 recipes-kernel/linux/linux-yocto-quark/iot-devkit-spi/wlan-broadcom.cfg | 2 ++
 recipes-kernel/linux/linux-yocto-quark/iot-devkit-spi/wlan-realtek.cfg  | 1 +
 .../linux/linux-yocto-quark/iot-devkit/netfilter-small-3.8.cfg  | 1 +
 recipes-kernel/linux/linux-yocto-quark/iot-devkit/usb-eth-gadget.cfg| 2 +-
 recipes-kernel/linux/linux-yocto-quark/iot-devkit/usb-net.cfg   | 1 +
 recipes-kernel/linux/linux-yocto-quark/iot-devkit/wlan-broadcom.cfg | 2 ++
 recipes-kernel/linux/linux-yocto-quark/iot-devkit/wlan-realtek.cfg  | 1 +
 9 files changed, 11 insertions(+), 1 deletion(-)

-- 
1.9.1

-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

[meta-intel] [meta-intel-iot-devkit] [PATCH 1/5] linux-yocto-quark: Added CONFIG_USB_NET_RNDIS_WLAN=m to usb-net.cfg

[Chang Rebecca Swee Fun]

From: YUGERAJ RAMAJAYAM yugeraj.ramaja...@intel.com

Added CONFIG_USB_NET_RNDIS_WLAN=m to usb-net.cfg.

CONFIG_USB_USBNET requires CONFIG_USB_NET_RNDIS_WLAN to be enabled in kernel
configuration.

Signed-off-by: YUGERAJ RAMAJAYAM yugeraj.ramaja...@intel.com
Signed-off-by: Chang Rebecca Swee Fun rebecca.swee.fun.ch...@intel.com
---
 recipes-kernel/linux/linux-yocto-quark/iot-devkit-spi/usb-net.cfg | 1 +
 recipes-kernel/linux/linux-yocto-quark/iot-devkit/usb-net.cfg | 1 +
 2 files changed, 2 insertions(+)

diff --git a/recipes-kernel/linux/linux-yocto-quark/iot-devkit-spi/usb-net.cfg 
b/recipes-kernel/linux/linux-yocto-quark/iot-devkit-spi/usb-net.cfg
index 0501130..69a2e70 100644
--- a/recipes-kernel/linux/linux-yocto-quark/iot-devkit-spi/usb-net.cfg
+++ b/recipes-kernel/linux/linux-yocto-quark/iot-devkit-spi/usb-net.cfg
@@ -12,3 +12,4 @@
 #CONFIG_USB_NET_CDC_SUBSET=m
 #CONFIG_USB_NET_ZAURUS=m
 #CONFIG_USB_NET_INT51X1=m
+#CONFIG_USB_NET_RNDIS_WLAN=m
diff --git a/recipes-kernel/linux/linux-yocto-quark/iot-devkit/usb-net.cfg 
b/recipes-kernel/linux/linux-yocto-quark/iot-devkit/usb-net.cfg
index 45da619..eb00e49 100644
--- a/recipes-kernel/linux/linux-yocto-quark/iot-devkit/usb-net.cfg
+++ b/recipes-kernel/linux/linux-yocto-quark/iot-devkit/usb-net.cfg
@@ -12,3 +12,4 @@ CONFIG_USB_NET_MCS7830=m
 CONFIG_USB_NET_CDC_SUBSET=m
 CONFIG_USB_NET_ZAURUS=m
 CONFIG_USB_NET_INT51X1=m
+CONFIG_USB_NET_RNDIS_WLAN=m
-- 
1.9.1

-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

[meta-intel] [meta-intel-iot-devkit] [PATCH 3/5] linux-yocto-quark: Added CONFIG_IP_ADVANCED_ROUTER=m to netfilter-small-3.8.cfg

[Chang Rebecca Swee Fun]

From: YUGERAJ RAMAJAYAM yugeraj.ramaja...@intel.com

Added CONFIG_IP_ADVANCED_ROUTER=m to netfilter-small-3.8.cfg.

CONFIG_IP_MULTIPLE_TABLES requires CONFIG_IP_ADVANCED_ROUTER to be enabled
in kernel configuration.

Signed-off-by: YUGERAJ RAMAJAYAM yugeraj.ramaja...@intel.com
Signed-off-by: Chang Rebecca Swee Fun rebecca.swee.fun.ch...@intel.com
---
 .../linux/linux-yocto-quark/iot-devkit-spi/netfilter-small-3.8.cfg   | 1 +
 .../linux/linux-yocto-quark/iot-devkit/netfilter-small-3.8.cfg   | 1 +
 2 files changed, 2 insertions(+)

diff --git 
a/recipes-kernel/linux/linux-yocto-quark/iot-devkit-spi/netfilter-small-3.8.cfg 
b/recipes-kernel/linux/linux-yocto-quark/iot-devkit-spi/netfilter-small-3.8.cfg
index 2def700..f87900f 100644
--- 
a/recipes-kernel/linux/linux-yocto-quark/iot-devkit-spi/netfilter-small-3.8.cfg
+++ 
b/recipes-kernel/linux/linux-yocto-quark/iot-devkit-spi/netfilter-small-3.8.cfg
@@ -21,3 +21,4 @@
 #CONFIG_NETFILTER_XT_CONNMARK=m
 #CONFIG_NETFILTER_XT_TARGET_CONNMARK=m
 #CONFIG_NETFILTER_XT_MATCH_CONNMARK=m
+#CONFIG_IP_ADVANCED_ROUTER=m
diff --git 
a/recipes-kernel/linux/linux-yocto-quark/iot-devkit/netfilter-small-3.8.cfg 
b/recipes-kernel/linux/linux-yocto-quark/iot-devkit/netfilter-small-3.8.cfg
index e9b71c4..69328b2 100644
--- a/recipes-kernel/linux/linux-yocto-quark/iot-devkit/netfilter-small-3.8.cfg
+++ b/recipes-kernel/linux/linux-yocto-quark/iot-devkit/netfilter-small-3.8.cfg
@@ -21,3 +21,4 @@ CONFIG_NETFILTER_XT_MATCH_NFACCT=m
 CONFIG_NETFILTER_XT_CONNMARK=m
 CONFIG_NETFILTER_XT_TARGET_CONNMARK=m
 CONFIG_NETFILTER_XT_MATCH_CONNMARK=m
+CONFIG_IP_ADVANCED_ROUTER=m
-- 
1.9.1

-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

[meta-intel] [meta-intel-iot-devkit] [PATCH 2/5] linux-yocto-quark: Added CONFIG_HW_RANDOM=m and CONFIG_B43_BCMA=m

[Chang Rebecca Swee Fun]

From: YUGERAJ RAMAJAYAM yugeraj.ramaja...@intel.com

Added CONFIG_HW_RANDOM=m and CONFIG_B43_BCMA=m to wlan-broadcom.cfg.

CONFIG_B43_HWRNG requires CONFIG_HW_RANDOM to be enabled in kernel 
configuration.
CONFIG_B43_PHY_HT requires CONFIG_B43_BCMA to be enabled in kernel 
configuration.

Signed-off-by: YUGERAJ RAMAJAYAM yugeraj.ramaja...@intel.com
Signed-off-by: Chang Rebecca Swee Fun rebecca.swee.fun.ch...@intel.com
---
 recipes-kernel/linux/linux-yocto-quark/iot-devkit-spi/wlan-broadcom.cfg | 2 ++
 recipes-kernel/linux/linux-yocto-quark/iot-devkit/wlan-broadcom.cfg | 2 ++
 2 files changed, 4 insertions(+)

diff --git 
a/recipes-kernel/linux/linux-yocto-quark/iot-devkit-spi/wlan-broadcom.cfg 
b/recipes-kernel/linux/linux-yocto-quark/iot-devkit-spi/wlan-broadcom.cfg
index 374fd87..272d58a 100644
--- a/recipes-kernel/linux/linux-yocto-quark/iot-devkit-spi/wlan-broadcom.cfg
+++ b/recipes-kernel/linux/linux-yocto-quark/iot-devkit-spi/wlan-broadcom.cfg
@@ -22,3 +22,5 @@
 #CONFIG_SSB_SDIOHOST=y
 #CONFIG_SSB_DRIVER_PCICORE_POSSIBLE=y
 #CONFIG_SSB_DRIVER_PCICORE=y
+#CONFIG_HW_RANDOM=m
+#CONFIG_B43_BCMA=m
diff --git 
a/recipes-kernel/linux/linux-yocto-quark/iot-devkit/wlan-broadcom.cfg 
b/recipes-kernel/linux/linux-yocto-quark/iot-devkit/wlan-broadcom.cfg
index 3361e8b..7e08eef 100644
--- a/recipes-kernel/linux/linux-yocto-quark/iot-devkit/wlan-broadcom.cfg
+++ b/recipes-kernel/linux/linux-yocto-quark/iot-devkit/wlan-broadcom.cfg
@@ -22,3 +22,5 @@ CONFIG_SSB_SDIOHOST_POSSIBLE=y
 CONFIG_SSB_SDIOHOST=y
 CONFIG_SSB_DRIVER_PCICORE_POSSIBLE=y
 CONFIG_SSB_DRIVER_PCICORE=y
+CONFIG_HW_RANDOM=m
+CONFIG_B43_BCMA=m
-- 
1.9.1

-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

[meta-intel] [meta-intel-iot-devkit] [PATCH 0/5] Adding missing kernel configurations for meta-intel-iot-devkit

[Chang Rebecca Swee Fun]

This patchset was intended to add in some important kernel
configurations that are found missing in the final configuration
(.config) file of linux-yocto-quark kernel.
Some kernel modules were not loaded properly due to these
missing kernel configurations.

The missing kernel configurations in the final .config was
cross-checked with LTSI kernel version 3.14 to track their
dependencies.

The root cause is due to missing dependent kernel config that
was excluded from the .cfg files under meta-intel-iot-devkit/
recipes-kernel/linux/linux-yocto-quark/iot-devkit*

This patches were build tested and verified that the feature
provided by the kernel configurations are now functioning.

This patchset was target to be merge into master if there
is no further concern.

Thanks.

Regards,
Rebecca

YUGERAJ RAMAJAYAM (5):
  linux-yocto-quark: Added CONFIG_USB_NET_RNDIS_WLAN=m to usb-net.cfg
  linux-yocto-quark: Added CONFIG_HW_RANDOM=m and CONFIG_B43_BCMA=m
  linux-yocto-quark: Added CONFIG_IP_ADVANCED_ROUTER=m to
netfilter-small-3.8.cfg
  linux-yocto-quark: Added CONFIG_USB_MASS_STORAGE=m to
usb-eth-gadget.cfg
  linux-yocto-quark: Added CONFIG_RTL_CARDS=m to wlan-realtek.cfg

 .../linux/linux-yocto-quark/iot-devkit-spi/netfilter-small-3.8.cfg  | 1 +
 recipes-kernel/linux/linux-yocto-quark/iot-devkit-spi/usb-net.cfg   | 1 +
 recipes-kernel/linux/linux-yocto-quark/iot-devkit-spi/wlan-broadcom.cfg | 2 ++
 recipes-kernel/linux/linux-yocto-quark/iot-devkit-spi/wlan-realtek.cfg  | 1 +
 .../linux/linux-yocto-quark/iot-devkit/netfilter-small-3.8.cfg  | 1 +
 recipes-kernel/linux/linux-yocto-quark/iot-devkit/usb-eth-gadget.cfg| 2 +-
 recipes-kernel/linux/linux-yocto-quark/iot-devkit/usb-net.cfg   | 1 +
 recipes-kernel/linux/linux-yocto-quark/iot-devkit/wlan-broadcom.cfg | 2 ++
 recipes-kernel/linux/linux-yocto-quark/iot-devkit/wlan-realtek.cfg  | 1 +
 9 files changed, 11 insertions(+), 1 deletion(-)

-- 
1.9.1

-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

[meta-intel] [meta-intel-iot-devkit] [PATCH 5/5] linux-yocto-quark: Added CONFIG_RTL_CARDS=m to wlan-realtek.cfg

[Chang Rebecca Swee Fun]

From: YUGERAJ RAMAJAYAM yugeraj.ramaja...@intel.com

Added CONFIG_RTL_CARDS=m to wlan-realtek.cfg.

The follwing kernel configuration depends on CONFIG_RTL_CARDS to be enabled
in kernel configuration:
CONFIG_RTLWIFI=m
CONFIG_RTLWIFI_DEBUG=n
CONFIG_RTL8723AE=m
CONFIG_RTL8192SE=m
CONFIG_RTL8192DE=m
CONFIG_RTL8192CU=m
CONFIG_RTL8192CE=m
CONFIG_RTL8192C_COMMON=m
CONFIG_RTL8188EE=m

Signed-off-by: YUGERAJ RAMAJAYAM yugeraj.ramaja...@intel.com
Signed-off-by: Chang Rebecca Swee Fun rebecca.swee.fun.ch...@intel.com
---
 recipes-kernel/linux/linux-yocto-quark/iot-devkit-spi/wlan-realtek.cfg | 1 +
 recipes-kernel/linux/linux-yocto-quark/iot-devkit/wlan-realtek.cfg | 1 +
 2 files changed, 2 insertions(+)

diff --git 
a/recipes-kernel/linux/linux-yocto-quark/iot-devkit-spi/wlan-realtek.cfg 
b/recipes-kernel/linux/linux-yocto-quark/iot-devkit-spi/wlan-realtek.cfg
index 8876217..5a81c9a 100644
--- a/recipes-kernel/linux/linux-yocto-quark/iot-devkit-spi/wlan-realtek.cfg
+++ b/recipes-kernel/linux/linux-yocto-quark/iot-devkit-spi/wlan-realtek.cfg
@@ -9,3 +9,4 @@
 #CONFIG_RTL8192DE=m
 #CONFIG_RTL8723AE=m
 #CONFIG_RTL8188EE=m
+#CONFIG_RTL_CARDS=m
diff --git a/recipes-kernel/linux/linux-yocto-quark/iot-devkit/wlan-realtek.cfg 
b/recipes-kernel/linux/linux-yocto-quark/iot-devkit/wlan-realtek.cfg
index d762950..aa8cb6f 100644
--- a/recipes-kernel/linux/linux-yocto-quark/iot-devkit/wlan-realtek.cfg
+++ b/recipes-kernel/linux/linux-yocto-quark/iot-devkit/wlan-realtek.cfg
@@ -9,3 +9,4 @@ CONFIG_RTL8192SE=m
 CONFIG_RTL8192DE=m
 CONFIG_RTL8723AE=m
 CONFIG_RTL8188EE=m
+CONFIG_RTL_CARDS=m
-- 
1.9.1

-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

Re: [meta-intel] [PATCH 1/1] meta-valleyisland: Update linux-yocto v3.10.40 SRCREV to v3.10.65

[Chang, Rebecca Swee Fun]

Reviewed-by: Chang Rebecca Swee Fun rebecca.swee.fun.ch...@intel.com

 -Original Message-
 From: meta-intel-boun...@yoctoproject.org [mailto:meta-intel-
 boun...@yoctoproject.org] On Behalf Of wei.tee...@intel.com
 Sent: 02 March, 2015 5:59 PM
 To: meta-intel@yoctoproject.org
 Subject: [meta-intel] [PATCH 1/1] meta-valleyisland: Update linux-yocto
 v3.10.40 SRCREV to v3.10.65
 
 From: Ng Wei Tee wei.tee...@intel.com
 
 Use the latest HEADs of the git branches from the linux-yocto
 v3.10 kernel repository.
 
 Signed-off-by: Ng Wei Tee wei.tee...@intel.com
 ---
  .../recipes-kernel/linux/linux-yocto_3.10.bbappend |   28 
 ++--
  1 file changed, 14 insertions(+), 14 deletions(-)
 
 diff --git a/meta-isg/meta-valleyisland/recipes-kernel/linux/linux-
 yocto_3.10.bbappend b/meta-isg/meta-valleyisland/recipes-kernel/linux/linux-
 yocto_3.10.bbappend
 index 084bb47..c262471 100644
 --- a/meta-isg/meta-valleyisland/recipes-kernel/linux/linux-
 yocto_3.10.bbappend
 +++ b/meta-isg/meta-valleyisland/recipes-kernel/linux/linux-
 yocto_3.10.bbappend
 @@ -7,15 +7,15 @@ COMPATIBLE_MACHINE_valleyisland-32 = valleyisland-
 32
  KMACHINE_valleyisland-32 = valleyisland-32
  KBRANCH_valleyisland-32 = standard/base
 
 -KERNEL_FEATURES_append_valleyisland-32 =  features/valleyisland-
 io/valleyisland-io \
 -
 features/valleyisland-io/valleyisland-
 io-pci
 +KERNEL_FEATURES_append_valleyisland-32 =  features/valleyisland-
 io/valleyisland-io.scc \
 +
 features/valleyisland-io/valleyisland-
 io-pci.scc
 
 -LINUX_VERSION_valleyisland-32 = 3.10.40
 -SRCREV_machine_valleyisland-32 =
 f53a6114b3a6e8c03ca4752de829887015f4c942
 -SRCREV_meta_valleyisland-32 =
 90edb289dccfe838d4e364e1a5815447a6642b98
 -SRCREV_valleyisland-io_valleyisland-32 =
 8ea4fb625f2654bbdd5dfcb9db67328d21ebe504
 +LINUX_VERSION_valleyisland-32 = 3.10.65
 +SRCREV_machine_valleyisland-32 =
 ef1b96279e1a087a9d5b6a0601830d42ea47355c
 +SRCREV_meta_valleyisland-32 =
 d5456dd830cad14bd844753b751b83744ced3793
 +SRCREV_vialleyisland-io_valleyisland-32 =
 0992d01f5f382f6da60004ef87f67ebd3ca13732
 
 -SRC_URI_valleyisland-32 = git://git.yoctoproject.org/linux-yocto-
 3.10.git;protocol=git;nocheckout=1;branch=${KBRANCH},${KMETA},valleyisland-
 io-1.0;name=machine,meta,valleyisland-io
 +SRC_URI_valleyisland-32 = git://git.yoctoproject.org/linux-yocto-
 3.10.git;protocol=git;nocheckout=1;branch=${KBRANCH},${KMETA},valleyisland-
 io-3.0;name=machine,meta,valleyisland-io
 
  #
  # MACHINE = valleyisland-64 #
 @@ -24,14 +24,14 @@ COMPATIBLE_MACHINE_valleyisland-64 =
 valleyisland-64
  KMACHINE_valleyisland-64 = valleyisland
  KBRANCH_valleyisland-64 = standard/base
 
 -KERNEL_FEATURES_append_valleyisland-64 =  features/valleyisland-
 io/valleyisland-io \
 -
 features/valleyisland-io/valleyisland-
 io-pci
 +KERNEL_FEATURES_append_valleyisland-64 =  features/valleyisland-
 io/valleyisland-io.scc \
 +
 features/valleyisland-io/valleyisland-
 io-pci.scc
 
 -LINUX_VERSION_valleyisland-64 = 3.10.40
 -SRCREV_machine_valleyisland-64 =
 f53a6114b3a6e8c03ca4752de829887015f4c942
 -SRCREV_meta_valleyisland-64 =
 90edb289dccfe838d4e364e1a5815447a6642b98
 -SRCREV_valleyisland-io_valleyisland-64 =
 8ea4fb625f2654bbdd5dfcb9db67328d21ebe504
 +LINUX_VERSION_valleyisland-64 = 3.10.65
 +SRCREV_machine_valleyisland-64 =
 ef1b96279e1a087a9d5b6a0601830d42ea47355c
 +SRCREV_meta_valleyisland-64 =
 d5456dd830cad14bd844753b751b83744ced3793
 +SRCREV_valleyisland-io_valleyisland-64 =
 0992d01f5f382f6da60004ef87f67ebd3ca13732
 
 -SRC_URI_valleyisland-64 = git://git.yoctoproject.org/linux-yocto-
 3.10.git;protocol=git;nocheckout=1;branch=${KBRANCH},${KMETA},valleyisland-
 io-1.0;name=machine,meta,valleyisland-io
 +SRC_URI_valleyisland-64 = git://git.yoctoproject.org/linux-yocto-
 3.10.git;protocol=git;nocheckout=1;branch=${KBRANCH},${KMETA},valleyisland-
 io-3.0;name=machine,meta,valleyisland-io
 
  module_autoload_i2c-dev = i2c-dev
 --
 1.7.9.5
 
 --
 ___
 meta-intel mailing list
 meta-intel@yoctoproject.org
 https://lists.yoctoproject.org/listinfo/meta-intel
-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

Re: [meta-intel] [PATCH 1/1] meta-valleyisland: Update the PREFERRED_VERSION of linux-yocto-3.10 to 3.14

[Chang, Rebecca Swee Fun]

Reviewed-by: Chang Rebecca Swee Fun rebecca.swee.fun.ch...@intel.com

 -Original Message-
 From: meta-intel-boun...@yoctoproject.org [mailto:meta-intel-
 boun...@yoctoproject.org] On Behalf Of wei.tee...@intel.com
 Sent: 26 February, 2015 5:55 PM
 To: meta-intel@yoctoproject.org
 Subject: [meta-intel] [PATCH 1/1] meta-valleyisland: Update the
 PREFERRED_VERSION of linux-yocto-3.10 to 3.14
 
 From: Ng Wei Tee wei.tee...@intel.com
 
 Update the PREFERRED_VERSION of linux-yocto-3.10 to 3.14 for
 valleyisland-32 and valleyisland-64.
 
 Signed-off-by: Ng Wei Tee wei.tee...@intel.com
 ---
  .../conf/machine/valleyisland-32.conf  |2 +-
  .../conf/machine/valleyisland-64.conf  |2 +-
  2 files changed, 2 insertions(+), 2 deletions(-)
 
 diff --git a/meta-isg/meta-valleyisland/conf/machine/valleyisland-32.conf
 b/meta-isg/meta-valleyisland/conf/machine/valleyisland-32.conf
 index 6bbae7a..385fb93 100644
 --- a/meta-isg/meta-valleyisland/conf/machine/valleyisland-32.conf
 +++ b/meta-isg/meta-valleyisland/conf/machine/valleyisland-32.conf
 @@ -6,7 +6,7 @@
  #@DESCRIPTION: Machine configuration for Valley Island 32-bit systems,
 without Intel-proprietary graphics bits
 
  PREFERRED_PROVIDER_virtual/kernel ?= linux-yocto
 -PREFERRED_VERSION_linux-yocto ?= 3.10%
 +PREFERRED_VERSION_linux-yocto ?= 3.14%
 
  require conf/machine/include/intel-core2-32-common.inc
  require conf/machine/include/intel-common-pkgarch.inc
 diff --git a/meta-isg/meta-valleyisland/conf/machine/valleyisland-64.conf
 b/meta-isg/meta-valleyisland/conf/machine/valleyisland-64.conf
 index a13cc17..7b5fe2d 100644
 --- a/meta-isg/meta-valleyisland/conf/machine/valleyisland-64.conf
 +++ b/meta-isg/meta-valleyisland/conf/machine/valleyisland-64.conf
 @@ -7,7 +7,7 @@
 
 
  PREFERRED_PROVIDER_virtual/kernel ?= linux-yocto
 -PREFERRED_VERSION_linux-yocto ?= 3.10%
 +PREFERRED_VERSION_linux-yocto ?= 3.14%
 
  require conf/machine/include/intel-corei7-64-common.inc
  require conf/machine/include/intel-common-pkgarch.inc
 --
 1.7.9.5
 
 --
 ___
 meta-intel mailing list
 meta-intel@yoctoproject.org
 https://lists.yoctoproject.org/listinfo/meta-intel
-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

Re: [meta-intel] Valleyisland boot gets stuck

[Chang, Rebecca Swee Fun]

Hi,

Thanks for your email. We have tested on the supported platforms that we 
declared in our BSP download page and there is no such issue seen on our side. 
You can also choose to log a bugzilla ticket if you think you need this issue 
to be fix. However, since the board you used is not in our supported platform 
list, we will evaluate first and try our best to help you.

Thanks.

Rebecca

 -Original Message-
 From: meta-intel-boun...@yoctoproject.org [mailto:meta-intel-
 boun...@yoctoproject.org] On Behalf Of Chris Tapp
 Sent: 28 November, 2014 4:58 PM
 To: meta-intel@yoctoproject.org
 Subject: [meta-intel] Valleyisland boot gets stuck
 
 I'm using the valleyisland BSP to create an image for an ASRock IBI-151 board
 and this is basically working, but there is an issue when it boots - the boot 
 stalls
 when the Yocto psplash gets progress bar gets to about 66%.
 
 The console doesn't appear to have any messages that give a clue to what's
 going on.
 
 I can get the boot to continue by inserting or removing a USB device 
 (including
 inserting a 'random' USB security device). Once booted the system runs
 normally.
 
 Any ideas what's going on here?
 
 --
 
 Chris Tapp
 opensou...@keylevel.com
 www.keylevel.com
 
 
 You can tell you're getting older when your car insurance gets real cheap!
 
 --
 ___
 meta-intel mailing list
 meta-intel@yoctoproject.org
 https://lists.yoctoproject.org/listinfo/meta-intel
-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

Re: [meta-intel] [PATCH 0/1] Update kernel SRCREV for meta-valleyisland

[Chang, Rebecca Swee Fun]

Alright, I will check again on Daisy and submit again for Daisy.
Thanks.

Rebecca

 -Original Message-
 From: Zanussi, Tom
 Sent: 09 September, 2014 10:43 PM
 To: Chang, Rebecca Swee Fun
 Cc: meta-intel@yoctoproject.org
 Subject: Re: [meta-intel] [PATCH 0/1] Update kernel SRCREV for meta-
 valleyisland
 
 On Mon, 2014-09-08 at 19:16 +0800, rebecca.swee.fun.ch...@intel.com
 wrote:
  From: Chang Rebecca Swee Fun rebecca.swee.fun.ch...@intel.com
 
  Hi,
 
  This patch is to update SRCREV of kernel recipe to v3.10.43 by taking
  the latest HEADs of the branches in linux-yocto-3.10.
 
  Please review the changes and provide feedback if there is any.
  This patch is target for meta-intel master branch and Daisy branch.
 
 
 Pulled into master, but not daisy.  With daisy, I get:
 
 
 uild Configuration:
 BB_VERSION= 1.22.0
 BUILD_SYS = x86_64-linux
 NATIVELSBSTRING   = Ubuntu-12.04
 TARGET_SYS= x86_64-poky-linux
 MACHINE   = valleyisland-64
 DISTRO= poky
 DISTRO_VERSION= 1.6.1
 TUNE_FEATURES = m64 corei7
 TARGET_FPU= 
 meta
 meta-yocto
 meta-yocto-bsp= daisy0:b2f045c400fa8bd20b319c60137b1575f967cef1
 meta-intel
 meta-valleyisland = daisy5:bb0a6b3e5142c60bb79b172ce98d3e6b9bb2fae7
 
 NOTE: Preparing runqueue
 NOTE: Executing SetScene Tasks
 NOTE: Executing RunQueue Tasks
 NOTE: validating kernel config, see log.do_kernel_configcheck for details
 ERROR: Function failed: do_compile (log file is located at
 /usr/local/src/yocto/daisy-test/build/tmp/work/valleyisland_64-poky-
 linux/lttng-modules/2.4.0-r0/temp/log.do_compile.29842)
 ERROR: Logfile of failure stored
 in: /usr/local/src/yocto/daisy-test/build/tmp/work/valleyisland_64-poky-
 linux/lttng-modules/2.4.0-r0/temp/log.do_compile.29842
 Log data follows:
 | DEBUG: Executing shell function do_compile
 | NOTE: make -j 8 -e MAKEFLAGS=
 KERNEL_PATH=/usr/local/src/yocto/daisy-test/build/tmp/sysroots/valleyisland-
 64/usr/src/kernel KERNEL_SRC=/usr/local/src/yocto/daisy-
 test/build/tmp/sysroots/valleyisland-64/usr/src/kernel
 KERNEL_VERSION=3.10.43-ltsi-yocto-standard CC=x86_64-poky-linux-gcc
 LD=x86_64-poky-linux-ld.bfd  AR=x86_64-poky-linux-ar
 | make
 -C /usr/local/src/yocto/daisy-test/build/tmp/sysroots/valleyisland-
 64/usr/src/kernel M=/usr/local/src/yocto/daisy-
 test/build/tmp/work/valleyisland_64-poky-linux/lttng-modules/2.4.0-r0/git
 modules
 | make[1]: Entering directory
 `/usr/local/src/yocto/daisy-test/build/tmp/sysroots/valleyisland-
 64/usr/src/kernel'
 |   CC
 [M]  /usr/local/src/yocto/daisy-test/build/tmp/work/valleyisland_64-poky-
 linux/lttng-modules/2.4.0-r0/git/lttng-ring-buffer-client-discard.o
 |   CC
 [M]  /usr/local/src/yocto/daisy-test/build/tmp/work/valleyisland_64-poky-
 linux/lttng-modules/2.4.0-r0/git/lttng-ring-buffer-client-overwrite.o
 |   CC
 [M]  /usr/local/src/yocto/daisy-test/build/tmp/work/valleyisland_64-poky-
 linux/lttng-modules/2.4.0-r0/git/lttng-ring-buffer-metadata-client.o
 |   CC
 [M]  /usr/local/src/yocto/daisy-test/build/tmp/work/valleyisland_64-poky-
 linux/lttng-modules/2.4.0-r0/git/lttng-ring-buffer-client-mmap-discard.o
 |   CC
 [M]  /usr/local/src/yocto/daisy-test/build/tmp/work/valleyisland_64-poky-
 linux/lttng-modules/2.4.0-r0/git/lttng-ring-buffer-client-mmap-overwrite.o
 |   CC
 [M]  /usr/local/src/yocto/daisy-test/build/tmp/work/valleyisland_64-poky-
 linux/lttng-modules/2.4.0-r0/git/lttng-ring-buffer-metadata-mmap-client.o
 |   CC
 [M]  /usr/local/src/yocto/daisy-test/build/tmp/work/valleyisland_64-poky-
 linux/lttng-modules/2.4.0-r0/git/lttng-statedump-impl.o
 |   CC
 [M]  /usr/local/src/yocto/daisy-test/build/tmp/work/valleyisland_64-poky-
 linux/lttng-modules/2.4.0-r0/git/wrapper/irqdesc.o
 |   CC
 [M]  /usr/local/src/yocto/daisy-test/build/tmp/work/valleyisland_64-poky-
 linux/lttng-modules/2.4.0-r0/git/wrapper/fdtable.o
 |   CC
 [M]  /usr/local/src/yocto/daisy-test/build/tmp/work/valleyisland_64-poky-
 linux/lttng-modules/2.4.0-r0/git/lttng-events.o
 |   CC
 [M]  /usr/local/src/yocto/daisy-test/build/tmp/work/valleyisland_64-poky-
 linux/lttng-modules/2.4.0-r0/git/lttng-abi.o
 |   CC
 [M]  /usr/local/src/yocto/daisy-test/build/tmp/work/valleyisland_64-poky-
 linux/lttng-modules/2.4.0-r0/git/lttng-probes.o
 |   CC
 [M]  /usr/local/src/yocto/daisy-test/build/tmp/work/valleyisland_64-poky-
 linux/lttng-modules/2.4.0-r0/git/lttng-context.o
 |   CC
 [M]  /usr/local/src/yocto/daisy-test/build/tmp/work/valleyisland_64-poky-
 linux/lttng-modules/2.4.0-r0/git/lttng-context-pid.o
 |   CC
 [M]  /usr/local/src/yocto/daisy-test/build/tmp/work/valleyisland_64-poky-
 linux/lttng-modules/2.4.0-r0/git/lttng-context-procname.o
 |   CC
 [M]  /usr/local/src/yocto/daisy-test/build/tmp/work/valleyisland_64-poky-
 linux/lttng-modules/2.4.0-r0/git/lttng-context-prio.o
 |   CC
 [M]  /usr/local/src/yocto/daisy-test/build/tmp/work/valleyisland_64-poky-
 linux/lttng-modules/2.4.0-r0/git/lttng-context-nice.o
 |   CC
 [M]  /usr/local/src/yocto/daisy-test/build

Re: [meta-intel] Yocto + mohonpeak BSP build probelm

[Chang, Rebecca Swee Fun]

Thanks for pointing that out. We will update it soon.

-Rebecca

From: Lai Eddy [mailto:eddy.lai...@gmail.com]
Sent: 16 July, 2014 5:39 PM
To: Chang, Rebecca Swee Fun
Cc: meta-intel@yoctoproject.org
Subject: Re: [meta-intel] Yocto + mohonpeak BSP build probelm

Thanks Rebecca,

Bblayers.conf:
- Remove line : /media/eddylai/datahd/poky/meta-intel/meta-isg \
fixed the problem, and I just add the 3 layer path according to Mohonpeak BSP's 
README file ( 
http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/tree/meta-isg/meta-mohonpeak/README?h=daisy
 ), maybe this file need to be updated.

BRGDS
Eddy Lai

2014-07-16 16:51 GMT+08:00 Chang, Rebecca Swee Fun 
rebecca.swee.fun.ch...@intel.commailto:rebecca.swee.fun.ch...@intel.com:
Hi Eddy,

Thanks for using Mohonpeak Yocto Project BSP. I’ve checked your attachments. 
Here are my comments:

Bblayers.conf:
- Remove line : /media/eddylai/datahd/poky/meta-intel/meta-isg \
- You only add layers that contains conf/ directory. In this case, meta-isg 
layer does not contain any layer configurations, so you don’t need to add that.

Layer.conf:
- You have duplicated parallelism options
Note that you have:
BB_NUMBER_THREADS ?= 8
BB_NUMBER_THREADS ?= 
${@oe.utils.cpu_count()}mailto:$%7b@oe.utils.cpu_count()%7d

Choose 1 option and comment out the other option.
BB_NUMBER_THREADS ?= 
${@oe.utils.cpu_count()}mailto:$%7b@oe.utils.cpu_count()%7d will allocate max 
number of threads based on your machine capability.
If you would like to specify your own, comment this line.

Same for this:
PARALLEL_MAKE ?= -j 8
PARALLEL_MAKE ?= -j 
${@oe.utils.cpu_count()}mailto:$%7b@oe.utils.cpu_count()%7d

- You are building two MACHINE type
MACHINE ?= mohonpeak-32
MACHINE ??= qemux86

Choose one and comment out the other option.

Regards
Rebecca



From: 
meta-intel-boun...@yoctoproject.orgmailto:meta-intel-boun...@yoctoproject.org 
[mailto:meta-intel-boun...@yoctoproject.orgmailto:meta-intel-boun...@yoctoproject.org]
 On Behalf Of Lai Eddy
Sent: 16 July, 2014 4:39 PM
To: meta-intel@yoctoproject.orgmailto:meta-intel@yoctoproject.org
Subject: [meta-intel] Yocto + mohonpeak BSP build probelm


I have just download Yocto YP Core - Daisy 1.6.1 and  Intel® Atom® Processor 
C2000 (Mohon Peak) BSP , modified .conf files (as attached) then try the first 
time build, got errors as below, anything else I did wrong? (have tried both 
32/64 arch )
checked there's no conf/layer.conf under meta-isg folder included in the 
original downloaded BSP( tryied both git and download the .bz2 file from YP 
site)
Eddy Lai

$ bitbake core-image-sato
ERROR: Traceback (most recent call last):
  File /media/eddylai/datahd/poky/bitbake/lib/bb/cookerdata.py, line 163, in 
wrapped
return func(fn, *args)
  File /media/eddylai/datahd/poky/bitbake/lib/bb/cookerdata.py, line 173, in 
parse_config_file
return bb.parse.handle(fn, data, include)
  File /media/eddylai/datahd/poky/bitbake/lib/bb/parse/__init__.py, line 99, 
in handle
return h['handle'](fn, data, include)
  File 
/media/eddylai/datahd/poky/bitbake/lib/bb/parse/parse_py/ConfHandler.py, line 
120, in handle
abs_fn = resolve_file(fn, data)
  File /media/eddylai/datahd/poky/bitbake/lib/bb/parse/__init__.py, line 122, 
in resolve_file
raise IOError(file %s not found % fn)
IOError: file /media/eddylai/datahd/poky/meta-intel/meta-isg/conf/layer.conf 
not found

ERROR: Unable to parse 
/media/eddylai/datahd/poky/meta-intel/meta-isg/conf/layer.conf: file 
/media/eddylai/datahd/poky/meta-intel/meta-isg/conf/layer.conf not found


-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

Re: [meta-intel] Valleyisland SDIO support

[Chang, Rebecca Swee Fun]

Hi,

I'm aware that the DDR50 mode is not fully supported. The clock appears to be 
unstable when SDCARD host running with DDR50 mode. We have a workaround that 
introduce a new quirk to force host with broken DDR50 mode to run with SDR25 
mode. As we think that this workaround might not be suitable to be upstream to 
mainline kernel, this workaround will be implemented in our valleyisland-io 
feature branch in future. We are now working on backporting our features from 
mainline kernel to LTSI/LTS kernel. And eventually all those workaround that do 
not fit upstream criteria will be implemented temporary in feature branch.

I'm not sure whether I can provide you the workaround patch here. I will work 
with our driver developers in order to help you in this. You may file a bug in 
bugzilla so that we got track on your enquiry. Thanks a lot.

Rebecca


From: IGI/Falk Bauer [mailto:f.ba...@igi-systems.com]
Sent: 12 May, 2014 5:37 PM
To: Chang, Rebecca Swee Fun
Cc: meta-intel@yoctoproject.org
Subject: Valleyisland SDIO support

Hello Rebecca,
thanks for your recently work with the Baytrail board. I can confirm that the 
image in dora branch is working with full OpenGL support.
Here is another question relating to the SDIO controller embedded into the atom 
processor.
In the intel specifiction update from january 2014 
(http://www.intel.com/content/dam/www/public/us/en/documents/specification-updates/atom-Z36xxx-Z37xxx-spec-update.pdf)
 there is an entry named VLT55 SD Card UHS - I Mode is Not Fully Supported.
We have issues here with sd cards from sandisk which are running into error 
messages like
**
May 7 16:27:53 valleyisland-32 user.debug kernel: [ 125.254962] sdhci-pci 
:00:12.0: setting latency timer to 64
May 7 16:27:55 valleyisland-32 user.info kernel: [ 127.510449] mmc1: new ultra 
high speed DDR50 SDHC card at address e624
May 7 16:27:55 valleyisland-32 user.info kernel: [ 127.511010] mmcblk0: 
mmc1:e624 SD08G 7.40 GiB
May 7 16:27:55 valleyisland-32 user.info kernel: [ 127.520193] mmcblk0: p1
May 7 16:27:55 valleyisland-32 user.err kernel: [ 127.526524] mmcblk0: error 
-84 transferring data, sector 15523712, nr 8, cmd response 0x900, card status 
0xb00
May 7 16:27:55 valleyisland-32 user.warn kernel: [ 127.526534] mmcblk0: 
retrying using single block read
May 7 16:27:55 valleyisland-32 user.err kernel: [ 127.529319] mmcblk0: error 
-84 transferring data, sector 15523712, nr 8, cmd response 0x900, card status 
0x0
May 7 16:27:55 valleyisland-32 user.warn kernel: [ 127.529329] 
blk_update_request: 773 callbacks suppressed
May 7 16:27:55 valleyisland-32 user.err kernel: [ 127.529335] end_request: I/O 
error, dev mmcblk0, sector 15523712
May 7 16:27:55 valleyisland-32 user.err kernel: [ 127.531980] mmcblk0: error 
-84 transferring data, sector 15523713, nr 7, cmd response 0x900, card status 
0x0
May 7 16:27:55 valleyisland-32 user.err kernel: [ 127.531990] end_request: I/O 
error, dev mmcblk0, sector 15523713
**

These messages appears in the kernel log buffer after inserting an sd card 
SanDisk Extreme 30 MB/s, class 10 UHS 1 8GB (vendor name in sysfs is SU08G).
Further investigations reveals that the error reproduce is related to the kind 
of sd card, filesystem on the partition aso.
I think that the errata vlt55 leads to the messages in the log. Have you 
experienced some similar issues with the Z3000 atom series? Or is there some 
plans or possibilities to disable the UHS feature for the SDIO device embedded 
in the atom cpu? I know that in the specification update there is currently the 
no fix entry. But maybe there is some quick-and-dirty fix like a 
SDHCI_QUIRK2_BROKEN_UHS define or so in the sdhci module in the kernel.
If you wish i can also fill a bug in bugzilla.

Falk


IGI - Ingenieur-Gesellschaft fuer Interfaces mbH
Dipl.-Ing. Falk Bauer
Applications Engineer
Langenauer Str. 46
57223 Kreuztal, Germany
Tel.:

+49 2732 5525 0

Fax:

+49 2732 5525 25

E-mail:

f.ba...@igi-systems.commailto:f.ba...@igi-systems.com

Internet:

www.igi-systems.comhttp://www.igi.eu/news.html

Follow us:

[IGI News Feed]http://www.igi.eu/IGI_News.xml [IGI at YouTube] 
http://www.youtube.com/IGISystems   [LinkedIn] 
http://www.linkedin.com/company/follow/submit?id=2662318fl=startft=pageKey%3Dbiz-overview-internal%3Bmodule%3DbuttoncsrfToken=ajax%3A8766554907507224198goback=%2Enmp_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1_*1%2Ebzo_*1_*1_*1_*1_*1_*1_*1_igi*5systemstrk=co_fol-start-3


[IGI Logo]http://www.igi.eu/news.html



Meet us:
Geospatial World Forum in Geneve (5-9 
May)http://www.igi.eu/event-reader/events/geospatial-world-forum-in-geneve-switzerland.html
 * Geo Business in London (28+29 
May)http://www.igi.eu/event-reader/events/geo-business-2014-in-london-uk.html



-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org

Re: [meta-intel] Valleyisland graphics in Dora

[Chang, Rebecca Swee Fun]

Hi,

Valleyisland-io includes Baytrail supported Low Power Subsystem (LPSS) I/O 
devices.
For example, I2C, SPI, GPIO etc. The current enumeration mode supported in Dora 
is ACPI mode only.

For rt-kernel support in Dora, we have implemented and tested on Bayley Bay CRB 
and Valley Island Dev Kit.
We are now in the progress of making the rt-kernel recipes available in Yocto 
git repository. Stay tuned.

Rebecca

 -Original Message-
 From: Keskinarkaus, Teemu [mailto:teemu.keskinark...@maximatecc.com]
 Sent: 14 April, 2014 12:13 PM
 To: Darren Hart; Chang, Rebecca Swee Fun; 'IGI/Falk Bauer'
 Cc: meta-intel@yoctoproject.org
 Subject: RE: [meta-intel] Valleyisland graphics in Dora
 
 Hi,
 
 What does the valley-island-io - feature include?
 
 To make things not so easy and simple, we need to run our system 32-bit and
 not 64-bit. Valleyisland - support has both, but corei7 has only 64-bit.  We 
 are
 also using Dora-branch and corei7 support is only for master-branch.
 
 Any estimation for the rt-kernel support for Dora/Valleyisland?
 
 Teemu Keskinarkaus
 Software system engineer
 
 maximatecc - Humans in control
 
  -Original Message-
  From: Darren Hart [mailto:dvh...@linux.intel.com]
  Sent: 9. huhtikuuta 2014 19:42
  To: Chang, Rebecca Swee Fun; Keskinarkaus, Teemu; 'IGI/Falk Bauer'
  Cc: meta-intel@yoctoproject.org
  Subject: Re: [meta-intel] Valleyisland graphics in Dora
 
  On 4/4/14, 2:58, Chang, Rebecca Swee Fun
  rebecca.swee.fun.ch...@intel.com wrote:
 
  Hi,
  
  For rt-kernel support, we will seriously consider about enabling the
  feature, please stay tuned for more features in the coming releases.
 
  This is being supported currently on the intel-corei7-64 BSP which has
  Bay Trail support and includes 3.10-LTSI, 3.10-LTSI-RT, and 3.14 kernel
 support.
 
  It is lacking the valley-island-io feature branch. If you are looking
  for that, the valley-island BSP is still your best bet, and working
  with Rebecca to get RT support added.
 
  --
  Darren Hart   Open Source Technology
  Center
  darren.h...@intel.com Intel Corporation
 
 
 
 
 
 
 Actuant Corporation Email Notice
 
 This message is intended only for the use of the Addressee and may contain
 information that is PRIVILEGED and/or CONFIDENTIAL.
 This email is intended only for the personal and confidential use of the
 recipient(s) named above. If the reader of this email is not an intended
 recipient, you have received this email in error and any review, 
 dissemination,
 distribution or copying is strictly prohibited.
 If you have received this email in error, please notify the sender immediately
 by return mail and permanently delete the copy you received.
 
 Thank you.
-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

Re: [meta-intel] Valleyisland graphics in Dora

[Chang, Rebecca Swee Fun]

Hi,

For rt-kernel support, we will seriously consider about enabling the feature, 
please stay tuned for more features in the coming releases.

About removing unwanted kernel configs, you can do the same as what you did to 
add configs. In your config files, use # CONFIG_IGB is not set and this can 
help you to turn off the configs.
FYI, this is not a proper way. This is meant for your own development. 
The kernel configs are set in linux-yocto-3.X meta branch. The configurations 
that we set are boot tested and undergone sanity tests in order to ensure our 
device drivers work for all. 
Since this removal of configs is specified to your case, you own the 
responsibility to maintain such customization locally.

Thank you.

 -Original Message-
 From: Keskinarkaus, Teemu [mailto:teemu.keskinark...@maximatecc.com]
 Sent: 04 April, 2014 5:22 PM
 To: Chang, Rebecca Swee Fun; 'IGI/Falk Bauer'
 Cc: meta-intel@yoctoproject.org
 Subject: RE: Valleyisland graphics in Dora
 
 Hi,
 
 I can confirm this that it works. I had too old kernel version in my system. I
 updated it to 3.10.35(including the git hashes) and now the accelerated
 graphics works and I don't have that error anymore that I had before and also
 Intel-driver works on Xorg.
 
 This brings me to another problem I encountered while updating the meta-
 intel.
 
 We are using rt-kernel in our product and it seems that valleyisland - layer
 has only support for normal kernel. Is the rt-kernel support coming or should
 I switch to master-version to get that?
 
 I tried updating my rt-kernel recipes to be used with new kernel version and
 valleyisland, but even though I changed the KBRANCH to
 standard/preempt-rt/base and updated the git hashes the compilation fails.
 It seems that the configuration of the kernel doesn't go properly and
 valleyisland-32 - kernel is configured for 64-bit etc.  I'm guessing that the
 kernel is missing the support for valleyisland-32?
 
 One other thing regarding the configurations too. I'm not sure  if this is 
 more
 of generic poky stuff or meta-intel, but feel free to answer if you wish. How
 is the kernel configuration going now? I mean I have those pieces of
 configuration files that has one or more config-options (Like CONFIG_IGB=y)
 and then I define them in recipe as SRC_URI and they 'just work'. That works
 when needing to add something, but how do I remove some configurations
 that I don't need/want? Ie. which is the proper way to do this? I couldn't 
 find
 any proper documentation of this or I've missed something.
 
 Teemu Keskinarkaus
 Software system engineer
 
 maximatecc - Humans in control
 
 
  -Original Message-
  From: Chang, Rebecca Swee Fun
  [mailto:rebecca.swee.fun.ch...@intel.com]
  Sent: 4. huhtikuuta 2014 4:03
  To: 'IGI/Falk Bauer'; Keskinarkaus, Teemu
  Cc: meta-intel@yoctoproject.org
  Subject: RE: Valleyisland graphics in Dora
 
  Hi both,
 
  Based on your descriptions about the problem, I can confirm that I do
  not see the issue on my side with the latest Dora branch meta-valleyisland
 recipes.
  I've tested glxgears and got the glxinfo from Bayley Bay CRB and also
  Valley Island Dev Kit. I'm building my image with
  LICENSE_FLAGS_WHITELIST = commercial and also the
  EXTRA_MACHINE_FEATURES = tools-testapps for testing purposes. I do
 not recommend to change the branch to standard/ltsi.
  Standard/base has sufficient backport support for Baytrail for the
  time being and we are working on to add more. You may go to bugzilla
  to log down the problem you've seen and provide more information for us
 to look into it. Thanks.
 
  Rebecca
 
 
   -Original Message-
   From: meta-intel-boun...@yoctoproject.org [mailto:meta-intel-
   boun...@yoctoproject.org] On Behalf Of IGI/Falk Bauer
   Sent: 03 April, 2014 9:30 PM
   To: Keskinarkaus, Teemu
   Cc: meta-intel@yoctoproject.org
   Subject: Re: [meta-intel] Valleyisland graphics in Dora
  
   Teemu,
   i had similar problems a few days ago with our E3825 based hardware.
   The most important thing is that you switched to the ltsi kernel
   where the Bay Trail support is backported from newer kernel
   versions. Bay Trail support was introduced from version 3.11 i think.
   You have to look for the following message in the kernel message buffer:
   [drm:i915_pci_probe] *ERROR* Preliminary hardware support disabled
   This means that the device file /dev/dri/card0 is not created and so
   the intel driver says that the device is not found. This message
   appears if you use the standard/base kernel version in yocto.
  
   To switch to the ltsi kernel you have to set the following statement
   in the
   meta-isg/meta-valleyisland/recipes-kernel/linux/linux-
 yocto_3.10.bbappend:
   KBRANCH_valleyisland-32 = standard/ltsi
   SRCREV is also changed to the commit id for the tagged version of ltsi
 3.10.32:
   SRCREV_machine_valleyisland-32 =
   78afd3095c9b37efbbfbfdc25eb3833ef3c6a718
  
   Yet I do not know how to manage

Re: [meta-intel] Valleyisland graphics in Dora

[Chang, Rebecca Swee Fun]

Hi both,

Based on your descriptions about the problem, I can confirm that I do not see 
the issue on my side with the latest Dora branch meta-valleyisland recipes.
I've tested glxgears and got the glxinfo from Bayley Bay CRB and also Valley 
Island Dev Kit. I'm building my image with LICENSE_FLAGS_WHITELIST = 
commercial and also the EXTRA_MACHINE_FEATURES = tools-testapps for testing 
purposes. I do not recommend to change the branch to standard/ltsi. 
Standard/base has sufficient backport support for Baytrail for the time being 
and we are working on to add more. You may go to bugzilla to log down the 
problem you've seen and provide more information for us to look into it. Thanks.

Rebecca


 -Original Message-
 From: meta-intel-boun...@yoctoproject.org [mailto:meta-intel-
 boun...@yoctoproject.org] On Behalf Of IGI/Falk Bauer
 Sent: 03 April, 2014 9:30 PM
 To: Keskinarkaus, Teemu
 Cc: meta-intel@yoctoproject.org
 Subject: Re: [meta-intel] Valleyisland graphics in Dora
 
 Teemu,
 i had similar problems a few days ago with our E3825 based hardware. The
 most important thing is that you switched to the ltsi kernel where the Bay
 Trail support is backported from newer kernel versions. Bay Trail support was
 introduced from version 3.11 i think.
 You have to look for the following message in the kernel message buffer:
 [drm:i915_pci_probe] *ERROR* Preliminary hardware support disabled This
 means that the device file /dev/dri/card0 is not created and so the intel
 driver says that the device is not found. This message appears if you use the
 standard/base kernel version in yocto.
 
 To switch to the ltsi kernel you have to set the following statement in the
 meta-isg/meta-valleyisland/recipes-kernel/linux/linux-yocto_3.10.bbappend:
 KBRANCH_valleyisland-32 = standard/ltsi
 SRCREV is also changed to the commit id for the tagged version of ltsi 
 3.10.32:
 SRCREV_machine_valleyisland-32 =
 78afd3095c9b37efbbfbfdc25eb3833ef3c6a718
 
 Yet I do not know how to manage such changes in a layer overlay. I have
 directly hacked the bbappend file currently.
 
 Hope this is of help for you.
 
 Falk
 
 
 --
 IGI - Ingenieur-Gesellschaft fuer Interfaces mbH Dipl.-Ing. Falk Bauer
 Applications Engineer Langenauer Str. 46
 57223 Kreuztal, Germany
 Tel.: +49 2732 5525 0
 Fax: +49 2732 5525 25
 E-mail: f.ba...@igi-systems.com
 Internet: www.igi-systems.com
 ---Ursprüngliche 
 Nachricht-
 Von: meta-intel-boun...@yoctoproject.org [mailto:meta-intel-
 boun...@yoctoproject.org] Im Auftrag von Keskinarkaus, Teemu
 Gesendet: Donnerstag, 3. April 2014 13:04
 An: meta-intel@yoctoproject.org
 Betreff: [meta-intel] Valleyisland graphics in Dora
 
 Hi,
 
 I noticed that Dora branch has also finally got its Valleyisland support so I
 downloaded latest Dora-branch of meta-intel and also updated Dora-branch
 of Poky.
 
 I then rebuild my own image of it and it booted ok. The thing is that when I
 try to use any gl applications (for example glxinfo or glxgears) I get the
 following error:
 
 sh-4.2# glxinfo
 name of display: :0.0
 Error: couldn't find RGB GLX visual or fbconfig
 Error: couldn't find RGB GLX visual or fbconfig
 
 What am I missing or is there a bug somewhere?
 
 I also have to use Vesa-driver for Xorg and not Intel driver. If I try to use 
 Intel
 driver it says device not found. Any idea what might cause that? I thought
 that the Intel driver should support that HW with acceleration? I think Vesa-
 driver doesn't support acceleration or doe it? The HW I use have beta version
 of BIOS so could that be the display part of the BIOS is missing some display
 things or is that bug/configuration issue in software?
 
 I'm running Yocto on E3826 HW.
 
 Teemu Keskinarkaus
 Software system engineer
 
 maximatecc - Humans in control
 
 
 
 
 Actuant Corporation Email Notice
 
 This message is intended only for the use of the Addressee and may contain
 information that is PRIVILEGED and/or CONFIDENTIAL.
 This email is intended only for the personal and confidential use of the
 recipient(s) named above. If the reader of this email is not an intended
 recipient, you have received this email in error and any review, 
 dissemination,
 distribution or copying is strictly prohibited.
 If you have received this email in error, please notify the sender immediately
 by return mail and permanently delete the copy you received.
 
 Thank you.
 --
 ___
 meta-intel mailing list
 meta-intel@yoctoproject.org
 https://lists.yoctoproject.org/listinfo/meta-intel
 
 
 
 --
 ___
 meta-intel mailing list
 meta-intel@yoctoproject.org
 https://lists.yoctoproject.org/listinfo/meta-intel
-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org

Re: [meta-intel] [PATCHv2 4/5] meta-valleyisland: add kernel recipe for valleyisland

[Chang, Rebecca Swee Fun]

Hi all,

Thanks for all the input. I will remove _pn and use = and test build. After 
I'm done with verification, I will respin the pull request.

Thanks everyone.

Rebecca

 -Original Message-
 From: Darren Hart [mailto:dvh...@linux.intel.com]
 Sent: 25 March, 2014 6:39 AM
 To: Paul Eggleton
 Cc: Chang, Rebecca Swee Fun; meta-intel@yoctoproject.org
 Subject: Re: [meta-intel] [PATCHv2 4/5] meta-valleyisland: add kernel recipe
 for valleyisland
 
 On 3/24/14, 15:24, Paul Eggleton paul.eggle...@linux.intel.com wrote:
 
 On Monday 24 March 2014 15:16:56 Darren Hart wrote:
  On 3/24/14, 15:11, Paul Eggleton paul.eggle...@linux.intel.com
 wrote:
  On Monday 24 March 2014 15:07:10 Darren Hart wrote:
   On 3/24/14, 10:57, rebecca.swee.fun.ch...@intel.com
  
   rebecca.swee.fun.ch...@intel.com wrote:
   +#
   +# MACHINE = valleyisland-32 #
   +#
   +COMPATIBLE_MACHINE_valleyisland-32 = valleyisland-32
   +KMACHINE_valleyisland-32 = valleyisland-32
   +KBRANCH_valleyisland-32 = standard/base
   +KERNEL_FEATURES_valleyisland-32 =
   features/valleyisland-io/valleyisland-io
   +
   +LINUX_VERSION_valleyisland-32 = 3.10.32
   +SRCREV_machine_pn-linux-yocto_valleyisland-32 ?=
   61dde96f97bb5b1ed4c11caf9a857d55ad8f6e17
   +SRCREV_meta_pn-linux-yocto_valleyisland-32 ?=
   99c503a92885060bebf2bba6747735e8e9346a40
  
   With respect the need for pn-linux-yocto here, this is because all
 the
   other SRCREV_machine* in meta-intel are using = instead of ?=.
   This
  
  won't
  
   get set because the base linux-yocto recipe specifies a SRCREV, so
 the
  
  ?=
  
   will no override it. The pn-linux-yocto provides a more specific
 value
   which has not yet been set, so it sticks and gets applied.
  
   Just for consistency, the right answer is probably to use =
   instead
 of
  
  ?=
  
   and drop the pn-linux-yocto.
  
   I do not really care for have = in the bbappend honestly. I
   wonder
 if
   Paul would have another recommendation here...
  
  What concerns you about using = here? I would have thought it was OK
  in this situation; ?= is only really helpful where you want to apply
  a default where a value that should override the default may already
  have been set (e.g.
 in
  local.conf where a desired value might have been set from the
  command line).
 
  That is basically the concern, do we want people to be able to
 override it  easily? Perhaps the answer is no. I suspect SRCREV's are
 really not  something we want people messing with. We can still
 override in local.conf  using = right?
 
 We can if an additional override that is not present in the
 recipe/append is used (e.g. pn-linux-yocto, assuming that is removed
 from the append as you suggest).
 
 If the recipe is setting it with = then that does make it a little
 harder to override, but I think with something like SRCREV that is a
 good thing as you say.
 
 Cheers,
 Paul
 
 Thank you Paul,
 
 Rebecca, can you verify that this can work without the pn-linux-yocto by
 using = instead of ?= ? We would prefer to remain consistent with BSPs in
 meta-intel so the same override rules and procedures can be applied to all
 the BSPs.
 
 --
 Darren Hart
 Yocto Project - Linux Kernel
 Intel Open Source Technology Center
 
 
 

-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

Re: [meta-intel] [PATCH 0/5] [DORA] meta-isg: add new BSP layer for Valley Island

[Chang, Rebecca Swee Fun]

Hi Tom,

Here is my build configuration:

Build Configuration:
BB_VERSION= 1.20.0
BUILD_SYS = x86_64-linux
NATIVELSBSTRING   = Ubuntu-12.10
TARGET_SYS= x86_64-poky-linux
MACHINE   = valleyisland-64
DISTRO= poky
DISTRO_VERSION= 1.5.1
TUNE_FEATURES = m64 core2
TARGET_FPU= 
meta  
meta-yocto
meta-yocto-bsp= dora:023c35795ff8edd79bb27848a01dd49239f052d4
meta-intel
meta-tlk  
meta-valleyisland = dora:99d1f2f61feb5b338d659babe32ad4ae89e9bf3b

Rebecca

 -Original Message-
 From: Zanussi, Tom
 Sent: 21 March, 2014 8:54 PM
 To: Chang, Rebecca Swee Fun
 Cc: 'Darren Hart'; meta-intel@yoctoproject.org
 Subject: Re: [meta-intel] [PATCH 0/5] [DORA] meta-isg: add new BSP layer
 for Valley Island
 
 On Fri, 2014-03-21 at 05:41 -0500, Chang, Rebecca Swee Fun wrote:
   -Original Message-
   From: Darren Hart [mailto:dvh...@linux.intel.com]
   Sent: 21 March, 2014 12:29 PM
   To: Chang, Rebecca Swee Fun; Zanussi, Tom
   Cc: meta-intel@yoctoproject.org
   Subject: Re: [meta-intel] [PATCH 0/5] [DORA] meta-isg: add new BSP
   layer for Valley Island
  
   On 3/20/14, 20:52, Chang, Rebecca Swee Fun
   rebecca.swee.fun.ch...@intel.com wrote:
   
   The changes in linux-yocto-3.10 was merged. And I sent the pull
   request for meta-intel after linux-yocto-3.10 was updated. I
   noticed that the commit ids are not the one I'm using. Is the
   recipe goes wrong some where else?
   
   I've also checked my branch (rebeccas/meta-valleyisland-dora-dev)
   in meta-intel-contrib. They are same as what I am sending out. But
   your build error log showing the wrong commit id.
   
   I need to check again to confirm.
  
   Ah, the commit Ids will be different after Bruce adds his
   Signed-off-by and if he merged it with anything pending. Always
   check the linux-yocto tree for new commit Ids after your changes have
 been merged.
  
  No, I think my recipe is correct. I have send out a recipe with commit
  ids with Bruce's signed-off. However, Tom's build failure was building
  at different commit id.
 
  In my recipe, I am appending:
  SRCREV_machine-linux-yocto_valleyisland-32 ?=
 61dde96f97bb5b1ed4c11caf9a857d55ad8f6e17
  SRCREV_meta-linux-yocto_valleyisland-32 ?=
 99c503a92885060bebf2bba6747735e8e9346a40
 
  From Tom's build log:
  3.10.32+gitAUTOINC+6ad20f049a_c03195ed6e-r0
  Which does not match with my recipe.
 
  I don't have compiling issue here. Can Tom please help to check his build
 again?
  Thanks a lot.
 
 
 I'll check, but I don't expect any difference - this was from a clean build 
 after
 seeing it the first time.
 
 But just to make sure we're on the same page, can you verify that you're
 using the same poky and meta-intel SRCREVs as in my error message (or
 send me yours)?
 
 Thanks,
 
 Tom
 
  Rebecca
 

-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

Re: [meta-intel] [PATCH 0/5] [DORA] meta-isg: add new BSP layer for Valley Island

[Chang, Rebecca Swee Fun]

 -Original Message-
 From: Darren Hart [mailto:dvh...@linux.intel.com]
 Sent: 21 March, 2014 3:44 AM
 To: Zanussi, Tom; Chang, Rebecca Swee Fun
 Cc: meta-intel@yoctoproject.org
 Subject: Re: [meta-intel] [PATCH 0/5] [DORA] meta-isg: add new BSP layer
 for Valley Island
 
 On 3/20/14, 8:24, Tom Zanussi tom.zanu...@intel.com wrote:
 
 On Fri, 2014-03-21 at 01:55 +0800, rebecca.swee.fun.ch...@intel.com
 wrote:
  From: Chang Rebecca Swee Fun rebecca.swee.fun.ch...@intel.com
 
  Hi all,
 
  This is a pull request for meta-valleyisland supporting
  linux-yocto-3.10 on Dora branch.
 
  In this patch series, a meta-valleyisland layer will be added into
  meta-intel Dora branch.
 
  The kernel recipe is able to support basic drivers which essential to
  boot up sequence. For example, SATA, USB, GbE, and UART. The graphics
  driver support in this bsp is Intel i915 graphics driver.
 
  The LPSS I/O device drivers are available only in ACPI mode. This is
  due the PCI related code base are still under development. PCI mode
  LPSS I/O devices will be hosted in a feature branch in
  linux-yocto-3.10 in near future.
 
  Please pull this patch series into meta-intel Dora branch.
 
 
 Hi Rebecca,
 
 I'm seeing a build failure with this patchset:
 
 trz@elmorro:/usr/local/src/yocto/dora-test/build$ bitbake
 core-image-satoLoading cache: 100%
 |###| ETA:
 00:00:00
 Loaded 1208 entries from dependency cache.
 NOTE: Resolving any missing task queue dependencies
 
 Build Configuration:
 BB_VERSION= 1.20.0
 BUILD_SYS = x86_64-linux
 NATIVELSBSTRING   = Ubuntu-12.04
 TARGET_SYS= i586-poky-linux
 MACHINE   = valleyisland-32
 DISTRO= poky
 DISTRO_VERSION= 1.5.1
 TUNE_FEATURES = m32 core2
 TARGET_FPU= 
 meta
 meta-yocto
 meta-yocto-bsp= dora1:023c35795ff8edd79bb27848a01dd49239f052d4
 meta-intel
 meta-valleyisland = dora2:5e1b84083097e0a1e38ae70a53d48b87d9c099b4
 
 NOTE: Preparing runqueue
 NOTE: Executing SetScene Tasks
 NOTE: Executing RunQueue Tasks
 ERROR: Function failed: do_patch (log file is located at
 /usr/local/src/yocto/dora-test/build/tmp/work/valleyisland_32-poky-linu
 x/l
 inux-yocto/3.10.32+gitAUTOINC+6ad20f049a_c03195ed6e-
 r0/temp/log.do_patc
 h.5
 267)
 ERROR: Logfile of failure stored in:
 /usr/local/src/yocto/dora-test/build/tmp/work/valleyisland_32-poky-linu
 x/l
 inux-yocto/3.10.32+gitAUTOINC+6ad20f049a_c03195ed6e-
 r0/temp/log.do_patc
 h.5
 267
 Log data follows:
 | DEBUG: Executing shell function do_patch Branch meta-temp set up to
 | track remote branch meta from origin.
 | Deleted branch meta-temp (was f58e62b).
 | WARNING: addon feature features/valleyisland-io/valleyisland-io was
 not found
 | ERROR: required features were not found. aborting ERROR. Could not
 | update standard/base
 | WARNING:
 /usr/local/src/yocto/dora-test/build/tmp/work/valleyisland_32-poky-linu
 x/l
 inux-yocto/3.10.32+gitAUTOINC+6ad20f049a_c03195ed6e-
 r0/temp/run.do_patc
 h.5
 267:1 exit 1 from
 |   exit 1
 | ERROR: Function failed: do_patch (log file is located at
 /usr/local/src/yocto/dora-test/build/tmp/work/valleyisland_32-poky-linu
 x/l
 inux-yocto/3.10.32+gitAUTOINC+6ad20f049a_c03195ed6e-
 r0/temp/log.do_patc
 h.5
 267)
 ERROR: Task 85
 (/usr/local/src/yocto/dora-test/meta/recipes-kernel/linux/linux-yocto_3
 .10 .bb, do_patch) failed with exit code '1'
 NOTE: Tasks Summary: Attempted 1873 tasks of which 1105 didn't need to
 be rerun and 1 failed.
 Waiting for 0 running tasks to finish:
 
 Summary: 1 task failed:
 
 /usr/local/src/yocto/dora-test/meta/recipes-kernel/linux/linux-yocto_3.10.
 bb, do_patch
 Summary: There was 1 ERROR message shown, returning a non-zero exit
 code.
 
 
 
 Looks like we're pending the linux-yocto changes to go in. Rebecca those
 have been sent and Acked right? Just waiting on merge?

The changes in linux-yocto-3.10 was merged. And I sent the pull request for 
meta-intel after linux-yocto-3.10 was updated. I noticed that the commit ids 
are not the one I'm using. Is the recipe goes wrong some where else?

I've also checked my branch (rebeccas/meta-valleyisland-dora-dev) in 
meta-intel-contrib. They are same as what I am sending out. But your build 
error log showing the wrong commit id. 

I need to check again to confirm.

Thanks.

Rebecca

 
 
 --
 Darren Hart
 Yocto Project - Linux Kernel
 Intel Open Source Technology Center
 
 
 

-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

Re: [meta-intel] New valleyisland support

[Chang, Rebecca Swee Fun]

Hi all,

We are in progress of making Valley Island BSP available in Dora with kernel 
3.10.
Currently we are trying to root cause the i915 graphic driver issue and we will 
start pushing out for review once it is done.
As of linux-yocto-rt for Valley Island, it is not included in Dylan release. I 
will need to discuss with the team whether to include in our coming release.

Thanks.
Rebecca

 -Original Message-
 From: Darren Hart [mailto:dvh...@linux.intel.com]
 Sent: 12 March, 2014 11:01 PM
 To: Keskinarkaus, Teemu; Meta Intel
 Cc: Chang, Rebecca Swee Fun; Ong, Boon Leong
 Subject: Re: [meta-intel] New valleyisland support
 
 Hi Teemu,
 
 Can you explain how you arrived at using the dvhart/bsp-ng branch? This is a
 development/testing branch, certainly not something meant for
 productization use. We're merging bits of bsp-ng into master as it's tested,
 verified, and fixed up.
 
 Valleyisland support specifically is available in Dylan under meta-isg/meta-
 valleyisland. Rebecca and her team are working on adding it to Dora with a
 3.10 kernel I believe, but I'll leave it to her to comment on that.
 
 If you are just looking for Baytrail SoC support (not specifically
 valleyisland) then that is now available in meta-intel/master using the
 intel-corei7-64 BSP. This is a new approach to Intel BSPs which supports
 multiple boards/CPUs with a single BSP.
 
 As to linux-yocto-rt, we have not removed support for it. If you are referring
 to the removal of the linux-yocto-rt*bbappend files in dvhart/bsp-ng, that is
 done in favor of a new mechanism called the intel-common kernel, which
 uses a single kernel build across multiple BSPs, removing the need for the
 bbappend in each BSP layer - you'll note it is still present under
 common/recipes-kernel/linux.
 
 If you can provide some more context about what you are trying to do, we
 should be able to help make sure you are working with the right sources, and
 prioritize any development to fill any gaps.
 
 Thanks,
 
 Darren
 
 On 3/10/14, 21:45, Keskinarkaus, Teemu
 teemu.keskinark...@maximatecc.com wrote:
 
 Hi,
 
 I'm bit lost here. I'm looking for support for valleyisland that is for
 Dora branch of the Yocto. I cloned the dvhart/bsp-ng, but couldn't find
 any references to valleyisland or bay trail from there so I'm guessing
 I'm looking from the wrong place. Is there a right place? Or is the
 support 'coming soon' for Dora?
 
 I'm also bit disappointed to see that you chose to drop linux-rt
 support in favor of non-rt-linux. Mostly because I'm using the linux-rt
 variant.
 ;) So now I need to add it back there myself.
 
 Teemu Keskinarkaus
 Software system engineer
 
 maximatecc - Humans in control
 
 
 
 
 Actuant Corporation Email Notice
 
 This message is intended only for the use of the Addressee and may
 contain information that is PRIVILEGED and/or CONFIDENTIAL.
 This email is intended only for the personal and confidential use of
 the
 recipient(s) named above. If the reader of this email is not an
 intended recipient, you have received this email in error and any
 review, dissemination, distribution or copying is strictly prohibited.
 If you have received this email in error, please notify the sender
 immediately by return mail and permanently delete the copy you received.
 
 Thank you.
 --
 ___
 meta-intel mailing list
 meta-intel@yoctoproject.org
 https://lists.yoctoproject.org/listinfo/meta-intel
 
 
 
 --
 Darren Hart
 Yocto Project - Linux Kernel
 Intel Open Source Technology Center
 
 
 

-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

Re: [meta-intel] [PATCHv3 0/5] meta-valleyisland: add new bsp layer into meta-intel

[Chang, Rebecca Swee Fun]

 -Original Message-
 From: Kamble, Nitin A
 Sent: 12 February, 2014 1:34 AM
 To: Chang, Rebecca Swee Fun; meta-intel@yoctoproject.org
 Cc: ch...@yoctoproject.org
 Subject: Re: [meta-intel] [PATCHv3 0/5] meta-valleyisland: add new bsp layer
 into meta-intel
 
 
 On 2/11/2014 7:52 AM, rebecca.swee.fun.ch...@intel.com wrote:
  From: Chang, Rebecca Swee Fun rebecca.swee.fun.ch...@intel.com
 
  Hi all,
 
  This patchset is to add new BSP layer into meta-intel.
  meta-valleyisland is a BSP maintained by ISG. The BSP is made
  specifically for Intel Atom E38XX Processor E38XX Development Kit
  (formerly known as Valley Island). Valley Island BSP is meant to
  support Valley Island Development Kit, Bayley Bay CRB and Bakersport
 CRB.
 
  Please pull this patch set into meta-intel Dylan branch.
 
  Thank you.
 
  Rebecca
 Hi Rebecca,
Can you list what has changed from the last pull request? I notice that, 
 this
 pull request is missing updates to many review comments I gave to the last
 pull request.
 
 Nitin

PATCHv3 Change Log
In commit meta-valleyisland: new BSP layer for Intel Atom Processor E38XX
 Updated README. Added mkefidisk.sh to prepare an EFI enabled bootable 
image.

In commit meta-valleyisland: provide machine configuration for valleyisland
 Conf files are updated with new argument in APPENDS. This is to enable 
SMBUS driver by default.

Remove recipes-graphics as it is not needed.

In commit meta-valleyisland: add kernel recipe for valleyisland BSP
 Kernel recipe is updated according to the comments given. Remove the 
redundant SRC_URI.
 Update LINUX_VERSION to 3.8.13 which map to the commit IDs.
 Added additional argument in KERNEL_FEATURES. Kernel recipe enable PCI 
mode enumeration by default. User can remove 
features/valleyisland-io/valleyisland-io-pci.scc \ if they need to build ACPI 
mode image.

In commit meta-isg: add new meta-isg layer in dylan branch
 Updated typos in MAINTAINERS file

This is all the changes in PATCHv3. I will take now caution in submitting patch 
in future.
Thanks all.

Rebecca

 
  The following changes since commit
 b383d94711bf13f67ab00a07022cfcb512ff206c:
 
 MAINTAINERS: Add MOHONPEAK maintainer (2013-12-09 10:29:27 -0600)
 
  are available in the git repository at:
 
 git://git.yoctoproject.org/meta-intel-contrib rebeccas/meta-valleyisland-
 dylan
 
  http://git.yoctoproject.org/cgit.cgi/meta-intel-contrib/log/?h=rebecca
  s/meta-valleyisland-dylan
 
  Chang, Rebecca Swee Fun (5):
 meta-valleyisland: new BSP layer for Intel Atom Processor E38XX
 meta-valleyisland: provide machine configuration for valleyisland
 meta-valleyisland: provide a formfactor for valleyisland bsp
 meta-valleyisland: add kernel recipe for valleyisland BSP
 meta-isg: add new meta-isg layer in dylan branch
 
meta-isg/MAINTAINERS   |   43 
meta-isg/README|7 +
meta-isg/meta-valleyisland/COPYING.MIT |   17 ++
meta-isg/meta-valleyisland/README  |  218
 
meta-isg/meta-valleyisland/README.sources  |   18 ++
meta-isg/meta-valleyisland/conf/layer.conf |   14 ++
.../conf/machine/valleyisland-32.conf  |   20 ++
.../conf/machine/valleyisland-64.conf  |   22 ++
.../formfactor/valleyisland-32/machconfig  |3 +
.../formfactor/valleyisland-64/machconfig  |3 +
.../recipes-bsp/formfactor/formfactor_0.0.bbappend |3 +
.../recipes-kernel/linux/linux-yocto_3.8.bbappend  |   33 +++
12 files changed, 401 insertions(+)
create mode 100644 meta-isg/MAINTAINERS
create mode 100644 meta-isg/README
create mode 100644 meta-isg/meta-valleyisland/COPYING.MIT
create mode 100644 meta-isg/meta-valleyisland/README
create mode 100644 meta-isg/meta-valleyisland/README.sources
create mode 100644 meta-isg/meta-valleyisland/conf/layer.conf
create mode 100644 meta-isg/meta-
 valleyisland/conf/machine/valleyisland-32.conf
create mode 100644 meta-isg/meta-
 valleyisland/conf/machine/valleyisland-64.conf
create mode 100644 meta-isg/meta-valleyisland/recipes-
 bsp/formfactor/formfactor/valleyisland-32/machconfig
create mode 100644 meta-isg/meta-valleyisland/recipes-
 bsp/formfactor/formfactor/valleyisland-64/machconfig
create mode 100644 meta-isg/meta-valleyisland/recipes-
 bsp/formfactor/formfactor_0.0.bbappend
create mode 100644
  meta-isg/meta-valleyisland/recipes-kernel/linux/linux-yocto_3.8.bbappe
  nd
 

___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

Re: [meta-intel] [PATCH 0/6] [PATCHv2] meta-valleyisland: new bsp layer for Intel Atom Processor E38XX

[Chang, Rebecca Swee Fun]

Hi all,

Please ignore this submission for meta-intel master branch as we do not have 
any plan yet for valleyisland in master branch.
Meanwhile, please focus on the submission for meta-intel dylan branch.
Hope I do not make it confusing.

Thanks.

Rebecca

 -Original Message-
 From: Chang, Rebecca Swee Fun
 Sent: 05 February, 2014 5:26 PM
 To: meta-intel@yoctoproject.org
 Cc: Chang; Chang, Rebecca Swee Fun
 Subject: [PATCH 0/6] [PATCHv2] meta-valleyisland: new bsp layer for Intel
 Atom Processor E38XX
 
 From: Chang, Rebecca Swee Fun rebecca.swee.fun.ch...@intel.com
 
 Hi all,
 
 This pull request is the submission for meta-valleyisland.
 The image built was sanity tested with some basic driver I/O testing.
 
 There is a minor changes compare to the previous pull request.
 The kernel recipe has been updated with latest commit on meta branch.
 
 This pull request is to be pulled into meta-intel/master branch.
 I will send out another pull request for Dylan branch today.
 
 Thanks all.
 
 Rebecca
 
 The following changes since commit
 c5ca9f67121bff0b7400a175f005212234906b37:
 
   emgd-driver-bin: preserves the package stripping logic (2014-01-28 16:41:49
 -0600)
 
 are available in the git repository at:
 
   git://git.yoctoproject.org/meta-intel-contrib rebeccas/meta-valleyisland-
 master
   http://git.yoctoproject.org/cgit.cgi/meta-intel-
 contrib/log/?h=rebeccas/meta-valleyisland-master
 
 Chang, Rebecca Swee Fun (6):
   meta-isg: update MAINTAINERS file
   meta-valleyisland: new BSP layer for Intel Atom Processor E38XX
   meta-valleyisland: provide machine configuration for valleyisland
   meta-valleyisland: provide a formfactor for valleyisland bsp
   meta-valleyisland: add graphics support for valleyisland bsp
   meta-valleyisland: add kernel recipe for valleyisland BSP
 
  meta-isg/MAINTAINERS   |4 +
  meta-isg/meta-valleyisland/COPYING.MIT |   17 ++
  meta-isg/meta-valleyisland/README  |  217
 
  meta-isg/meta-valleyisland/README.sources  |   18 ++
  meta-isg/meta-valleyisland/conf/layer.conf |   14 ++
  .../conf/machine/valleyisland-32.conf  |   21 ++
  .../conf/machine/valleyisland-64.conf  |   23 +++
  .../formfactor/valleyisland-32/machconfig  |3 +
  .../formfactor/valleyisland-64/machconfig  |3 +
  .../recipes-bsp/formfactor/formfactor_0.0.bbappend |3 +
  .../xserver-xf86-config/valleyisland-32/xorg.conf  |   26 +++
  .../xserver-xf86-config/valleyisland-64/xorg.conf  |   26 +++
  .../xorg-xserver/xserver-xf86-config_0.1.bbappend  |1 +
  .../recipes-kernel/linux/linux-yocto_3.8.bbappend  |   32 +++
  14 files changed, 408 insertions(+)
  create mode 100644 meta-isg/meta-valleyisland/COPYING.MIT
  create mode 100644 meta-isg/meta-valleyisland/README  create mode
 100644 meta-isg/meta-valleyisland/README.sources
  create mode 100644 meta-isg/meta-valleyisland/conf/layer.conf
  create mode 100644 meta-isg/meta-valleyisland/conf/machine/valleyisland-
 32.conf
  create mode 100644 meta-isg/meta-valleyisland/conf/machine/valleyisland-
 64.conf
  create mode 100644 meta-isg/meta-valleyisland/recipes-
 bsp/formfactor/formfactor/valleyisland-32/machconfig
  create mode 100644 meta-isg/meta-valleyisland/recipes-
 bsp/formfactor/formfactor/valleyisland-64/machconfig
  create mode 100644 meta-isg/meta-valleyisland/recipes-
 bsp/formfactor/formfactor_0.0.bbappend
  create mode 100644 meta-isg/meta-valleyisland/recipes-graphics/xorg-
 xserver/xserver-xf86-config/valleyisland-32/xorg.conf
  create mode 100644 meta-isg/meta-valleyisland/recipes-graphics/xorg-
 xserver/xserver-xf86-config/valleyisland-64/xorg.conf
  create mode 100644 meta-isg/meta-valleyisland/recipes-graphics/xorg-
 xserver/xserver-xf86-config_0.1.bbappend
  create mode 100644 meta-isg/meta-valleyisland/recipes-kernel/linux/linux-
 yocto_3.8.bbappend
 
 --
 1.7.10.4

___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel