[yocto] [meta-selinux][PATCH 1/2] initscripts: add a local copy of devpts.sh
From: Wenzong Fan wenzong@windriver.com
Start point to make SELinux specific changes in devpts.sh, copied from
oe-core layer.
Signed-off-by: Wenzong Fan wenzong@windriver.com
---
recipes-core/initscripts/initscripts/devpts.sh| 28 +
recipes-core/initscripts/initscripts_1.0.bbappend |2 ++
2 files changed, 30 insertions(+)
create mode 100755 recipes-core/initscripts/initscripts/devpts.sh
diff --git a/recipes-core/initscripts/initscripts/devpts.sh
b/recipes-core/initscripts/initscripts/devpts.sh
new file mode 100755
index 000..c6043fb
--- /dev/null
+++ b/recipes-core/initscripts/initscripts/devpts.sh
@@ -0,0 +1,28 @@
+#!/bin/sh
+### BEGIN INIT INFO
+# Provides: devpts
+# Required-Start: udev
+# Required-Stop:
+# Default-Start: S
+# Default-Stop:
+# Short-Description: Mount /dev/pts file systems.
+### END INIT INFO
+
+. /etc/default/devpts
+
+if grep -q devpts /proc/filesystems
+then
+ #
+ # Create multiplexor device.
+ #
+ test -c /dev/ptmx || mknod -m 666 /dev/ptmx c 5 2
+
+ #
+ # Mount /dev/pts if needed.
+ #
+ if ! grep -q devpts /proc/mounts
+ then
+ mkdir -p /dev/pts
+ mount -t devpts devpts /dev/pts -ogid=${TTYGRP},mode=${TTYMODE}
+ fi
+fi
diff --git a/recipes-core/initscripts/initscripts_1.0.bbappend
b/recipes-core/initscripts/initscripts_1.0.bbappend
index 367cd6b..462db6f 100644
--- a/recipes-core/initscripts/initscripts_1.0.bbappend
+++ b/recipes-core/initscripts/initscripts_1.0.bbappend
@@ -1,5 +1,7 @@
PR .= .3
+FILESEXTRAPATHS_prepend := ${THISDIR}/${PN}:
+
do_install_append () {
cat -EOF ${D}${sysconfdir}/init.d/populate-volatile.sh
touch /var/log/lastlog
--
1.7.9.5
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-selinux][PATCH 2/2] initscripts/devpts.sh: fix context for /dev/pts
From: Wenzong Fan wenzong@windriver.com
devpts use file_use_trans to allocate security contexts. As there are no
range_trans rules for initrc_t mounting devpts, the security level of
mountpoint will be derived from the initrc process, to be systemhigh
(s15:c0.c1023), instead of expected systemlow(s0).
This will block login shells to search PTYs, so use restorecon to fix
this.
Signed-off-by: Wenzong Fan wenzong@windriver.com
---
recipes-core/initscripts/initscripts/devpts.sh |1 +
1 file changed, 1 insertion(+)
diff --git a/recipes-core/initscripts/initscripts/devpts.sh
b/recipes-core/initscripts/initscripts/devpts.sh
index c6043fb..a0b037f 100755
--- a/recipes-core/initscripts/initscripts/devpts.sh
+++ b/recipes-core/initscripts/initscripts/devpts.sh
@@ -24,5 +24,6 @@ then
then
mkdir -p /dev/pts
mount -t devpts devpts /dev/pts -ogid=${TTYGRP},mode=${TTYMODE}
+ test ! -x /sbin/restorecon || /sbin/restorecon -F /dev/pts
fi
fi
--
1.7.9.5
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-selinux][PATCH 0/2] initscripts/devpts.sh: fix context for /dev/pts
From: Wenzong Fan wenzong@windriver.com devpts use file_use_trans to allocate security contexts. As there are no range_trans rules for initrc_t mounting devpts, the security level of mountpoint will be derived from the initrc process, to be systemhigh (s15:c0.c1023), instead of expected systemlow(s0). This will block login shells to search PTYs, so use restorecon to fix this. The following changes since commit 368f65a475069ed384d82be09c2515fb765e22ec: initscripts/checkroot.sh: restore file contexts for /run (2014-05-09 08:59:54 -0400) are available in the git repository at: git://git.pokylinux.org/poky-contrib wenzong/fix-pts http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=wenzong/fix-pts Wenzong Fan (2): initscripts: add a local copy of devpts.sh initscripts/devpts.sh: fix context for /dev/pts recipes-core/initscripts/initscripts/devpts.sh| 29 + recipes-core/initscripts/initscripts_1.0.bbappend |2 ++ 2 files changed, 31 insertions(+) create mode 100755 recipes-core/initscripts/initscripts/devpts.sh -- 1.7.9.5 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Question / issue
On 14-05-12 01:56 AM, Paul McGougan wrote: From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com] Secondly, (and this is our main issue) I have found that by adding the do_install_append function, even if it is completely empty, whenever I try to bitbake anything that depends on the kernel, that bitbake always re-runs the kernel install stage, even when there have been no changes. Literally I can run a bitbake, then run the same bitbake command again, and both times the kernel install stage gets run (this is a problem because it takes a long time to run). It appears to be happening because the stampfile is not found every time (the hash appears to be wrong). Is this a bug? Is there a fix or work-around for this problem? In this front, I'm not the best reference. Checking the sstate signature might help, it should show which variables are being used .. and possibly invalidating the signature, triggering the steps to run again. Thanks Bruce. Just for reference of anyone else who runs into a similar issue our issue was: 1. The do_install_append function was not *really* empty, the content of it was commented out. 2. The dependency parser when parsing recipes not only looks for content changes, but for also for changes to the values of referenced variables, and unfortunately it still performs variable-value substitution in commented-out code. In our case, we had the variable $DATETIME in there (but commented out), this caused the dependency checker to substitute in the current value for DATETIME which of course changed on each run. Aha. That's what I thought it might be (and what I've been hit by before in the past), sstate signature checking showed the variable in these other cases .. so I thought I'd suggest it. Glad to hear you have a working solution. Cheers, Bruce The fix was to add: do_install[vardepsexclude] += DATETIME Regards, Paul McGougan Confidentiality Notice: This message (including attachments) is a private communication solely for use of the intended recipient(s). If you are not the intended recipient(s) or believe you received this message in error, notify the sender immediately and then delete this message. Any other use, retention, dissemination or copying is prohibited and may be a violation of law, including the Electronic Communication Privacy Act of 1986. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Question / issue
On Monday 12 May 2014 07:03:55 Bruce Ashfield wrote: On 14-05-12 01:56 AM, Paul McGougan wrote: From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com] Secondly, (and this is our main issue) I have found that by adding the do_install_append function, even if it is completely empty, whenever I try to bitbake anything that depends on the kernel, that bitbake always re-runs the kernel install stage, even when there have been no changes. Literally I can run a bitbake, then run the same bitbake command again, and both times the kernel install stage gets run (this is a problem because it takes a long time to run). It appears to be happening because the stampfile is not found every time (the hash appears to be wrong). Is this a bug? Is there a fix or work-around for this problem? In this front, I'm not the best reference. Checking the sstate signature might help, it should show which variables are being used .. and possibly invalidating the signature, triggering the steps to run again. Thanks Bruce. Just for reference of anyone else who runs into a similar issue our issue was: 1. The do_install_append function was not *really* empty, the content of it was commented out. 2. The dependency parser when parsing recipes not only looks for content changes, but for also for changes to the values of referenced variables, and unfortunately it still performs variable-value substitution in commented-out code. In our case, we had the variable $DATETIME in there (but commented out), this caused the dependency checker to substitute in the current value for DATETIME which of course changed on each run. Aha. That's what I thought it might be (and what I've been hit by before in the past), sstate signature checking showed the variable in these other cases .. so I thought I'd suggest it. Glad to hear you have a working solution. The fix was to add: do_install[vardepsexclude] += DATETIME Er, if DATETIME is in the dependencies for this task and that is a bug in the core recipe, we should fix it in the core. The question is how is it getting in there? Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] RPM to Verify Installed Packages
On 5/9/14, 12:14 PM, Mark Hatle wrote: On 5/7/14, 7:46 AM, Diego Sueiro wrote: Folks, I'm looking at this issue. I'd suggest you open a bug in the Yocto Project bugzilla. Feel free to assign it to me. (I'll end up with it anyway...) I opened a bug, 6309. I've sent a fix for master, and we can work it back into previous versions once approved by oe-core. --Mark --Mark On Tue, May 6, 2014 at 3:48 PM, Diego Sueiro diego.sue...@gmail.com mailto:diego.sue...@gmail.com wrote: On Tue, May 6, 2014 at 3:39 PM, Khem Raj raj.k...@gmail.com mailto:raj.k...@gmail.com wrote: On Tue, May 6, 2014 at 11:34 AM, Diego Sueiro diego.sue...@gmail.com mailto:diego.sue...@gmail.com wrote: It's hard to say. But when I try to execute it I receive: cannot execute binary file. And the output of file command is: data. My bet is that the system was powered down during the update process. what happens if you reinstall it ? It works. But the problem is that --verify option is not working. Even if I remove a file from the installed package it did not point for a missing file. Any thoughts? Regards, -- *dS Diego Sueiro Administrador do Embarcados www.embarcados.com.br http://www.embarcados.com.br/?utm_source=assinatura_diegoutm_medium=e-mailutm_campaign=Assinatura%20Email%20Diego /*long live rock 'n roll*/ -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-atmel] automatic bootloaders generation
please find attached patches for
- automatic bootloaders generation
https://github.com/linux4sam/meta-atmel/pull/16
Ciao
--
Marco Cavallini | KOAN sas | Bergamo - Italia
embedded and real-time software engineering
Phone:+39-035-255.235 - Fax:+39-178-22.39.748
http://www.KoanSoftware.com
From cc08f5529a08498b07482f80cd0d99a391af034d Mon Sep 17 00:00:00 2001
From: Marco Cavallini m.cavall...@koansoftware.com
Date: Mon, 12 May 2014 17:32:24 +0200
Subject: [meta-atmel 1/2] Added bootloaders to the recipe of every machine
* Include file with
* EXTRA_IMAGEDEPENDS += at91bootstrap u-boot
Signed-off-by: Marco Cavallini m.cavall...@koansoftware.com
---
conf/machine/at91sam9rlek.conf | 1 +
conf/machine/at91sam9x5ek.conf | 1 +
conf/machine/include/bootloaders.inc | 2 ++
conf/machine/sama5d3_xplained.conf | 8 +---
conf/machine/sama5d3xek.conf | 1 +
5 files changed, 6 insertions(+), 7 deletions(-)
create mode 100644 conf/machine/include/bootloaders.inc
diff --git a/conf/machine/at91sam9rlek.conf b/conf/machine/at91sam9rlek.conf
index 6ed6f81..4a41b19 100644
--- a/conf/machine/at91sam9rlek.conf
+++ b/conf/machine/at91sam9rlek.conf
@@ -3,6 +3,7 @@
#@DESCRIPTION: Machine configuration for Atmel's evaluation board
require conf/machine/include/tune-arm926ejs.inc
+require conf/machine/include/bootloaders.inc
MACHINE_FEATURES = kernel26 apm alsa ext2 ext3 usbgadget screen touchscreen ppp
diff --git a/conf/machine/at91sam9x5ek.conf b/conf/machine/at91sam9x5ek.conf
index 5308536..de5598a 100644
--- a/conf/machine/at91sam9x5ek.conf
+++ b/conf/machine/at91sam9x5ek.conf
@@ -3,6 +3,7 @@
#@DESCRIPTION: Machine configuration for Atmel's evaluation board
require conf/machine/include/tune-arm926ejs.inc
+require conf/machine/include/bootloaders.inc
MACHINE_FEATURES = kernel26 apm alsa ext2 ext3 usbhost usbgadget screen camera can touchscreen ppp
KERNEL_DEVICETREE = ${S}/arch/arm/boot/dts/at91sam9g25ek.dts \
diff --git a/conf/machine/include/bootloaders.inc b/conf/machine/include/bootloaders.inc
new file mode 100644
index 000..162b7a1
--- /dev/null
+++ b/conf/machine/include/bootloaders.inc
@@ -0,0 +1,2 @@
+# Add bootloaders to the images of every machine
+EXTRA_IMAGEDEPENDS += at91bootstrap u-boot
diff --git a/conf/machine/sama5d3_xplained.conf b/conf/machine/sama5d3_xplained.conf
index dcbcedb..24fe2a2 100644
--- a/conf/machine/sama5d3_xplained.conf
+++ b/conf/machine/sama5d3_xplained.conf
@@ -3,6 +3,7 @@
#@DESCRIPTION: Machine configuration for Atmel's evaluation board
require conf/machine/include/tune-cortexa5.inc
+require conf/machine/include/bootloaders.inc
MACHINE_FEATURES = kernel26 apm alsa ext2 ext3 usbhost usbgadget screen camera can touchscreen ppp wifi
KERNEL_DEVICETREE = \
@@ -34,10 +35,3 @@ UBI_VOLNAME = rootfs
UBOOT_MACHINE = sama5d3xek_nandflash_config
UBOOT_ENTRYPOINT = 0x20008000
UBOOT_LOADADDRESS = 0x20008000
-
-EXTRA_IMAGEDEPENDS += at91bootstrap u-boot-at91
-
-module_autoload_atmel_usba_udc = atmel_usba_udc
-module_autoload_g_serial = g_serial
-
-ROOTFS_POSTPROCESS_COMMAND += sama5d3_xplained_rootfs_postprocess;
diff --git a/conf/machine/sama5d3xek.conf b/conf/machine/sama5d3xek.conf
index 65487be..07d967d 100644
--- a/conf/machine/sama5d3xek.conf
+++ b/conf/machine/sama5d3xek.conf
@@ -3,6 +3,7 @@
#@DESCRIPTION: Machine configuration for Atmel's evaluation board
require conf/machine/include/tune-cortexa5.inc
+require conf/machine/include/bootloaders.inc
MACHINE_FEATURES = kernel26 apm alsa ext2 ext3 usbhost usbgadget screen camera can touchscreen ppp
KERNEL_DEVICETREE = \
--
1.8.4
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-atmel] Unified IMAGE_POSTPROCESS_COMMAND in image recipes
please find attached patches for
- Unified IMAGE_POSTPROCESS_COMMAND in your image recipes
https://github.com/linux4sam/meta-atmel/pull/11
Ciao
--
Marco Cavallini | KOAN sas | Bergamo - Italia
embedded and real-time software engineering
Phone:+39-035-255.235 - Fax:+39-178-22.39.748
http://www.KoanSoftware.com
From 0050a6a7fa34930f587c07b1c7ae9a73b4c3ba91 Mon Sep 17 00:00:00 2001
From: Marco Cavallini m.cavall...@koansoftware.com
Date: Mon, 12 May 2014 17:34:20 +0200
Subject: [meta-atmel 2/2] Unified usba_udc and g_serial setting for all
atmel-xplained-*-image.bb
* Moved common parts in atmel-demo-image.inc
Signed-off-by: Marco Cavallini m.cavall...@koansoftware.com
---
recipes-core/images/atmel-demo-image.inc | 18 ++
recipes-core/images/atmel-xplained-demo-image.bb | 12
recipes-core/images/atmel-xplained-lcd-demo-image.bb | 12
3 files changed, 18 insertions(+), 24 deletions(-)
diff --git a/recipes-core/images/atmel-demo-image.inc b/recipes-core/images/atmel-demo-image.inc
index 3101e20..394bebe 100644
--- a/recipes-core/images/atmel-demo-image.inc
+++ b/recipes-core/images/atmel-demo-image.inc
@@ -35,3 +35,21 @@ inherit core-image
# we don't need the kernel in the image
ROOTFS_POSTPROCESS_COMMAND += rm -f ${IMAGE_ROOTFS}/boot/*Image*;
+
+# Unified usba_udc and g_serial
+module_autoload_atmel_usba_udc = atmel_usba_udc
+module_autoload_g_serial = g_serial
+
+sama5d3_xplained_rootfs_postprocess() {
+curdir=$PWD
+cd ${IMAGE_ROOTFS}
+
+# autoload needed modules
+cd etc
+echo atmel_usba_udc modules
+echo g_serial modules
+
+cd $curdir
+}
+
+ROOTFS_POSTPROCESS_COMMAND += sama5d3_xplained_rootfs_postprocess;
diff --git a/recipes-core/images/atmel-xplained-demo-image.bb b/recipes-core/images/atmel-xplained-demo-image.bb
index 5a88add..59b4572 100644
--- a/recipes-core/images/atmel-xplained-demo-image.bb
+++ b/recipes-core/images/atmel-xplained-demo-image.bb
@@ -8,15 +8,3 @@ IMAGE_INSTALL += \
packagegroup-base-3g \
packagegroup-base-usbhost \
-
-sama5d3_xplained_rootfs_postprocess() {
-curdir=$PWD
-cd ${IMAGE_ROOTFS}
-
-# autoload needed modules
-cd etc
-echo atmel_usba_udc modules
-echo g_serial modules
-
-cd $curdir
-}
diff --git a/recipes-core/images/atmel-xplained-lcd-demo-image.bb b/recipes-core/images/atmel-xplained-lcd-demo-image.bb
index cecd4c3..6cda1c3 100644
--- a/recipes-core/images/atmel-xplained-lcd-demo-image.bb
+++ b/recipes-core/images/atmel-xplained-lcd-demo-image.bb
@@ -15,15 +15,3 @@ IMAGE_INSTALL += \
tslib-tests \
tslib-calibrate \
-
-sama5d3_xplained_rootfs_postprocess() {
-curdir=$PWD
-cd ${IMAGE_ROOTFS}
-
-# autoload needed modules
-cd etc
-echo atmel_usba_udc modules
-echo g_serial modules
-
-cd $curdir
-}
--
1.8.4
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] RPM to Verify Installed Packages
Mark, On Mon, May 12, 2014 at 12:37 PM, Mark Hatle mark.ha...@windriver.comwrote: On 5/9/14, 12:14 PM, Mark Hatle wrote: On 5/7/14, 7:46 AM, Diego Sueiro wrote: Folks, I'm looking at this issue. I'd suggest you open a bug in the Yocto Project bugzilla. Feel free to assign it to me. (I'll end up with it anyway...) I opened a bug, 6309. I've sent a fix for master, and we can work it back into previous versions once approved by oe-core. Thanks for your effort. Regards, -- *dS Diego Sueiro Administrador do Embarcados www.embarcados.com.brhttp://www.embarcados.com.br/?utm_source=assinatura_diegoutm_medium=e-mailutm_campaign=Assinatura%20Email%20Diego /*long live rock 'n roll*/ -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] New meta-amd mailing list announcement
There is a new mailing list for AMD platform/board related patches and discussion. You can sign up here: https://lists.yoctoproject.org/listinfo/meta-amd The meta-amd layer git repository is publicly available here: git://git.yoctoproject.org/meta-amd (cgit web interface here: http://git.yoctoproject.org/cgit/cgit.cgi/meta-amd/) Please checkout the README at the top level for details on submitting patches. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Question / issue
On 2014-05-12 07:56, Paul McGougan wrote: From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com] Secondly, (and this is our main issue) I have found that by adding the do_install_append function, even if it is completely empty, whenever I try to bitbake anything that depends on the kernel, that bitbake always re-runs the kernel install stage, even when there have been no changes. Literally I can run a bitbake, then run the same bitbake command again, and both times the kernel install stage gets run (this is a problem because it takes a long time to run). It appears to be happening because the stampfile is not found every time (the hash appears to be wrong). Is this a bug? Is there a fix or work-around for this problem? In this front, I'm not the best reference. Checking the sstate signature might help, it should show which variables are being used .. and possibly invalidating the signature, triggering the steps to run again. Thanks Bruce. Just for reference of anyone else who runs into a similar issue our issue was: 1. The do_install_append function was not *really* empty, the content of it was commented out. To me, Thats sound like a bug in the dependency parser. It should not parse for changes in comments, i.e. in this case do_install_append comments. Or perhaps in variable expansion, which could be avoided in commented sections. Br, David -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] New meta-amd mailing list announcement
Goog initiative guys. One quick question(out of curiosity): what is with the bbappend near the bb file? Alex On Monday, May 12, 2014 9:32 PM, Sean Hudson sean_hud...@mentor.com wrote: There is a new mailing list for AMD platform/board related patches and discussion. You can sign up here: https://lists.yoctoproject.org/listinfo/meta-amd The meta-amd layer git repository is publicly available here: git://git.yoctoproject.org/meta-amd (cgit web interface here: http://git.yoctoproject.org/cgit/cgit.cgi/meta-amd/) Please checkout the README at the top level for details on submitting patches. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto-- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [OE-core] New meta-amd mailing list announcement
On Mon, May 12, 2014 at 2:58 PM, Sean Hudson sean_hud...@mentor.com wrote: There is a new mailing list for AMD platform/board related patches and discussion. You can sign up here: https://lists.yoctoproject.org/listinfo/meta-amd The meta-amd layer git repository is publicly available here: git://git.yoctoproject.org/meta-amd (cgit web interface here: http://git.yoctoproject.org/cgit/cgit.cgi/meta-amd/) Please checkout the README at the top level for details on submitting patches. What are the layer dependencies? -- Otavio Salvador O.S. Systems http://www.ossystems.com.brhttp://code.ossystems.com.br Mobile: +55 (53) 9981-7854Mobile: +1 (347) 903-9750 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Agenda: Yocto Project Technical Team Meeting - Tuesday, May 6, 2014 8:00 AM US Pacific Time
Agenda: * Opens collection - 5 min (Stephen) * Yocto 1.7 status - 5 min (Stephen/team) https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.7_Status https://wiki.yoctoproject.org/wiki/Yocto_1.7_Schedule https://wiki.yoctoproject.org/wiki/Yocto_1.7_Features * SWAT team rotation: Paul - Saul https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team * Opens - 10 min * Team Sharing - 10 min -Original Appointment- We encourage people attending the meeting to logon the Yocto Project IRC chancel during the meeting (optional): Yocto IRC: http://webchat.freenode.net/?channels=#yocto IRC Tutorial: http://www.irchelp.org/irchelp/irctutorial.html Conference details Conference name: Yocto Project Technical Team Conference date/start time: Tue Jun 25, 2013 at 11:00 AM Eastern Daylight Time (GMT-0400) Participants: 30 Duration: 30 minutes Participant passcode: 42001078 Dial-in number: 1.972.995. US Toll Free number: 1.877.561.6828 BlackBerry users, click this link to join your conference as a participant: 1.972.995.x42001078# Depending on where you are dialing from, either your BlackBerry will pause and enter the passcode automatically or you will be prompted to click again to dial the passcode. Local and Global Access Numbers Country Dial-in number Australia: 1800 636 843 Czech Republic: 242 430 350 China (Beijing): From office dial 8-995 or 8784277 Beijing Out of Office dial 5878 4277 China (Shanghai): From office dial 8-995 or 3073322 Shanghai Out of Office dial 2307 3322 China (Shenzen): From office dial 8-995 or 6007877 Shenzen Out of Office dial 2600 7877 China (Other Cities): From IP phone dial 8-995 Other cities - Non IP phone dial 021-23073322 Denmark: 8060 1400 Finland: 09 41333477 France: 0497 275888 Germany: 08161 803232 Holland: 030 2417490 India: BSNL subscribers use 1800 425 9996 (Toll Free) Airtel subscribers use 0008 009 861 212 (Toll Free) From TI Campus use 8995 Others use 2509 9555 (Landline within Bangalore) or 80 2509 9555 (Outside Bangalore) Israel: 09 790 6715 Italy: 039 69061234 (039 is local city code not country code) Japan: From TI Campus use 8 995 Outside TI use 03 4331 3777 Malaysia: From IP phone dial 2643799 From Kuala Lumpur dial 4264 3799 Outside Kuala Lumpur dial (03)4264 3799 Norway: 2 295 8744 Philippines: From Baguio City use 4471177 From Metro Manila area use 8702477 Singapore: From IP phone dial 3894777 Outside TI use 6389 4777 South Korea: From IP phone dial 5606998 From Seoul dial 5606998 Outside Seoul dial (02)5606998 Sweden: 08 58755577 Taiwan: From IP phone dial 1363 From Taipei dial 2241 1363 Outside Taipei dial (02)2241 1363 Turkey: Landline Only dial 0811 288 0001 then enter 877 633 1123 UK: 01908 355599 US: 972 995 or 1877 561 6828 Recurring conferences First scheduled conference: Tue Jun 25, 2013 Recurrence frequency: Weekly - Every 1 week(s) on Tuesday Recurrence ends: End after 52 occurrences Thanks, Stephen K. Jolley Yocto Project Program Manager INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124 * Work Telephone: (503) 712-0534 *Cell:(208) 244-4460 * Email: stephen.k.jol...@intel.com -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [OE-core] OEDAM: OpenEmbedded Developers (Americas) Meeting
Meeting notes have been published on the OEDAM page: http://openembedded.org/wiki/OEDAM#Minutes Jefro takes the blame for typos and other reporting errors. On Wed, May 7, 2014 at 4:18 PM, Denys Dmytriyenko de...@denix.org wrote: The OpenEmbedded Board of Directors would like to thank everyone who was able to participate (either in person in Santa Clara or online) in our first OEDAM OpenEmbedded Developers (Americas) Meeting on May 2nd and 3rd! The meeting was a huge success and a lot of fun! We would also like to thank Ettus Research/NI for providing the premises, as well as Jefro and the Yocto Project for sponsoring the event and providing food! The meeting minutes should be published shortly. -- Denys On Thu, Feb 20, 2014 at 07:03:24PM -0500, Philip Balister wrote: The OpenEmbedded Project is holding a developers meeting May 2-3, 2014, in Santa Clara, CA. This meeting is immediately after the Embedded Linux Conference North America. All active OpenEmbedded and Yocto Project developers are invited to attend. NOTE: this is a development meeting for the project itself, not a training session. May 2-3, 2014 time TBD Ettus Research/National Instruments 4600 Patrick Henry Drive Santa Clara, CA 95054 USA Lunch will be provided on both days. For more information and to add yourself to the list of attendees, see the wiki page at http://openembedded.org/wiki/OEDAM Here are a couple of photos from 2009: http://www.flickr.com/photos/32615155@N00/sets/72157622653686647/ I'd like to thank Jefro for help with this announcement. Any errors are mine though. Philip, OpenEmbedded eV Chair. ___ Openembedded-core mailing list openembedded-c...@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core -- ___ Openembedded-core mailing list openembedded-c...@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core -- Jeff Osier-Mixon @Intel Yocto Project Community Manager http://yoctoproject.org -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Question / issue
-Original Message- From: Paul Eggleton [mailto:paul.eggle...@linux.intel.com] Er, if DATETIME is in the dependencies for this task and that is a bug in the core recipe, we should fix it in the core. The question is how is it getting in there? The DATETIME was being introduced in my bbappend, not the core recipe. So I don't think a change is needed to the core recipe. But see my response to David's email. Regards, Paul Confidentiality Notice: This message (including attachments) is a private communication solely for use of the intended recipient(s). If you are not the intended recipient(s) or believe you received this message in error, notify the sender immediately and then delete this message. Any other use, retention, dissemination or copying is prohibited and may be a violation of law, including the Electronic Communication Privacy Act of 1986. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Question / issue
-Original Message- From: David Nyström [mailto:david.c.nyst...@gmail.com] To me, Thats sound like a bug in the dependency parser. It should not parse for changes in comments, i.e. in this case do_install_append comments. Or perhaps in variable expansion, which could be avoided in commented sections. Hi David. Yes, I agree that the dependency parser should be altered. I would suggest your 2nd suggestion would be the most appropriate, i.e. do not perform variable expansion in commented lines. Regards, Paul Confidentiality Notice: This message (including attachments) is a private communication solely for use of the intended recipient(s). If you are not the intended recipient(s) or believe you received this message in error, notify the sender immediately and then delete this message. Any other use, retention, dissemination or copying is prohibited and may be a violation of law, including the Electronic Communication Privacy Act of 1986. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[linux-yocto] [PATCH 1/5] meta: haswell-wc: removed using of common-pc-64.scc
From: Chan Wei Sern wei.sern.c...@intel.com Removed using of bsp/common-pc-64/common-pc-64.scc from haswell-wc-standard.scc and haswell-wc-preempt-rt.scc. Added ktypes/standard/standard.scc for haswell-wc-standard.scc This is because we are migrating the BSP to use intel-common. Signed-off-by: Chan Wei Sern wei.sern.c...@intel.com --- meta/cfg/kernel-cache/bsp/haswell-wc/haswell-wc-preempt-rt.scc |2 +- meta/cfg/kernel-cache/bsp/haswell-wc/haswell-wc-standard.scc |2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/meta/cfg/kernel-cache/bsp/haswell-wc/haswell-wc-preempt-rt.scc b/meta/cfg/kernel-cache/bsp/haswell-wc/haswell-wc-preempt-rt.scc index 88614a7..07e5e8e 100644 --- a/meta/cfg/kernel-cache/bsp/haswell-wc/haswell-wc-preempt-rt.scc +++ b/meta/cfg/kernel-cache/bsp/haswell-wc/haswell-wc-preempt-rt.scc @@ -4,7 +4,7 @@ define KARCH x86_64 # no new branch required, re-use the ktypes/preempt-rt/preempt-rt.scc branch include ktypes/preempt-rt/preempt-rt.scc -include bsp/common-pc-64/common-pc-64.scc + include haswell-wc.scc diff --git a/meta/cfg/kernel-cache/bsp/haswell-wc/haswell-wc-standard.scc b/meta/cfg/kernel-cache/bsp/haswell-wc/haswell-wc-standard.scc index b715a4f..bc6bc7b 100644 --- a/meta/cfg/kernel-cache/bsp/haswell-wc/haswell-wc-standard.scc +++ b/meta/cfg/kernel-cache/bsp/haswell-wc/haswell-wc-standard.scc @@ -2,7 +2,7 @@ define KMACHINE haswell-wc define KTYPE standard define KARCH x86_64 -include bsp/common-pc-64/common-pc-64-standard.scc +include ktypes/standard/standard.scc include haswell-wc.scc -- 1.7.10.4 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 0/5] Update meta branch for meta-ISGs platforms configuration
From: Chan Wei Sern wei.sern.c...@intel.com Hi All, This is a patch series that consist of below: 1. Removed using of common-pc-64.scc from haswell-wc,crystalforest and mohonpeak. 2. Start using ktypes/standard/standard.scc for meta-ISG platforms. 3. Add back RTC configuration for crystalforest after changing from common-pc-64.scc to standard.scc. 4. Add back USB HID configuration for crystalforest after changing from common-pc-64.scc to standard.scc. Please help to pull this patch into linux-yocto-3.10:meta branch. Thanks. Regards, Chan Wei Sern The following changes since commit 617c6158c3d5b931f0d6131e0b0a7b374c792599: mei.cfg: enable Intel chipsets (2014-05-05 09:46:42 -0400) are available in the git repository at: git://git.yoctoproject.org/linux-yocto-contrib wchan9/intel-common-meta http://git.yoctoproject.org/cgit.cgi/linux-yocto-contrib/log/?h=wchan9/intel-common-meta Chan Wei Sern (2): meta: haswell-wc: removed using of common-pc-64.scc meta: mohonpeak: removed using of common-pc-64.scc Sreeju Slevaraj (3): meta: crystalforest: removed using of common-pc-64.scc meta: crystalforest: included RTC configuration meta: crystalforest: included USB HID configuration .../cfg/kernel-cache/bsp/crystalforest/crystalforest-preempt-rt.scc |1 - meta/cfg/kernel-cache/bsp/crystalforest/crystalforest-standard.scc |3 +-- meta/cfg/kernel-cache/bsp/crystalforest/crystalforest.cfg |3 +++ meta/cfg/kernel-cache/bsp/crystalforest/crystalforest.scc |2 ++ meta/cfg/kernel-cache/bsp/haswell-wc/haswell-wc-preempt-rt.scc |2 +- meta/cfg/kernel-cache/bsp/haswell-wc/haswell-wc-standard.scc|2 +- meta/cfg/kernel-cache/bsp/mohonpeak/mohonpeak-preempt-rt.scc|1 - 7 files changed, 8 insertions(+), 6 deletions(-) -- 1.7.10.4 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 5/5] meta: crystalforest: included USB HID configuration
From: Sreeju Slevaraj sreeju.armughanx.selva...@intel.com Since migrating this BSP to use intel-common, we need to add the configuration required to enable USB HID Signed-off-by: Sreeju Slevaraj sreeju.armughanx.selva...@intel.com Signed-off-by: Chan Wei Sern wei.sern.c...@intel.com --- meta/cfg/kernel-cache/bsp/crystalforest/crystalforest.cfg |3 +++ 1 file changed, 3 insertions(+) diff --git a/meta/cfg/kernel-cache/bsp/crystalforest/crystalforest.cfg b/meta/cfg/kernel-cache/bsp/crystalforest/crystalforest.cfg index 91a94a7..35a1d1e 100644 --- a/meta/cfg/kernel-cache/bsp/crystalforest/crystalforest.cfg +++ b/meta/cfg/kernel-cache/bsp/crystalforest/crystalforest.cfg @@ -35,3 +35,6 @@ CONFIG_I2C_I801=y CONFIG_ITCO_WDT=y CONFIG_ITCO_VENDOR_SUPPORT=y CONFIG_LPC_ICH=y + +CONFIG_USB_HID=y +CONFIG_USB_HIDDEV=y -- 1.7.10.4 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 4/5] meta: crystalforest: included RTC configuration
From: Sreeju Slevaraj sreeju.armughanx.selva...@intel.com Since migrating this BSP to use intel-common, we need to add RTC configuration to enable real time clock. Signed-off-by: Sreeju Slevaraj sreeju.armughanx.selva...@intel.com Signed-off-by: Chan Wei Sern wei.sern.c...@intel.com --- meta/cfg/kernel-cache/bsp/crystalforest/crystalforest.scc |2 ++ 1 file changed, 2 insertions(+) diff --git a/meta/cfg/kernel-cache/bsp/crystalforest/crystalforest.scc b/meta/cfg/kernel-cache/bsp/crystalforest/crystalforest.scc index e309144..d62293cb 100644 --- a/meta/cfg/kernel-cache/bsp/crystalforest/crystalforest.scc +++ b/meta/cfg/kernel-cache/bsp/crystalforest/crystalforest.scc @@ -23,3 +23,5 @@ include features/pci/pci.scc #Enable GCC inlining include features/inline/inline.scc + +include cfg/timer/rtc.scc -- 1.7.10.4 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 2/5] meta: mohonpeak: removed using of common-pc-64.scc
From: Chan Wei Sern wei.sern.c...@intel.com Removed using of bsp/common-pc-64/common-pc-64.scc from mohonpeak-preempt-rt.scc This is because we are migrating the BSP to use intel-common. Signed-off-by: Chan Wei Sern wei.sern.c...@intel.com --- meta/cfg/kernel-cache/bsp/mohonpeak/mohonpeak-preempt-rt.scc |1 - 1 file changed, 1 deletion(-) diff --git a/meta/cfg/kernel-cache/bsp/mohonpeak/mohonpeak-preempt-rt.scc b/meta/cfg/kernel-cache/bsp/mohonpeak/mohonpeak-preempt-rt.scc index c1fdef1..89f6064 100644 --- a/meta/cfg/kernel-cache/bsp/mohonpeak/mohonpeak-preempt-rt.scc +++ b/meta/cfg/kernel-cache/bsp/mohonpeak/mohonpeak-preempt-rt.scc @@ -4,7 +4,6 @@ define KARCH x86_64 # no new branch required, re-use the ktypes/preempt-rt/preempt-rt.scc branch include ktypes/preempt-rt/preempt-rt.scc -include bsp/common-pc-64/common-pc-64.scc include mohonpeak.scc -- 1.7.10.4 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 3/5] meta: crystalforest: removed using of common-pc-64.scc
From: Sreeju Slevaraj sreeju.armughanx.selva...@intel.com Removed using of bsp/common-pc-64/common-pc-64.scc from crystalforest-preempt-rt.scc and crystalforeset-standard.scc. Added ktypes/standard/standard.scc for crystalforest-standard.scc. This is because we are migrating the BSP to use intel-common. Signed-off-by: Sreeju Slevaraj sreeju.armughanx.selva...@intel.com Signed-off-by: Chan Wei Sern wei.sern.c...@intel.com --- .../cfg/kernel-cache/bsp/crystalforest/crystalforest-preempt-rt.scc |1 - meta/cfg/kernel-cache/bsp/crystalforest/crystalforest-standard.scc |3 +-- 2 files changed, 1 insertion(+), 3 deletions(-) diff --git a/meta/cfg/kernel-cache/bsp/crystalforest/crystalforest-preempt-rt.scc b/meta/cfg/kernel-cache/bsp/crystalforest/crystalforest-preempt-rt.scc index cd6bfde..2cef533 100644 --- a/meta/cfg/kernel-cache/bsp/crystalforest/crystalforest-preempt-rt.scc +++ b/meta/cfg/kernel-cache/bsp/crystalforest/crystalforest-preempt-rt.scc @@ -4,7 +4,6 @@ define KARCH x86_64 # no new branch required, re-use the ktypes/preempt-rt/preempt-rt.scc branch include ktypes/preempt-rt/preempt-rt.scc -include bsp/common-pc-64/common-pc-64.scc include crystalforest.scc diff --git a/meta/cfg/kernel-cache/bsp/crystalforest/crystalforest-standard.scc b/meta/cfg/kernel-cache/bsp/crystalforest/crystalforest-standard.scc index c3b416c..bfd8359 100644 --- a/meta/cfg/kernel-cache/bsp/crystalforest/crystalforest-standard.scc +++ b/meta/cfg/kernel-cache/bsp/crystalforest/crystalforest-standard.scc @@ -2,8 +2,7 @@ define KMACHINE crystalforest define KTYPE standard define KARCH x86_64 -include bsp/common-pc-64/common-pc-64-standard.scc -branch crystalforest +include ktypes/standard/standard.scc include crystalforest.scc -- 1.7.10.4 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH 0/5] Update meta branch for meta-ISGs platforms configuration
On 5/12/2014 3:20 PM, wei.sern.c...@intel.com wrote: From: Chan Wei Sern wei.sern.c...@intel.com Hi All, This is a patch series that consist of below: 1. Removed using of common-pc-64.scc from haswell-wc,crystalforest and mohonpeak. 2. Start using ktypes/standard/standard.scc for meta-ISG platforms. 3. Add back RTC configuration for crystalforest after changing from common-pc-64.scc to standard.scc. 4. Add back USB HID configuration for crystalforest after changing from common-pc-64.scc to standard.scc. All the commits in this pull requests are well contained, and should not affect other BSPs. Still the common kernel may get affected, and other BSPs using the common kernel need to validated these changes. Wei Sern, Have you done any validation with other BSPs using the same kernel? Nitin Please help to pull this patch into linux-yocto-3.10:meta branch. Thanks. Regards, Chan Wei Sern The following changes since commit 617c6158c3d5b931f0d6131e0b0a7b374c792599: mei.cfg: enable Intel chipsets (2014-05-05 09:46:42 -0400) are available in the git repository at: git://git.yoctoproject.org/linux-yocto-contrib wchan9/intel-common-meta http://git.yoctoproject.org/cgit.cgi/linux-yocto-contrib/log/?h=wchan9/intel-common-meta Chan Wei Sern (2): meta: haswell-wc: removed using of common-pc-64.scc meta: mohonpeak: removed using of common-pc-64.scc Sreeju Slevaraj (3): meta: crystalforest: removed using of common-pc-64.scc meta: crystalforest: included RTC configuration meta: crystalforest: included USB HID configuration .../cfg/kernel-cache/bsp/crystalforest/crystalforest-preempt-rt.scc |1 - meta/cfg/kernel-cache/bsp/crystalforest/crystalforest-standard.scc |3 +-- meta/cfg/kernel-cache/bsp/crystalforest/crystalforest.cfg |3 +++ meta/cfg/kernel-cache/bsp/crystalforest/crystalforest.scc |2 ++ meta/cfg/kernel-cache/bsp/haswell-wc/haswell-wc-preempt-rt.scc |2 +- meta/cfg/kernel-cache/bsp/haswell-wc/haswell-wc-standard.scc|2 +- meta/cfg/kernel-cache/bsp/mohonpeak/mohonpeak-preempt-rt.scc|1 - 7 files changed, 8 insertions(+), 6 deletions(-) -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH 0/5] Update meta branch for meta-ISGs platforms configuration
On 5/12/2014 9:05 AM, Kamble, Nitin A wrote: On 5/12/2014 3:20 PM, wei.sern.c...@intel.com wrote: From: Chan Wei Sern wei.sern.c...@intel.com Hi All, This is a patch series that consist of below: 1. Removed using of common-pc-64.scc from haswell-wc,crystalforest and mohonpeak. 2. Start using ktypes/standard/standard.scc for meta-ISG platforms. 3. Add back RTC configuration for crystalforest after changing from common-pc-64.scc to standard.scc. 4. Add back USB HID configuration for crystalforest after changing from common-pc-64.scc to standard.scc. All the commits in this pull requests are well contained, and should not affect other BSPs. Still the common kernel may get affected, and other BSPs using the common kernel need to validated these changes. Wei Sern, Have you done any validation with other BSPs using the same kernel? The somewhat disruption changes here are for v3.10 kernel for intel-corei7-64 BSP, and we do not have any 64 bit non-ISG BSP in meta-intel using the v3.10 kernel as default. so I am not much nervous about these changes to common kernel now. For all the commits from the pull request: Acked-By: Nitin A Kamble nitin.a.kam...@intel.com Chan, Can you mention the kernel repository version in the pull request next time? This time, it was not clear weather these commits were for v3.10 kernel repo or v3.14 kernel repo. Thanks, Nitin Nitin Please help to pull this patch into linux-yocto-3.10:meta branch. Thanks. Regards, Chan Wei Sern The following changes since commit 617c6158c3d5b931f0d6131e0b0a7b374c792599: mei.cfg: enable Intel chipsets (2014-05-05 09:46:42 -0400) are available in the git repository at: git://git.yoctoproject.org/linux-yocto-contrib wchan9/intel-common-meta http://git.yoctoproject.org/cgit.cgi/linux-yocto-contrib/log/?h=wchan9/intel-common-meta Chan Wei Sern (2): meta: haswell-wc: removed using of common-pc-64.scc meta: mohonpeak: removed using of common-pc-64.scc Sreeju Slevaraj (3): meta: crystalforest: removed using of common-pc-64.scc meta: crystalforest: included RTC configuration meta: crystalforest: included USB HID configuration .../cfg/kernel-cache/bsp/crystalforest/crystalforest-preempt-rt.scc |1 - meta/cfg/kernel-cache/bsp/crystalforest/crystalforest-standard.scc |3 +-- meta/cfg/kernel-cache/bsp/crystalforest/crystalforest.cfg |3 +++ meta/cfg/kernel-cache/bsp/crystalforest/crystalforest.scc |2 ++ meta/cfg/kernel-cache/bsp/haswell-wc/haswell-wc-preempt-rt.scc |2 +- meta/cfg/kernel-cache/bsp/haswell-wc/haswell-wc-standard.scc |2 +- meta/cfg/kernel-cache/bsp/mohonpeak/mohonpeak-preempt-rt.scc |1 - 7 files changed, 8 insertions(+), 6 deletions(-) -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH 0/5] Update meta branch for meta-ISGs platforms configuration
On 14-05-12 06:20 PM, wei.sern.c...@intel.com wrote: From: Chan Wei Sern wei.sern.c...@intel.com Hi All, This is a patch series that consist of below: 1. Removed using of common-pc-64.scc from haswell-wc,crystalforest and mohonpeak. 2. Start using ktypes/standard/standard.scc for meta-ISG platforms. 3. Add back RTC configuration for crystalforest after changing from common-pc-64.scc to standard.scc. 4. Add back USB HID configuration for crystalforest after changing from common-pc-64.scc to standard.scc. Please help to pull this patch into linux-yocto-3.10:meta branch. merged Bruce Thanks. Regards, Chan Wei Sern The following changes since commit 617c6158c3d5b931f0d6131e0b0a7b374c792599: mei.cfg: enable Intel chipsets (2014-05-05 09:46:42 -0400) are available in the git repository at: git://git.yoctoproject.org/linux-yocto-contrib wchan9/intel-common-meta http://git.yoctoproject.org/cgit.cgi/linux-yocto-contrib/log/?h=wchan9/intel-common-meta Chan Wei Sern (2): meta: haswell-wc: removed using of common-pc-64.scc meta: mohonpeak: removed using of common-pc-64.scc Sreeju Slevaraj (3): meta: crystalforest: removed using of common-pc-64.scc meta: crystalforest: included RTC configuration meta: crystalforest: included USB HID configuration .../cfg/kernel-cache/bsp/crystalforest/crystalforest-preempt-rt.scc |1 - meta/cfg/kernel-cache/bsp/crystalforest/crystalforest-standard.scc |3 +-- meta/cfg/kernel-cache/bsp/crystalforest/crystalforest.cfg |3 +++ meta/cfg/kernel-cache/bsp/crystalforest/crystalforest.scc |2 ++ meta/cfg/kernel-cache/bsp/haswell-wc/haswell-wc-preempt-rt.scc |2 +- meta/cfg/kernel-cache/bsp/haswell-wc/haswell-wc-standard.scc|2 +- meta/cfg/kernel-cache/bsp/mohonpeak/mohonpeak-preempt-rt.scc|1 - 7 files changed, 8 insertions(+), 6 deletions(-) -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 0/1] [3.14] meta: Update Baytrail SoC config fragment
Minnowboard Max makes use of the I2C and PWM devices and may use either ACPI or PCI enumeration. Make sure these are available in the SoC config fragment. The following changes since commit 4df1e2ed992adeac4da60ad5118d0237e8cb88df: meta: bump to v3.14.2 (2014-04-28 23:50:30 -0400) are available in the git repository at: git://git.yoctoproject.org/linux-yocto-3.14 dvhart/meta/baytrail http://git.yoctoproject.org/cgit.cgi/linux-yocto-3.14/log/?h=dvhart/meta/baytrail Darren Hart (1): baytrail: Add I2C PCI and LPSS_PWM support .../features/soc/baytrail/baytrail.cfg |2 ++ 1 file changed, 2 insertions(+) -- 1.7.9.5 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH 0/5] Update meta branch for meta-ISGs platforms configuration
Hi Nitin/Bruce, Thanks for helping that merge. In my cover letter I did mention it's targeting linux-yocto-3.10:meta branch. I will make that obvious next time thanks for pointing that out. For validation comment, yes those patches I submitted is tested against those platforms I mentioned. I will make this note on my next cover letter as well. Thanks Regards, Chan Wei Sern. -Original Message- From: Kamble, Nitin A Sent: Tuesday, May 13, 2014 1:01 AM To: Chan, Wei Sern; linux-yocto@yoctoproject.org; Ashfield, Bruce (Wind River) Subject: Re: [linux-yocto] [PATCH 0/5] Update meta branch for meta-ISGs platforms configuration On 5/12/2014 9:05 AM, Kamble, Nitin A wrote: On 5/12/2014 3:20 PM, wei.sern.c...@intel.com wrote: From: Chan Wei Sern wei.sern.c...@intel.com Hi All, This is a patch series that consist of below: 1. Removed using of common-pc-64.scc from haswell-wc,crystalforest and mohonpeak. 2. Start using ktypes/standard/standard.scc for meta-ISG platforms. 3. Add back RTC configuration for crystalforest after changing from common-pc-64.scc to standard.scc. 4. Add back USB HID configuration for crystalforest after changing from common-pc-64.scc to standard.scc. All the commits in this pull requests are well contained, and should not affect other BSPs. Still the common kernel may get affected, and other BSPs using the common kernel need to validated these changes. Wei Sern, Have you done any validation with other BSPs using the same kernel? The somewhat disruption changes here are for v3.10 kernel for intel-corei7-64 BSP, and we do not have any 64 bit non-ISG BSP in meta-intel using the v3.10 kernel as default. so I am not much nervous about these changes to common kernel now. For all the commits from the pull request: Acked-By: Nitin A Kamble nitin.a.kam...@intel.com Chan, Can you mention the kernel repository version in the pull request next time? This time, it was not clear weather these commits were for v3.10 kernel repo or v3.14 kernel repo. Thanks, Nitin Nitin Please help to pull this patch into linux-yocto-3.10:meta branch. Thanks. Regards, Chan Wei Sern The following changes since commit 617c6158c3d5b931f0d6131e0b0a7b374c792599: mei.cfg: enable Intel chipsets (2014-05-05 09:46:42 -0400) are available in the git repository at: git://git.yoctoproject.org/linux-yocto-contrib wchan9/intel-common-meta http://git.yoctoproject.org/cgit.cgi/linux-yocto-contrib/log/?h=wchan 9/intel-common-meta Chan Wei Sern (2): meta: haswell-wc: removed using of common-pc-64.scc meta: mohonpeak: removed using of common-pc-64.scc Sreeju Slevaraj (3): meta: crystalforest: removed using of common-pc-64.scc meta: crystalforest: included RTC configuration meta: crystalforest: included USB HID configuration .../cfg/kernel-cache/bsp/crystalforest/crystalforest-preempt-rt.scc |1 - meta/cfg/kernel-cache/bsp/crystalforest/crystalforest-standard.scc |3 +-- meta/cfg/kernel-cache/bsp/crystalforest/crystalforest.cfg |3 +++ meta/cfg/kernel-cache/bsp/crystalforest/crystalforest.scc |2 ++ meta/cfg/kernel-cache/bsp/haswell-wc/haswell-wc-preempt-rt.scc |2 +- meta/cfg/kernel-cache/bsp/haswell-wc/haswell-wc-standard.scc |2 +- meta/cfg/kernel-cache/bsp/mohonpeak/mohonpeak-preempt-rt.scc |1 - 7 files changed, 8 insertions(+), 6 deletions(-) -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
