[yocto] Migrating LDAT fs_final.sh to Yocto
Migrating from LDAT to Yocto, and wondering whether there is an equivalent to LDAT's fs_final.sh script? The objective is to do some post-processing on the rootfs tree before it is packaged into the UBIFS image. MV -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [linux-yocto] [PATCH 1/1] mei.cfg: enable Intel chipsets
On 14-05-02 08:01 PM, Kamble, Nitin A wrote: On 4/25/2014 8:51 AM, Hart, Darren wrote: On 4/24/14, 18:42, Kamble, Nitin A nitin.a.kam...@intel.com wrote: From: Nitin A Kamble nitin.a.kam...@intel.com Enable Intel Chipsets in the AMT/MEI driver. Signed-off-by: Nitin A Kamble nitin.a.kam...@intel.com Acked-by: Darren Hart dvh...@linux.intel.com Hi Bruce, Can you pull this fix in the v3.10 kernel repository as well? No problem. I'm doing some -stable updates and will put this on top of them. Cheers, Bruce Thanks, Nitin --- meta/cfg/kernel-cache/features/amt/mei/mei.cfg | 1 + 1 file changed, 1 insertion(+) diff --git a/meta/cfg/kernel-cache/features/amt/mei/mei.cfg b/meta/cfg/kernel-cache/features/amt/mei/mei.cfg index c1c2ace..313084b 100644 --- a/meta/cfg/kernel-cache/features/amt/mei/mei.cfg +++ b/meta/cfg/kernel-cache/features/amt/mei/mei.cfg @@ -1,3 +1,4 @@ CONFIG_STAGING=y CONFIG_WATCHDOG_CORE=y CONFIG_INTEL_MEI=y +CONFIG_INTEL_MEI_ME=y -- 1.8.1.4 -- ___ linux-yocto mailing list linux-yo...@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [yocto] [OE-core] DNS when using Static IP
Hello Tarek, On 02.05.2014 13:04, Tarek El-Sherbiny wrote: Hi. I'm trying to set my IP config to a static address. iface eth0 inet static address 192.168.55.45 network 192.168.55.0 netmask 255.255.255.0 broadcast 192.168.55.255 gateway 192.168.55.1 dns-nameservers 192.168.10.2 FWIW, in Debian-based systems, which is where ifupdown comes from, you need to install the resolvconf package in order to handle dns-nameservers entries. I don't know whether that's compatible with busybox' implementation of ifupdown, though. Regards, Andreas But I don't get the DNS server address to be included in /etc/resolv.conf If I run in dchp mode, then the resolv.conf is updated with my DNS address. Is there something I'm missing here in my setup? -- /Tarek/ -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] DL_DIR problems
Hello All, We’re trying to share a DL_DIR over NFS so all developers don’t have to re-download source files every time they want to do a clean build. Unfortunately we’re running into problems with lock files that are left behind by (sometimes) terminated processes. This will block users who are trying subsequent builds. How are others approaching this problem? Thanks, Seth -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Migrating LDAT fs_final.sh to Yocto
On Mon, May 5, 2014 at 6:34 AM, Vuille, Martin (Martin) vmar...@avaya.com wrote: Migrating from LDAT to Yocto, and wondering whether there is an equivalent to LDAT’s fs_final.sh script? Don't know what that is but you can use image post processing hooks in yocto to do tweaks to images. see IMAGE_POSTPROCESS_COMMAND The objective is to do some post-processing on the rootfs “tree” before it is packaged into the UBIFS image. MV -- ___ 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] Migrating LDAT fs_final.sh to Yocto
Exactly what I am looking for. Thanks! MV -Original Message- From: Khem Raj [mailto:raj.k...@gmail.com] Sent: May 05, 2014 12:34 PM To: Vuille, Martin (Martin) Cc: yocto@yoctoproject.org Subject: Re: [yocto] Migrating LDAT fs_final.sh to Yocto On Mon, May 5, 2014 at 6:34 AM, Vuille, Martin (Martin) vmar...@avaya.com wrote: Migrating from LDAT to Yocto, and wondering whether there is an equivalent to LDAT’s fs_final.sh script? Don't know what that is but you can use image post processing hooks in yocto to do tweaks to images. see IMAGE_POSTPROCESS_COMMAND The objective is to do some post-processing on the rootfs “tree” before it is packaged into the UBIFS image. MV -- ___ 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] [AB] PublishLayerTarballs git archives the wrong directory
On Fri, May 2, 2014 at 1:16 PM, Jate S jate...@gmail.com wrote: I am running off of the master branch. I hope this log message is readable. The key is to know that I have a meta-oe repo in the build directory and that the last line shows it's running in build instead of build/meta-oe. git archive --format=tar HEAD --prefix=meta-oe-40e0f371f3eb1628655c484feac0cebf810737b4/ | bzip2 -c meta-oe-40e0f371f3eb1628655c484feac0cebf810737b4.tar.bz2; md5sum meta-oe-40e0f371f3eb1628655c484feac0cebf810737b4.tar.bz2 meta-oe-40e0f371f3eb1628655c484feac0cebf810737b4.tar.bz2.md5sum; mkdir -p /home/jate/tmp/yab/publish/builds/qemux86/20140501-1; rsync -av meta-oe-40e0f371f3eb1628655c484feac0cebf810737b4.tar.bz2* /home/jate/tmp/yab/publish/builds/qemux86/20140501-1 in dir /home/jate/yocto-autobuilder/yocto-slave/qemux86/build (timeout 10 secs) I think that it should be changing directory to meta-oe, but the code is just missing that. This happens with all the other repourl's in my config too. The generated tarballs are of the same size (of poky). You are correct. Patch in the works. -b Cheers - Jate S. -- Elizabeth Flanagan Yocto Project Build and Release -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] DL_DIR problems
On Mon, May 5, 2014 at 4:40 AM, Bollinger, Seth seth.bollin...@digi.comwrote: We’re trying to share a DL_DIR over NFS so all developers don’t have to re-download source files every time they want to do a clean build. Unfortunately we’re running into problems with lock files that are left behind by (sometimes) terminated processes. This will block users who are trying subsequent builds. How are others approaching this problem? One option would be to maintain an internal downloads mirror, either populated by an autobuilder or by an rsync after engineer builds to the server hosting it. There'd be duplication in local disk space, but you'd avoid the NFS locking issues. -- Christopher Larson clarson at kergoth dot com Founder - BitBake, OpenEmbedded, OpenZaurus Maintainer - Tslib Senior Software Engineer, Mentor Graphics -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] DL_DIR problems
On Mon, May 5, 2014 at 10:41 AM, Christopher Larson clar...@kergoth.com wrote: On Mon, May 5, 2014 at 4:40 AM, Bollinger, Seth seth.bollin...@digi.com wrote: We’re trying to share a DL_DIR over NFS so all developers don’t have to re-download source files every time they want to do a clean build. Unfortunately we’re running into problems with lock files that are left behind by (sometimes) terminated processes. This will block users who are trying subsequent builds. How are others approaching this problem? One option would be to maintain an internal downloads mirror, either populated by an autobuilder or by an rsync after engineer builds to the server hosting it. There'd be duplication in local disk space, but you'd avoid the NFS locking issues. This is similar how the project infrastructure works. nfs:/dl_dir nfs:/rsynced_dl_dir autobuilder uses the nfs:/dl_dir and a period rsync syncs to rsync_dl_dir. We can then use the rsync dir as our mirror. It ends up solving a few issues. If you don't want to run a full autobuilder, just a bitbake universe -c fetch on a cron job with all your layers would do it. -b -- Christopher Larson clarson at kergoth dot com Founder - BitBake, OpenEmbedded, OpenZaurus Maintainer - Tslib Senior Software Engineer, Mentor Graphics -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto -- Elizabeth Flanagan Yocto Project Build and Release -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH 1/1] dylan: fix C++ standard library headers on OS X
Nice. I will resend, along with the one I just discovered for the meta-mingw
layer, which needs a similar fix for kconfig-frontends-native.
—
james woodyatt james.woody...@intel.com
Software Architect, New Devices Group
On May 2, 2014, at 12:09, Richard Purdie richard.pur...@linuxfoundation.org
wrote:
On Thu, 2014-05-01 at 23:02 +, Woodyatt, James wrote:
commit 562fa987cea60d61c256195adce7e83bf1c1a8c9
Author: james woodyatt james.woody...@intel.com
Date: Thu May 1 14:44:39 2014 -0700
Fix C++ standard library header directory configuration.
Remove the 4.2.1 directory from the --with-gxx-include-dir path provided
to the configure script for GCC 4.7 in the cross-canadian build.
diff --git a/recipes-devtools/gcc/gcc-cross-canadian_4.7.bbappend
b/recipes-devt
index 3fcc012..083b930 100644
--- a/recipes-devtools/gcc/gcc-cross-canadian_4.7.bbappend
+++ b/recipes-devtools/gcc/gcc-cross-canadian_4.7.bbappend
@@ -4,7 +4,7 @@ INSANE_SKIP_${PN}_append_darwinsdk = staticdev
LDFLAGS_darwinsdk = ${BUILDSDK_LDFLAGS} -L${libdir}/..
# Change gxx-include-dir
-EXTRA_OECONF_PATHS_darwinsdk =
--with-gxx-include-dir=${SDKPATH}/sysroots/${TU
+EXTRA_OECONF_PATHS_darwinsdk =
--with-gxx-include-dir=${SDKPATH}/sysroots/${TU
--with-build-time-tools=${STAGING_DIR_NATIVE}${prefix_nat
--with-sysroot=${SDKPATH}/sysroots/${TUNE_PKGARCH}${TARGE
--with-build-sysroot=${STAGING_DIR_TARGET}
This patch is truncated at the linewrap unfortunately :(
Cheers,
Richard
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH 1/1] dylan: fix kconfig-frontends for ncurses --with-libterm
commit 939c9feca3c26d4603b573d887324d6220e93819
Author: james woodyatt james.woody...@intel.com
Date: Mon May 5 15:54:29 2014 -0700
kconfig-frontends-native: add support for --with-libterm.
This is a cherry-pick of cefcd4b655c2b7efdc6313740f3c8af89dd8f670 from
the kconfig-frontends project authoritative Git repository for a change
that went into 3.9 and later revisions that enables building on hosts
configurations where libncurses uses libtinfo.
diff --git a/oecore.patch b/oecore.patch
index 7371244..ec2fc8b 100644
--- a/oecore.patch
+++ b/oecore.patch
@@ -3272,3 +3272,38 @@ index 43a55a6..5553411 100644
SRC_URI[md5sum] = 3e379b4d8b9693948d751c154614c73e
+diff --git
a/meta/recipes-devtools/kconfig-frontends/files/kconfig-frontends-tinfo.patch
b/meta/recipes-devtools/kconfig-frontends/files/kconfig-frontends-tinfo.patch
+new file mode 100644
+index 000..1da643a
+--- /dev/null
b/meta/recipes-devtools/kconfig-frontends/files/kconfig-frontends-tinfo.patch
+@@ -0,0 +1,14 @@
++diff --git a/configure.ac b/configure.ac
++index 8b5bc5d..e90fd17 100644
++--- a/configure.ac
+ b/configure.ac
++@@ -283,6 +283,10 @@ AS_IF(
++ [test $need_curses = yes],
++ [AC_MSG_ERROR([could not find curses library (frontends:
mconf/nconf)])],
++ [has_curses=no])])
+++ AC_SEARCH_LIBS(
+++[setupterm],
+++[tinfo],
+++[break])
++ ncurses_LIBS=$LIBS
++ LIBS=$LIBS_old])
+diff --git
a/meta/recipes-devtools/kconfig-frontends/kconfig-frontends_3.8.0.bb
b/meta/recipes-devtools/kconfig-frontends/kconfig-frontends_3.8.0.bb
+index b9960f9..a1e7572 100644
+--- a/meta/recipes-devtools/kconfig-frontends/kconfig-frontends_3.8.0.bb
b/meta/recipes-devtools/kconfig-frontends/kconfig-frontends_3.8.0.bb
+@@ -13,7 +13,9 @@ SECTION = devel
+ DEPENDS += ncurses flex bison gperf pkgconfig-native
+ PR = r0
+ SPIN = .0
+-SRC_URI =
http://ymorin.is-a-geek.org/download/${BPN}/${BPN}-${PV}${SPIN}.tar.xz;
++SRC_URI =
http://ymorin.is-a-geek.org/download/${BPN}/${BPN}-${PV}${SPIN}.tar.xz \
++ file://kconfig-frontends-tinfo.patch \
++
+
+ SRC_URI[md5sum] = 73598aea99d01d9c422b335e9b963271
+ SRC_URI[sha256sum] =
b3ff325338aa291c9129dbf33c69ff321e30105aa06ff957be6f958acdc72b42
—
james woodyatt james.woody...@intel.com
Software Architect, New Devices Group
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH 0/1] dylan: fix kconfig-frontends for ncurses --with-libterm
Everyone— Another change required for building the meta-toolchain target (this time for MingW) on host configurations where ncurses is configured with —with-libterm. I cherry-picked this change to kconfig-frontends from its authoritative repository [change cefcd4b6] and added it to the oecore.patch file for the dylan branch on the meta-mingw layer. This change should not be required with kconfig-frontends-3.9 or later. — james woodyatt james.woody...@intel.com Software Architect, New Devices Group -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH 1/1] dylan: fix C++ standard library headers on OS X
Resend, this time with all contents.
commit 562fa987cea60d61c256195adce7e83bf1c1a8c9
Author: james woodyatt james.woody...@intel.com
Date: Thu May 1 14:44:39 2014 -0700
Fix C++ standard library header directory configuration.
Remove the 4.2.1 directory from the --with-gxx-include-dir path provided
to the configure script for GCC 4.7 in the cross-canadian build.
diff --git a/recipes-devtools/gcc/gcc-cross-canadian_4.7.bbappend
b/recipes-devtools/gcc/gcc-cross-canadian_4.7.bbappend
index 3fcc012..083b930 100644
--- a/recipes-devtools/gcc/gcc-cross-canadian_4.7.bbappend
+++ b/recipes-devtools/gcc/gcc-cross-canadian_4.7.bbappend
@@ -4,7 +4,7 @@ INSANE_SKIP_${PN}_append_darwinsdk = staticdev
LDFLAGS_darwinsdk = ${BUILDSDK_LDFLAGS} -L${libdir}/..
# Change gxx-include-dir
-EXTRA_OECONF_PATHS_darwinsdk =
--with-gxx-include-dir=${SDKPATH}/sysroots/${TUNE_PKGARCH}${TARGET_VENDOR}-${TARGET_OS}/usr/include/c++/4.2.1
\
+EXTRA_OECONF_PATHS_darwinsdk =
--with-gxx-include-dir=${SDKPATH}/sysroots/${TUNE_PKGARCH}${TARGET_VENDOR}-${TARGET_OS}/usr/include/c++
\
--with-build-time-tools=${STAGING_DIR_NATIVE}${prefix_native}/${TARGET_SYS}/bin
\
--with-sysroot=${SDKPATH}/sysroots/${TUNE_PKGARCH}${TARGET_VENDOR}-${TARGET_OS}
\
--with-build-sysroot=${STAGING_DIR_TARGET}
—
james woodyatt james.woody...@intel.com
Software Architect, New Devices Group
On May 1, 2014, at 16:02, Woodyatt, James james.woody...@intel.com wrote:
commit 562fa987cea60d61c256195adce7e83bf1c1a8c9
Author: james woodyatt james.woody...@intel.com
Date: Thu May 1 14:44:39 2014 -0700
Fix C++ standard library header directory configuration.
Remove the 4.2.1 directory from the --with-gxx-include-dir path provided
to the configure script for GCC 4.7 in the cross-canadian build.
diff --git a/recipes-devtools/gcc/gcc-cross-canadian_4.7.bbappend
b/recipes-devt
index 3fcc012..083b930 100644
--- a/recipes-devtools/gcc/gcc-cross-canadian_4.7.bbappend
+++ b/recipes-devtools/gcc/gcc-cross-canadian_4.7.bbappend
@@ -4,7 +4,7 @@ INSANE_SKIP_${PN}_append_darwinsdk = staticdev
LDFLAGS_darwinsdk = ${BUILDSDK_LDFLAGS} -L${libdir}/..
# Change gxx-include-dir
-EXTRA_OECONF_PATHS_darwinsdk =
--with-gxx-include-dir=${SDKPATH}/sysroots/${TU
+EXTRA_OECONF_PATHS_darwinsdk =
--with-gxx-include-dir=${SDKPATH}/sysroots/${TU
--with-build-time-tools=${STAGING_DIR_NATIVE}${prefix_nat
--with-sysroot=${SDKPATH}/sysroots/${TUNE_PKGARCH}${TARGE
--with-build-sysroot=${STAGING_DIR_TARGET}
—
james woodyatt james.woody...@intel.com
Software Architect, New Devices Group
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Definition of Yocto tasks
Is there a document that provides a detailed definition of what each these tasks do? Yocto, OE, and bitbake manuals tell us how to command a specific task to be run, but not what they do. The task name provides a good hint sometimes, but often that is not enough. Users shouldn't have to read the python code for this information. These descriptions should be a part of the yocto manual. Sections 5.3.4 to 5.3.11 of the Yocto mega-manual provide a good overview of some of these tasks in the context of a workflow, but doesn't mention most of these tasks and doesn't go into enough detail on the tasks it discusses. It wouldn't be appropriate to add more detail at that point in the manual, but it would be appropriate to include details regarding all of the tasks in an appendix. Examples... The manual states that do_fetch fetches source, but doesn't state that when git is used whether it performs a pull, fetch, or clone. What are the common failure conditions of do_fetch? And what should the user do to fix the problem? do_build is mentioned a few times, but there is no reference to it being the default task or what tasks are invoked by do_build and which are omitted. do_rm_work and do_wm_work_all are not mentioned at all. Result of listtasks: do_fetchall do_build do_devshell do_package_write_ipk do_cleansstate do_savedefconfig do_uboot_mkimage do_sizecheck do_strip do_packagedata_setscene do_configure do_clean do_deploy_setscene do_cleanall do_populate_lic do_populate_sysroot do_devicetree_image do_deploy do_menuconfig do_patch do_bundle_initramfs do_packagedata do_listtasks do_compile do_package_setscene do_populate_lic_setscene do_fetch do_checkuri do_compile_kernelmodules do_package_write_ipk_setscene do_package_write do_rm_work do_package do_unpack do_install do_checkuriall do_populate_sysroot_setscene do_rm_work_all I don't have the knowledge to create such an appendix, but I volunteer to be a proofreader. Regards, Bob -- ___ 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: Beth - Paul 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: [linux-yocto] How to include iw utility to yocto build for ARM
On 14-05-05 11:22 AM, Sathish Kumar Balasubramaniam -ERS, HCL Tech wrote: Please can someone let me know how to include the iw utility (http://wireless.kernel.org/en/users/Documentation/iw) to Yocto based on Linux kernel 3.4 using the Yocto build process for ARM It's not directly related to the kernel, but there's a layer which contains the utility: http://layers.openembedded.org/layerindex/recipe/25628/ You'd need to include that layer, and add the package to your rootfs. Bruce Regards, B.Sathish Kumar ::DISCLAIMER:: The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] How to include iw utility to yocto build for ARM
Thanks, Bruce. Yes I should have posted this in the general yocto mailing list... -Original Message- From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com] Sent: Monday, May 05, 2014 9:11 PM To: Sathish Kumar Balasubramaniam -ERS, HCL Tech; linux-yocto@yoctoproject.org Subject: Re: [linux-yocto] How to include iw utility to yocto build for ARM On 14-05-05 11:22 AM, Sathish Kumar Balasubramaniam -ERS, HCL Tech wrote: Please can someone let me know how to include the iw utility (http://wireless.kernel.org/en/users/Documentation/iw) to Yocto based on Linux kernel 3.4 using the Yocto build process for ARM It's not directly related to the kernel, but there's a layer which contains the utility: http://layers.openembedded.org/layerindex/recipe/25628/ You'd need to include that layer, and add the package to your rootfs. Bruce Regards, B.Sathish Kumar ::DISCLAIMER:: -- -- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. -- -- -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH 1/1] mei.cfg: enable Intel chipsets
-Original Message- From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com] Sent: Monday, May 05, 2014 6:38 AM To: Kamble, Nitin A; Hart, Darren; linux-yocto@yoctoproject.org Subject: Re: [PATCH 1/1] mei.cfg: enable Intel chipsets On 14-05-02 08:01 PM, Kamble, Nitin A wrote: On 4/25/2014 8:51 AM, Hart, Darren wrote: On 4/24/14, 18:42, Kamble, Nitin A nitin.a.kam...@intel.com wrote: From: Nitin A Kamble nitin.a.kam...@intel.com Enable Intel Chipsets in the AMT/MEI driver. Signed-off-by: Nitin A Kamble nitin.a.kam...@intel.com Acked-by: Darren Hart dvh...@linux.intel.com Hi Bruce, Can you pull this fix in the v3.10 kernel repository as well? No problem. I'm doing some -stable updates and will put this on top of them. Thanks Bruce, Let me know when you pull the commit in, I will be firing a build with that. Nitin Cheers, Bruce Thanks, Nitin --- meta/cfg/kernel-cache/features/amt/mei/mei.cfg | 1 + 1 file changed, 1 insertion(+) diff --git a/meta/cfg/kernel-cache/features/amt/mei/mei.cfg b/meta/cfg/kernel-cache/features/amt/mei/mei.cfg index c1c2ace..313084b 100644 --- a/meta/cfg/kernel-cache/features/amt/mei/mei.cfg +++ b/meta/cfg/kernel-cache/features/amt/mei/mei.cfg @@ -1,3 +1,4 @@ CONFIG_STAGING=y CONFIG_WATCHDOG_CORE=y CONFIG_INTEL_MEI=y +CONFIG_INTEL_MEI_ME=y -- 1.8.1.4 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
