[yocto] [PATCH] gstreamer-vaapi: add missing build dependencies
[YOCTO #3321] Signed-off-by: Ross Burton ross.bur...@intel.com --- common/recipes-multimedia/gstreamer/gstreamer-vaapi_git.bb |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/common/recipes-multimedia/gstreamer/gstreamer-vaapi_git.bb b/common/recipes-multimedia/gstreamer/gstreamer-vaapi_git.bb index 27552a2..74fa29a 100644 --- a/common/recipes-multimedia/gstreamer/gstreamer-vaapi_git.bb +++ b/common/recipes-multimedia/gstreamer/gstreamer-vaapi_git.bb @@ -6,7 +6,7 @@ based plugins for GStreamer and helper libraries: `vaapidecode', \ LICENSE = LGPLv2.1+ LIC_FILES_CHKSUM = file://COPYING.LIB;md5=4fbd65380cdd255951079008b364516c -DEPENDS = gstreamer libva +DEPENDS = gstreamer gst-plugins-base gst-plugins-bad libva # 0.3.8 tag SRCREV = 6ec4c2252a4aa706cd8631cb1083828485b9df9a -- 1.7.10 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH] gstreamer-vaapi: add missing build dependencies
On Tue, 2012-10-23 at 10:43 +0100, Ross Burton wrote: [YOCTO #3321] Fixed the problem for me here (sugarbay), thanks. Pulled into meta-intel/master. Tom Signed-off-by: Ross Burton ross.bur...@intel.com --- common/recipes-multimedia/gstreamer/gstreamer-vaapi_git.bb |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/common/recipes-multimedia/gstreamer/gstreamer-vaapi_git.bb b/common/recipes-multimedia/gstreamer/gstreamer-vaapi_git.bb index 27552a2..74fa29a 100644 --- a/common/recipes-multimedia/gstreamer/gstreamer-vaapi_git.bb +++ b/common/recipes-multimedia/gstreamer/gstreamer-vaapi_git.bb @@ -6,7 +6,7 @@ based plugins for GStreamer and helper libraries: `vaapidecode', \ LICENSE = LGPLv2.1+ LIC_FILES_CHKSUM = file://COPYING.LIB;md5=4fbd65380cdd255951079008b364516c -DEPENDS = gstreamer libva +DEPENDS = gstreamer gst-plugins-base gst-plugins-bad libva # 0.3.8 tag SRCREV = 6ec4c2252a4aa706cd8631cb1083828485b9df9a ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] ERROR: Function failed: do_rootfs, poky commit id 8ce23f569584f195391bc5c68a780e1bf54e4360
Hi, I haven't had any solutions for this build error that I'm facing. If someone could offer some insight as to what might be going wrong, it would be much appreciated. On Oct 23, 2012, at 12:22 AM, Elvis Dowson elvis.dow...@gmail.com wrote: | Configuring sysvinit. | Collected errors: | * preinst_configure: Aborting installation of base-passwd. | * opkg_install_cmd: Cannot install package packagegroup-core-boot. | ERROR: Function failed: do_rootfs (see /tool/yocto/poky/build/tmp/work/zynq_zc702-poky-linux-gnueabi/core-image-minimal-1.0-r0/temp/log.do_rootfs.30138 for further information) ERROR: Task 7 (/tool/yocto/poky/meta/recipes-core/images/core-image-minimal.bb, do_rootfs) failed with exit code '1' NOTE: Tasks Summary: Attempted 1395 tasks of which 227 didn't need to be rerun and 1 failed. No currently running tasks (1395 of 1396) The build appears to be failing because it cannot install packagegroup-core-boot. Has something changed recently in poky/master, that might be causing this? I additionally notice that the path being generated is zynq_702 instead of zynq-702. No-where in Philip Ballister's machine configs for the zc702 board, is is mentioned zynq_zc702 with an underscore, yet it adds it. It's kind of weird. ERROR: Function failed: do_rootfs (see /tool/yocto/poky/build/tmp/work/zynq_zc702-poky-linux-gnueabi/core-image-minimal-1.0-r0/temp/log.do_rootfs.30138 for further information) It's kind of weird. I also see the same zynq_zc702 entry with an underscore in the logs as follows: | + ipkgarchs='all any noarch arm armv4 armv5 armv5-vfp armv5e armv5e-vfp armv6-vfp armv7a armv7a-vfp armv7a-vfp-neon zynq_zc702' What could be causing this? Best regards, Elvis Dowson___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] ERROR: Function failed: do_rootfs, poky commit id 8ce23f569584f195391bc5c68a780e1bf54e4360
On Tue, Oct 23, 2012 at 08:32:02PM +0400, Elvis Dowson wrote: Hi, I haven't had any solutions for this build error that I'm facing. If someone could offer some insight as to what might be going wrong, it would be much appreciated. On Oct 23, 2012, at 12:22 AM, Elvis Dowson elvis.dow...@gmail.com wrote: | Configuring sysvinit. | Collected errors: | * preinst_configure: Aborting installation of base-passwd. | * opkg_install_cmd: Cannot install package packagegroup-core-boot. | ERROR: Function failed: do_rootfs (see /tool/yocto/poky/build/tmp/work/zynq_zc702-poky-linux-gnueabi/core-image-minimal-1.0-r0/temp/log.do_rootfs.30138 for further information) ERROR: Task 7 (/tool/yocto/poky/meta/recipes-core/images/core-image-minimal.bb, do_rootfs) failed with exit code '1' NOTE: Tasks Summary: Attempted 1395 tasks of which 227 didn't need to be rerun and 1 failed. No currently running tasks (1395 of 1396) The build appears to be failing because it cannot install packagegroup-core-boot. Has something changed recently in poky/master, that might be causing this? I additionally notice that the path being generated is zynq_702 instead of zynq-702. MACHINE_ARCH replaces - with _ in machine name. see https://bugzilla.yoctoproject.org/show_bug.cgi?id=946 Cheers, No-where in Philip Ballister's machine configs for the zc702 board, is is mentioned zynq_zc702 with an underscore, yet it adds it. It's kind of weird. ERROR: Function failed: do_rootfs (see /tool/yocto/poky/build/tmp/work/zynq_zc702-poky-linux-gnueabi/core-image-minimal-1.0-r0/temp/log.do_rootfs.30138 for further information) It's kind of weird. I also see the same zynq_zc702 entry with an underscore in the logs as follows: | + ipkgarchs='all any noarch arm armv4 armv5 armv5-vfp armv5e armv5e-vfp armv6-vfp armv7a armv7a-vfp armv7a-vfp-neon zynq_zc702' What could be causing this? Best regards, Elvis Dowson ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto -- Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com signature.asc Description: Digital signature ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] build failures after pull
I've reported this before, but it still happens. Today, I did a git pull into my local while master was checked out, both on poky and meta-intel. I then tried to rerun without cleaning or deleting anything for chiefriver. My last build had been successfully built, but didn't have audio. So when I saw patches, I thought I'd test again. I simply did source oe-init-build-env bitbake core-image-sato I got a failure in diffutils for some reason. I then did bitbake -c cleansstate diffutils bitbake core-image-sato. This time it worked. Jim A ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] ERROR: Function failed: do_rootfs, poky commit id 8ce23f569584f195391bc5c68a780e1bf54e4360
Hi, On Oct 23, 2012, at 8:32 PM, Elvis Dowson elvis.dow...@gmail.com wrote: I haven't had any solutions for this build error that I'm facing. If someone could offer some insight as to what might be going wrong, it would be much appreciated. On Oct 23, 2012, at 12:22 AM, Elvis Dowson elvis.dow...@gmail.com wrote: | Configuring sysvinit. | Collected errors: | * preinst_configure: Aborting installation of base-passwd. | * opkg_install_cmd: Cannot install package packagegroup-core-boot. | ERROR: Function failed: do_rootfs (see /tool/yocto/poky/build/tmp/work/zynq_zc702-poky-linux-gnueabi/core-image-minimal-1.0-r0/temp/log.do_rootfs.30138 for further information) ERROR: Task 7 (/tool/yocto/poky/meta/recipes-core/images/core-image-minimal.bb, do_rootfs) failed with exit code '1' NOTE: Tasks Summary: Attempted 1395 tasks of which 227 didn't need to be rerun and 1 failed. No currently running tasks (1395 of 1396) The build appears to be failing because it cannot install packagegroup-core-boot. Has something changed recently in poky/master, that might be causing this? I additionally notice that the path being generated is zynq_702 instead of zynq-702. No-where in Philip Ballister's machine configs for the zc702 board, is is mentioned zynq_zc702 with an underscore, yet it adds it. It's kind of weird. ERROR: Function failed: do_rootfs (see /tool/yocto/poky/build/tmp/work/zynq_zc702-poky-linux-gnueabi/core-image-minimal-1.0-r0/temp/log.do_rootfs.30138 for further information) It's kind of weird. I also see the same zynq_zc702 entry with an underscore in the logs as follows: | + ipkgarchs='all any noarch arm armv4 armv5 armv5-vfp armv5e armv5e-vfp armv6-vfp armv7a armv7a-vfp armv7a-vfp-neon zynq_zc702' What could be causing this? I found out why it was failing. I recently added two SSD drives in a RAID0 stripped disk configuration. One of the performance tweaks was to move /tmp to RAM, to improve the life of the SSDs. My /etc/fstab for setting up the /tmp folder inadvertently included the noexec,nodev,nosuid options, which cause the rootfs process to fail. the following entry works for the /etc/fstab for moving the /tmp file to RAM none/tmptmpfsdefaults,noatime,nodiratime00 I just updated poky and the rest of the meta-layers to the latest commit on their respective master branches, and it built successfully. Best regards, Elvis Dowson ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Unreadable menuconfig
When I run 'bitbake linux-yocto -c menuconfig' I was not getting a menuconfig - I had to tell my local.conf to use screen because auto was selecting a gnome terminal which would resize itself to something too small and menuconfig would exit with an error. Now I can get menuconfig and make changes, but it is extremely difficult to read. I have attached a screenshot of what I am talking about. Can anyone point me in the right direction on how to fix this? I would like to use the correct commands so that I don't mess anything up. Right now I have resorted to running menuconfig down in my build directory where the .config file is stored with the kernel source. Thoughts? Thanks! Jonathan ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Unreadable menuconfig
Jonathan Haws jonathan.h...@sdl.usu.edu writes: When I run 'bitbake linux-yocto -c menuconfig' I was not getting a menuconfig - I had to tell my local.conf to use screen because auto was selecting a gnome terminal which would resize itself to something too small and menuconfig would exit with an error. Now I can get menuconfig and make changes, but it is extremely difficult to read. I have attached a screenshot of what I am talking about. Can anyone point me in the right direction on how to fix this? I would like to use the correct commands so that I don't mess anything up. Right now I have resorted to running menuconfig down in my build directory where the .config file is stored with the kernel source. Thoughts? Try: OE_TERMINAL = xterm in your local.conf Marc ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Unreadable menuconfig
Thanks for the help. I used the solution from the following thread to take care of it: http://lists.linuxtogo.org/pipermail/openembedded-core/2012-August/027130.html Are there others having this issue? If so, is it something that should be pushed upstream? Thanks! ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] ERROR: Function failed: do_rootfs, poky commit id 8ce23f569584f195391bc5c68a780e1bf54e4360
On Tue, Oct 23, 2012 at 10:35:49PM +0400, Elvis Dowson wrote: Hi, On Oct 23, 2012, at 8:32 PM, Elvis Dowson elvis.dow...@gmail.com wrote: I haven't had any solutions for this build error that I'm facing. If someone could offer some insight as to what might be going wrong, it would be much appreciated. On Oct 23, 2012, at 12:22 AM, Elvis Dowson elvis.dow...@gmail.com wrote: | Configuring sysvinit. | Collected errors: | * preinst_configure: Aborting installation of base-passwd. | * opkg_install_cmd: Cannot install package packagegroup-core-boot. | ERROR: Function failed: do_rootfs (see /tool/yocto/poky/build/tmp/work/zynq_zc702-poky-linux-gnueabi/core-image-minimal-1.0-r0/temp/log.do_rootfs.30138 for further information) ERROR: Task 7 (/tool/yocto/poky/meta/recipes-core/images/core-image-minimal.bb, do_rootfs) failed with exit code '1' NOTE: Tasks Summary: Attempted 1395 tasks of which 227 didn't need to be rerun and 1 failed. No currently running tasks (1395 of 1396) The build appears to be failing because it cannot install packagegroup-core-boot. Has something changed recently in poky/master, that might be causing this? I additionally notice that the path being generated is zynq_702 instead of zynq-702. No-where in Philip Ballister's machine configs for the zc702 board, is is mentioned zynq_zc702 with an underscore, yet it adds it. It's kind of weird. ERROR: Function failed: do_rootfs (see /tool/yocto/poky/build/tmp/work/zynq_zc702-poky-linux-gnueabi/core-image-minimal-1.0-r0/temp/log.do_rootfs.30138 for further information) It's kind of weird. I also see the same zynq_zc702 entry with an underscore in the logs as follows: | + ipkgarchs='all any noarch arm armv4 armv5 armv5-vfp armv5e armv5e-vfp armv6-vfp armv7a armv7a-vfp armv7a-vfp-neon zynq_zc702' What could be causing this? I found out why it was failing. I recently added two SSD drives in a RAID0 stripped disk configuration. One of the performance tweaks was to move /tmp to RAM, to improve the life of the SSDs. My /etc/fstab for setting up the /tmp folder inadvertently included the noexec,nodev,nosuid options, which cause the rootfs process to fail. You can keep nodev and nosuid. I'm using this for long time without issues. But keep in mind that you have to keep parts of tmpdir (even after reboot) to keep sstate happy: https://bugzilla.yoctoproject.org/show_bug.cgi?id=3221 the following entry works for the /etc/fstab for moving the /tmp file to RAM none/tmptmpfsdefaults,noatime,nodiratime00 I just updated poky and the rest of the meta-layers to the latest commit on their respective master branches, and it built successfully. Best regards, Elvis Dowson ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto -- Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com signature.asc Description: Digital signature ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Unreadable menuconfig
On Tue, Oct 23, 2012 at 07:54:58PM +, Jonathan Haws wrote: Thanks for the help. I used the solution from the following thread to take care of it: http://lists.linuxtogo.org/pipermail/openembedded-core/2012-August/027130.html Are there others having this issue? If so, is it something that should be pushed upstream? It's still valid for me, I'm still using this https://github.com/shr-distribution/oe-core/commit/5d5e8783c0db7e2f0488eea02f795c9f543cd626 Cheers, -- Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com signature.asc Description: Digital signature ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Unreadable menuconfig
It's still valid for me, I'm still using this https://github.com/shr-distribution/oe-core/commit/5d5e8783c0db7e2f0488eea02f795c9f543cd626 H. I did a fresh download of the Yocto repos last week and that is not what I have. My file still has the HOSTLDFLAGS variable set. ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Unreadable menuconfig
On Tue, Oct 23, 2012 at 08:08:29PM +, Jonathan Haws wrote: It's still valid for me, I'm still using this https://github.com/shr-distribution/oe-core/commit/5d5e8783c0db7e2f0488eea02f795c9f543cd626 H. I did a fresh download of the Yocto repos last week and that is not what I have. My file still has the HOSTLDFLAGS variable set. this isn't in upstream oe-core repo, but in shr branch for shr-distribution. -- Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com signature.asc Description: Digital signature ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH 1/6] MAINTAINERS: corect pathname
From: Nitin A Kamble nitin.a.kam...@intel.com The commmon directory has more stuff than just recipes-core. All this need to be maintained together as part of the meta-intel layer. Signed-off-by: Nitin A Kamble nitin.a.kam...@intel.com --- MAINTAINERS |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/MAINTAINERS b/MAINTAINERS index d63ed31..eac592b 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -42,7 +42,7 @@ F:meta-chiefriver/ COMMON M: Nitin A Kamblenitin.a.kam...@intel.com -F: common/recipes-core/ +F: common/ CROWNBAY M: Nitin A Kamblenitin.a.kam...@intel.com -- 1.7.3.4 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH 2/6] chiefriver README: add WebTitle Compliance information
From: Nitin A Kamble nitin.a.kam...@intel.com The WebTitle will be used to publish the BSP on the Yocto Project Website. And adding the Yocto Project Compliance information for the 1.3 release. Also specifying all the layers used from meta-intel repository. Signed-off-by: Nitin A Kamble nitin.a.kam...@intel.com --- meta-chiefriver/README | 10 +- 1 files changed, 9 insertions(+), 1 deletions(-) diff --git a/meta-chiefriver/README b/meta-chiefriver/README index 7c47b02..7af1288 100644 --- a/meta-chiefriver/README +++ b/meta-chiefriver/README @@ -6,6 +6,14 @@ The 'Chief River' platform consists of the Intel Ivy Bridge processor, plus the Panther Point PCH. This BSP assumes that the Ivy Bridge integrated graphics are being used. +WebTitle: Intel 3nd Generations Core Platforms: Core i3, i5, i7 (Ivy Bridge) + + +Compliance: + +This BSP is compliant with Yocto Project as per requirements listed here: +http://www.yoctoproject.org/yocto-project-compatible-registration + Dependencies @@ -20,7 +28,7 @@ This layer depends on: branch: master URI: git://git.yoctoproject.org/meta-intel - layers: intel + layers: meta-intel, meta-chiefriver branch: master -- 1.7.3.4 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH 4/6] emenlow README: add WebTitle Compliance information
From: Nitin A Kamble nitin.a.kam...@intel.com The WebTitle will be used to publish the BSP on the Yocto Project Website. And adding the Yocto Project Compliance information for the 1.3 release. Also specifying all the layers used from meta-intel repository. Signed-off-by: Nitin A Kamble nitin.a.kam...@intel.com --- meta-emenlow/README | 11 ++- 1 files changed, 10 insertions(+), 1 deletions(-) diff --git a/meta-emenlow/README b/meta-emenlow/README index 3932718..91381d3 100644 --- a/meta-emenlow/README +++ b/meta-emenlow/README @@ -13,6 +13,15 @@ depending on which BSP tarball you downloaded. Please see the corresponding sections below for details. +WebTitle: Platforms with Intel Atom Z5xx processor with Intel US15W Controller Hub (emenlow) + + +Compliance: + +This BSP is compliant with Yocto Project as per requirements listed here: +http://www.yoctoproject.org/yocto-project-compatible-registration + + Dependencies @@ -26,7 +35,7 @@ This layer depends on: branch: master URI: git://git.yoctoproject.org/meta-intel - layers: intel + layers: meta-intel, meta-emenlow branch: master -- 1.7.3.4 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH 5/6] jasperforest README: add WebTitle Compliance information
From: Nitin A Kamble nitin.a.kam...@intel.com The WebTitle will be used to publish the BSP on the Yocto Project Website. And adding the Yocto Project Compliance information for the 1.3 release. Also specifying all the layers used from meta-intel repository. Signed-off-by: Nitin A Kamble nitin.a.kam...@intel.com --- meta-jasperforest/README | 11 ++- 1 files changed, 10 insertions(+), 1 deletions(-) diff --git a/meta-jasperforest/README b/meta-jasperforest/README index 12f84c2..98a4d57 100644 --- a/meta-jasperforest/README +++ b/meta-jasperforest/README @@ -8,6 +8,15 @@ combined with the Intel 3420 PCH chipset (Ibex Peak) make up the 'Picket Post' CRB this BSP was developed on. +WebTitle: Platforms with Intel Xeon C5500/C3500 processors with Intel 3420 PCH chipset (jasperforest) + + +Compliance: + +This BSP is compliant with Yocto Project as per requirements listed here: +http://www.yoctoproject.org/yocto-project-compatible-registration + + Dependencies @@ -21,7 +30,7 @@ This layer depends on: branch: master URI: git://git.yoctoproject.org/meta-intel - layers: intel + layers: meta-intel, meta-jasperforest branch: master -- 1.7.3.4 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH 6/6] sugarbay README: add WebTitle Compliance information
From: Nitin A Kamble nitin.a.kam...@intel.com The WebTitle will be used to publish the BSP on the Yocto Project Website. And adding the Yocto Project Compliance information for the 1.3 release. Also specifying all the layers used from meta-intel repository. Signed-off-by: Nitin A Kamble nitin.a.kam...@intel.com --- meta-sugarbay/README |9 - 1 files changed, 8 insertions(+), 1 deletions(-) diff --git a/meta-sugarbay/README b/meta-sugarbay/README index c8a99d7..36da170 100644 --- a/meta-sugarbay/README +++ b/meta-sugarbay/README @@ -6,6 +6,13 @@ The 'Sugar Bay' platform consists of the Intel Sandy Bridge processor, plus the Cougar Point PCH (Q67 Express or B65 Express chipsets). This BSP assumes that the Sandy Bridge integrated graphics are being used. +WebTitle: Intel 2nd Generations Core Platforms: Core i3, i5, i7 (Sandy Bridge) + +Compliance: + +This BSP is compliant with Yocto Project as per requirements listed here: +http://www.yoctoproject.org/yocto-project-compatible-registration + Dependencies @@ -20,7 +27,7 @@ This layer depends on: branch: master URI: git://git.yoctoproject.org/meta-intel - layers: intel + layers: meta-intel, meta-sugarbay branch: master -- 1.7.3.4 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH 0/6] meta-intel: README updates
From: Nitin A Kamble nitin.a.kam...@intel.com For the YP 1.3 release, README changes for the BSPs I am maintaining. Thanks, Nitin The following changes since commit f502e7493694c487767f60df232055bc7b854e69: gstreamer-vaapi: add missing build dependencies (2012-10-23 07:43:46 -0500) are available in the git repository at: git://git.yoctoproject.org/meta-intel-contrib nitin/misc http://git.yoctoproject.org/cgit.cgi/meta-intel-contrib/log/?h=nitin/misc Nitin A Kamble (6): MAINTAINERS: corect pathname chiefriver README: add WebTitle Compliance information crownbay README: add WebTitle Compliance information emenlow README: add WebTitle Compliance information jasperforest README: add WebTitle Compliance information sugarbay README: add WebTitle Compliance information MAINTAINERS |2 +- meta-chiefriver/README | 10 +- meta-crownbay/README | 13 +++-- meta-emenlow/README | 11 ++- meta-jasperforest/README | 11 ++- meta-sugarbay/README |9 - 6 files changed, 49 insertions(+), 7 deletions(-) -- 1.7.3.4 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH 2/6] chiefriver README: add WebTitle Compliance information
On 10/23/2012 01:24 PM, nitin.a.kam...@intel.com wrote: From: Nitin A Kamble nitin.a.kam...@intel.com The WebTitle will be used to publish the BSP on the Yocto Project Website. And adding the Yocto Project Compliance information for the 1.3 release. Also specifying all the layers used from meta-intel repository. Signed-off-by: Nitin A Kamble nitin.a.kam...@intel.com --- meta-chiefriver/README | 10 +- 1 files changed, 9 insertions(+), 1 deletions(-) diff --git a/meta-chiefriver/README b/meta-chiefriver/README index 7c47b02..7af1288 100644 --- a/meta-chiefriver/README +++ b/meta-chiefriver/README @@ -6,6 +6,14 @@ The 'Chief River' platform consists of the Intel Ivy Bridge processor, plus the Panther Point PCH. This BSP assumes that the Ivy Bridge integrated graphics are being used. +WebTitle: Intel 3nd Generations Core Platforms: Core i3, i5, i7 (Ivy Bridge) s/3nd/3rd/ Otherwise looks fine. + + +Compliance: + +This BSP is compliant with Yocto Project as per requirements listed here: +http://www.yoctoproject.org/yocto-project-compatible-registration + Dependencies @@ -20,7 +28,7 @@ This layer depends on: branch: master URI: git://git.yoctoproject.org/meta-intel - layers: intel + layers: meta-intel, meta-chiefriver branch: master -- Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH 3/6] crownbay README: add WebTitle Compliance information
On 10/23/2012 01:24 PM, nitin.a.kam...@intel.com wrote: From: Nitin A Kamble nitin.a.kam...@intel.com The WebTitle will be used to publish the BSP on the Yocto Project Website. And adding the Yocto Project Compliance information for the 1.3 release. Also specifying all the layers used from meta-intel repository. Signed-off-by: Nitin A Kamble nitin.a.kam...@intel.com --- meta-crownbay/README | 13 +++-- 1 files changed, 11 insertions(+), 2 deletions(-) diff --git a/meta-crownbay/README b/meta-crownbay/README index 4bc9f31..3996a94 100644 --- a/meta-crownbay/README +++ b/meta-crownbay/README @@ -2,13 +2,22 @@ This README file contains information on building the meta-crownbay BSP layer, and booting the images contained in the /binary directory. Please see the corresponding sections below for details. -The Crown Bay platform consists of the Intel Atom Z6xx processor, +The Crown Bay platform consists of the Intel Atom E6xx processor, plus the Intel EG20T Platform Controller Hub (Tunnel Creek + Topcliff). How can we distinguish this from Queens Bay, which I would describe in exactly the same terms? -- Darren It also supports the E6xx embedded on-chip graphics via the Intel Embedded Media and Graphics Driver (EMGD) 1.14 Driver. +WebTitle: Intel Atom E6xx processor with Intel EG20T Controller Hub development kit (crownbay) + + +Compliance: + +This BSP is compliant with Yocto Project as per requirements listed here: +http://www.yoctoproject.org/yocto-project-compatible-registration + + Dependencies @@ -22,7 +31,7 @@ This layer depends on: branch: master URI: git://git.yoctoproject.org/meta-intel - layers: intel + layers: meta-intel, meta-crownbay branch: master -- Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH 6/6] sugarbay README: add WebTitle Compliance information
On 10/23/2012 01:24 PM, nitin.a.kam...@intel.com wrote: From: Nitin A Kamble nitin.a.kam...@intel.com The WebTitle will be used to publish the BSP on the Yocto Project Website. And adding the Yocto Project Compliance information for the 1.3 release. Also specifying all the layers used from meta-intel repository. Signed-off-by: Nitin A Kamble nitin.a.kam...@intel.com --- meta-sugarbay/README |9 - 1 files changed, 8 insertions(+), 1 deletions(-) diff --git a/meta-sugarbay/README b/meta-sugarbay/README index c8a99d7..36da170 100644 --- a/meta-sugarbay/README +++ b/meta-sugarbay/README @@ -6,6 +6,13 @@ The 'Sugar Bay' platform consists of the Intel Sandy Bridge processor, plus the Cougar Point PCH (Q67 Express or B65 Express chipsets). This BSP assumes that the Sandy Bridge integrated graphics are being used. +WebTitle: Intel 2nd Generations Core Platforms: Core i3, i5, i7 (Sandy Bridge) Some places you used merged lowercase terms crownbay and other places the capitalized expanded terms Sandy Bridge. I don't know which is more correct, but we should be consistent in our usage. -- Darren + +Compliance: + +This BSP is compliant with Yocto Project as per requirements listed here: +http://www.yoctoproject.org/yocto-project-compatible-registration + Dependencies @@ -20,7 +27,7 @@ This layer depends on: branch: master URI: git://git.yoctoproject.org/meta-intel - layers: intel + layers: meta-intel, meta-sugarbay branch: master -- Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] ERROR: Function failed: do_rootfs, poky commit id 8ce23f569584f195391bc5c68a780e1bf54e4360
Just out of curiosity... On Tue, Oct 23, 2012 at 3:53 PM, Burton, Ross ross.bur...@intel.com wrote: An alternative (and less intrusive) is to increase the commit timeout on the build partition How does one go about adjusting the commit timeout on a partition/disk? ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] build failures after pull
On Tuesday, 23 October 2012 at 18:47, Jim Abernathy wrote: I've reported this before, but it still happens. Today, I did a git pull into my local while master was checked out, both on poky and meta-intel. I then tried to rerun without cleaning or deleting anything for chiefriver. My last build had been successfully built, but didn't have audio. So when I saw patches, I thought I'd test again. I simply did source oe-init-build-env bitbake core-image-sato I got a failure in diffutils for some reason. I then did bitbake -c cleansstate diffutils bitbake core-image-sato. Next time, including the log of the task that failed (do_compile in diffutils, I presume) might help identify what broke. Ross ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH 3/6] crownbay README: add WebTitle Compliance information
On Tue, 2012-10-23 at 13:24 -0700, nitin.a.kam...@intel.com wrote: From: Nitin A Kamble nitin.a.kam...@intel.com The WebTitle will be used to publish the BSP on the Yocto Project Website. And adding the Yocto Project Compliance information for the 1.3 release. Also specifying all the layers used from meta-intel repository. Signed-off-by: Nitin A Kamble nitin.a.kam...@intel.com --- meta-crownbay/README | 13 +++-- 1 files changed, 11 insertions(+), 2 deletions(-) diff --git a/meta-crownbay/README b/meta-crownbay/README index 4bc9f31..3996a94 100644 --- a/meta-crownbay/README +++ b/meta-crownbay/README @@ -2,13 +2,22 @@ This README file contains information on building the meta-crownbay BSP layer, and booting the images contained in the /binary directory. Please see the corresponding sections below for details. -The Crown Bay platform consists of the Intel Atom Z6xx processor, +The Crown Bay platform consists of the Intel Atom E6xx processor, plus the Intel EG20T Platform Controller Hub (Tunnel Creek + Topcliff). It also supports the E6xx embedded on-chip graphics via the Intel Embedded Media and Graphics Driver (EMGD) 1.14 Driver. +WebTitle: Intel Atom E6xx processor with Intel EG20T Controller Hub development kit (crownbay) + I'm not sure this kind of thing should be in the README since we can have multiple downloadable BSPs per layer e.g. crownbay vs crownbay-noemgd. I suppose in keeping with the build system you could have separate WebTitle_crownbay and WebTitle_crownbay-noemgd lines. ;-) (and it would be nice if you could get rid of the CamelCaps too) Why not put this info in the machine.conf, where we already have fields meant to be machine parseable e.g. #@TYPE: Machine #@NAME: crownbay #@WEBTITLE: ... Or maybe just use the exisiting #@DESCRIPTION for that... + +Compliance: + For consistency with the rest of the README, please remove the colon and clean up the underlining. Thanks, Tom +This BSP is compliant with Yocto Project as per requirements listed here: +http://www.yoctoproject.org/yocto-project-compatible-registration + + Dependencies @@ -22,7 +31,7 @@ This layer depends on: branch: master URI: git://git.yoctoproject.org/meta-intel - layers: intel + layers: meta-intel, meta-crownbay branch: master ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Performance improvements and machine build configuration
On Tue, Oct 23, 2012 at 1:45 PM, Elvis Dowson elvis.dow...@gmail.com wrote: The only curious thing that I've noticed is that I don't see a large performance improvement using a standard 3TB Seagate Barracuda 7200 RPM HDD, and the two Intel Series 330 SSDs in a striped RAID0 configuration. The read (600MB/s) / write (838MB/s) figures are impressive, although I expected the read performance to be higher than write performance, as is normally with a single SSD. I'm using the motherboard's hardware RAID support on a 6GB/s SATA 3 port. You probably don't use much disk I/O with 16GB of memory for a build. -M ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH 3/6] crownbay README: add WebTitle Compliance information
On 10/23/2012 02:16 PM, Tom Zanussi wrote: On Tue, 2012-10-23 at 13:24 -0700, nitin.a.kam...@intel.com wrote: +WebTitle: Intel Atom E6xx processor with Intel EG20T Controller Hub development kit (crownbay) + I'm not sure this kind of thing should be in the README since we can have multiple downloadable BSPs per layer e.g. crownbay vs crownbay-noemgd. I suppose in keeping with the build system you could have separate WebTitle_crownbay and WebTitle_crownbay-noemgd lines. ;-) (and it would be nice if you could get rid of the CamelCaps too) Why not put this info in the machine.conf, where we already have fields meant to be machine parseable e.g. #@TYPE: Machine #@NAME: crownbay #@WEBTITLE: ... Oh much much better. -- Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Performance improvements and machine build configuration
On Tuesday, 23 October 2012 at 22:19, McClintock Matthew-B29882 wrote: On Tue, Oct 23, 2012 at 1:45 PM, Elvis Dowson elvis.dow...@gmail.com (mailto:elvis.dow...@gmail.com) wrote: The only curious thing that I've noticed is that I don't see a large performance improvement using a standard 3TB Seagate Barracuda 7200 RPM HDD, and the two Intel Series 330 SSDs in a striped RAID0 configuration. The read (600MB/s) / write (838MB/s) figures are impressive, although I expected the read performance to be higher than write performance, as is normally with a single SSD. I'm using the motherboard's hardware RAID support on a 6GB/s SATA 3 port. You probably don't use much disk I/O with 16GB of memory for a build. My machine has 16G of RAM, and after a good build will have 12G of cache (according to /proc), but the disk activity light was frantic. I can only imagine it would be more frantic with less RAM to act as an over-sized disk cache. Ross ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] ERROR: Function failed: do_rootfs, poky commit id 8ce23f569584f195391bc5c68a780e1bf54e4360
On Tuesday, 23 October 2012 at 22:03, Trevor Woerner wrote: Just out of curiosity... On Tue, Oct 23, 2012 at 3:53 PM, Burton, Ross ross.bur...@intel.com (mailto:ross.bur...@intel.com) wrote: An alternative (and less intrusive) is to increase the commit timeout on the build partition How does one go about adjusting the commit timeout on a partition/disk? commit=[duration in seconds] in fstab. See the fstab man page for more examples. Ross ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Performance improvements and machine build configuration
On Tue, Oct 23, 2012 at 4:24 PM, Ross Burton ross.bur...@intel.com wrote: On Tuesday, 23 October 2012 at 22:19, McClintock Matthew-B29882 wrote: On Tue, Oct 23, 2012 at 1:45 PM, Elvis Dowson elvis.dow...@gmail.com (mailto:elvis.dow...@gmail.com) wrote: The only curious thing that I've noticed is that I don't see a large performance improvement using a standard 3TB Seagate Barracuda 7200 RPM HDD, and the two Intel Series 330 SSDs in a striped RAID0 configuration. The read (600MB/s) / write (838MB/s) figures are impressive, although I expected the read performance to be higher than write performance, as is normally with a single SSD. I'm using the motherboard's hardware RAID support on a 6GB/s SATA 3 port. You probably don't use much disk I/O with 16GB of memory for a build. My machine has 16G of RAM, and after a good build will have 12G of cache (according to /proc), but the disk activity light was frantic. I can only imagine it would be more frantic with less RAM to act as an over-sized disk cache. Frantic but was it actually limiting the build time? It would seem not according to Elvis observations. -M ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Performance improvements and machine build configuration
On Tuesday, 23 October 2012 at 22:37, McClintock Matthew-B29882 wrote: My machine has 16G of RAM, and after a good build will have 12G of cache (according to /proc), but the disk activity light was frantic. I can only imagine it would be more frantic with less RAM to act as an over-sized disk cache. Frantic but was it actually limiting the build time? It would seem not according to Elvis observations. No idea, it's always had 16G. One day I'll do some benchmarking. Ross ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] the use of the files in meta/lib
On Tue, Oct 23, 2012 at 6:39 PM, Liu treeb...@embedstudy.com wrote: I'm wondering the function of the directory meta/lib.I suspect the files are imported as modules by .bbclass.Is there any good reference docs about the python files in the directory ? They can be used by any python anywhere in the metadata. Some of its modules are automatically imported for all to use at any time, some are not. See base.bbclass and the OE_IMPORTS variable to see which are auto-imported. The only docs on them, as far as I know, is the code itself. There isn't a great deal of code, so I'd suggest perusing it directly. -- Christopher Larson ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Minutes: Yocto Project Technical Team Meeting - Tuesday, October 23, 2012 8:00 AM-9:00 AM (UTC-08:00) Pacific Time (US Canada).
Decision: - The community has unanimously agreed to release RC4 as the 1.3 release. Congrats to the team! Thank you all. Attendees: MichaelH, Mihai, Jessica, Beth, PaulE, JeffP, Sean, Kevin, Nitin, ScottR, Nitin, Amit, ChrisL, Bruce, Dave, Saul, Denys, Song Minutes: * Clarification: What kind of things we can have in opens and team sharing: - Opens: Anything you would like to have an open discussion or raise to others, including technical issues, questions, feature or fix proposals, request for feedback, blockers, concerns, suggestions, etc. - Team sharing: Anything you have done around YP in the past week, plan for the current week, issues, road blockers, need help from others, etc. Such as development work, conference experience, etc. * Opens collection - 5 min (Song) * Yocto 1.3 release readiness - 20 min (Song/team) https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.3_Status#Milestone_5_.281.3_release.29 - Release criteria review: All criteria has been met with RC4. - The QA report on RC4 is the cleanest QA report we have seen for the entire release. Very few issues. - Completed 71% of the work we planned for 1.3, compared with 1.2. - Fixed close to 570 bugs with medium or higher priority. - Dave: release criteria on performance, try common use case build. Set a performance target. . RP: have a suite of matrix for performance, including things such as disk space, time to run a special command, overhead of starting a bitbake.etc. . Beth: will work on the feature request for this performance measure. Will work with QA on this. - The community has unanimously agreed to release RC4 as the 1.3 release. Congrats to the team! Thank you all. * SWAT team rotation: Saul - Nitin - RP: AB is building everything, so far, it's not too bad. There are some failures on BSPs. * Opens - 10 min - Song: Mentor's plan around 1.4 timeframe. . Sean: continue to align mentor linux release with YP release. Interested to see how things move forward with webhob, will provide some feedback. Trying to aligning next mentor release with 1.3 now. The team is busy working on Mentor Linux now. * Team Sharing - 20 min - Mihai: working on an approach on package testing. Basic idea is to run make test for each package by including a new class. The test is run in the building environment (host machine). Will contact Bjorn (Enea) for this. Working on PPM module layer for poky. Just published yesterday, it's experimental. - MichaelH: added secondary DNS server, no interruption of server on rebooting now. https access is there, bottom of every git page. A lots of work with Jeff and others on content moving for new web site. Jeff is relieved. Package reporting website. Just got moderation on wiki account. Separate package reporting with download site. Getting download site for 1.3 ready. - Beth: added something to dev manual. How to release product with YP. Particularly with source archiver. LF checked it, generally pleased. - RP: focused on performance, we enabled sstate n 1.3, there are some issues if you have multiple machines sharing a common package architecture. Been unwinding the issue and looking at the shared lib code. Dealing with files, copying files. Debug package. Performance is one of the themes for 1.4. changes to autotool bbclass is happening. ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-intel/danny][PATCH] meta-crystalforest, linux-yocto_3.4.bbappend: Pin LINUX_VERSION
meta-crystalforest BSPs uses 3.4.9 kernel but the default yocto kernel is 3.4.11, if we do not pin the LINUX_VERSION then we get inconsistent version number for bzImage and the modules where modules are installed under /lib/modules/3.4.9-yocto-standard/ but kernel is called bzImage-3.4.11+git2+9e3bdb7344054264b750e53fbbb6394cc1c942ac_1+0985844fa6235422c67ef269952fa4e765f252f9-r4.3-crystalforest-stargo-20121024031021.bin This patch fixes this mismatch. Beaware that other BSPs from meta-intel may need something similar too. Signed-off-by: Khem Raj raj.k...@gmail.com --- .../recipes-kernel/linux/linux-yocto_3.4.bbappend |3 +++ 1 file changed, 3 insertions(+) diff --git a/meta-crystalforest/recipes-kernel/linux/linux-yocto_3.4.bbappend b/meta-crystalforest/recipes-kernel/linux/linux-yocto_3.4.bbappend index 082fe38..92aaa61 100644 --- a/meta-crystalforest/recipes-kernel/linux/linux-yocto_3.4.bbappend +++ b/meta-crystalforest/recipes-kernel/linux/linux-yocto_3.4.bbappend @@ -15,3 +15,6 @@ SRCREV_machine_pn-linux-yocto_crystalforest-shumway ?= 0985844fa6235422c67ef269 SRCREV_meta_pn-linux-yocto_crystalforest-shumway ?= 9e3bdb7344054264b750e53fbbb6394cc1c942ac module_autoload_uio = uio + +LINUX_VERSION = 3.4.9 + -- 1.7.9.5 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH 2/3] fri2: README: Correct typographical and wording errors
Correct minor issues reported by Steve S. Signed-off-by: Darren Hart dvh...@linux.intel.com Reported-by: Steve Sakoman st...@sakoman.com --- meta-fri2/README |6 +++--- 1 files changed, 3 insertions(+), 3 deletions(-) diff --git a/meta-fri2/README b/meta-fri2/README index a866174..05b7257 100644 --- a/meta-fri2/README +++ b/meta-fri2/README @@ -154,8 +154,8 @@ example: # eject /dev/sdf This should give you a bootable USB flash device. Insert the device -into a bootable USB socket on the target, and power on. This should -result in a system booted to the Sato graphical desktop. +into one of the USB host ports on the target, and power on. This +should result in a system booted to the Sato graphical desktop. If you want a terminal, use the arrows at the top of the UI to move to different pages of available applications, one of which is named @@ -242,7 +242,7 @@ e. GPIO --- The FRI2 has two I2C PCA555x GPIO devices used for internal control signals. These have not been exposed in the current release of the -BSP, but may be in the future. Regardless, these do would not provide +BSP, but may be in the future. Regardless, these would not provide general purpose IO with which to read or drive additional signals. f. MMC -- 1.7.5.4 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH 1/3] fri2: Add linux-yocto-tiny_3.4 support
Add support for the tiny KTYPE via a liunx-yocto-tiny bbappend
for the 3.4 kernel. With this kernel, DISTRO=poky-tiny can be
used with the fri2 and fri2-noemgd machines.
Signed-off-by: Darren Hart dvh...@linux.intel.com
---
.../linux/linux-yocto-tiny_3.4.bbappend| 14 ++
1 files changed, 14 insertions(+), 0 deletions(-)
create mode 100644 meta-fri2/recipes-kernel/linux/linux-yocto-tiny_3.4.bbappend
diff --git a/meta-fri2/recipes-kernel/linux/linux-yocto-tiny_3.4.bbappend
b/meta-fri2/recipes-kernel/linux/linux-yocto-tiny_3.4.bbappend
new file mode 100644
index 000..bc96859
--- /dev/null
+++ b/meta-fri2/recipes-kernel/linux/linux-yocto-tiny_3.4.bbappend
@@ -0,0 +1,14 @@
+FILESEXTRAPATHS_prepend := ${THISDIR}/${PN}:
+
+COMPATIBLE_MACHINE_fri2 = fri2
+KMACHINE_fri2 = fri2
+KBRANCH_fri2 = standard/tiny/base
+#SRCREV_machine_pn-linux-yocto-tiny_fri2 ?=
449f7f520350700858f21a5554b81cc8ad23267d
+SRCREV_meta_pn-linux-yocto-tiny_fri2 ?=
2ec32d511b62d44b63e8560a9b1d6895a5dac695
+
+
+COMPATIBLE_MACHINE_fri2-noemgd = fri2-noemgd
+KMACHINE_fri2-noemgd = fri2
+KBRANCH_fri2-noemgd = standard/tiny/base
+#SRCREV_machine_pn-linux-yocto-tiny_fri2-noemgd ?=
449f7f520350700858f21a5554b81cc8ad23267d
+SRCREV_meta_pn-linux-yocto-tiny_fri2-noemgd ?=
2ec32d511b62d44b63e8560a9b1d6895a5dac695
--
1.7.5.4
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH 3/3] fri2: Add grub-efi workaround for USB keyboard initialization
The Fastboot firmware will sometimes fail to init the USB keyboard when
connected directly in 1.0 mode (works fine through a 2.0 hub). By adding
the USB modules to the grub-efi build, we can ensure the keyboard will
be available in the grub menu at the expense of about a second in boot
time.
Signed-off-by: Darren Hart dvh...@linux.intel.com
---
.../recipes-bsp/grub/grub-efi-native_2.00.bbappend | 11 +++
1 files changed, 11 insertions(+), 0 deletions(-)
create mode 100644 meta-fri2/recipes-bsp/grub/grub-efi-native_2.00.bbappend
diff --git a/meta-fri2/recipes-bsp/grub/grub-efi-native_2.00.bbappend
b/meta-fri2/recipes-bsp/grub/grub-efi-native_2.00.bbappend
new file mode 100644
index 000..c6904ef
--- /dev/null
+++ b/meta-fri2/recipes-bsp/grub/grub-efi-native_2.00.bbappend
@@ -0,0 +1,11 @@
+# The Intel provided Fast Boot Firmware may not initialize the USB keyboard
+# before launching the grub.efi payload. Ensure GRUB has keyboard control by
+# building in the usb, usb_keyboard, and ohci modules.
+
+do_mkimage() {
+ ./grub-mkimage -p /EFI/BOOT -d ./grub-core/ \
+ -O ${GRUB_TARGET}-efi -o ./${GRUB_IMAGE} \
+ boot linux ext2 fat serial part_msdos part_gpt normal
efi_gop \
+ usb usb_keyboard ohci
+}
+
--
1.7.5.4
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
