Re: [yocto] Performance improvements and machine build configuration
Hi Chris, On Oct 23, 2012, at 11:39 PM, Chris Tapp wrote: > On 23 Oct 2012, at 19:45, Elvis Dowson wrote: > >> I noticed that between commits >> >> http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=0260bb5c6978839c068007fcff2f704937805faf >> >> and >> >> http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=a3d5e9e6b7729319c518dcaf25bbe0643bfb25db >> >> the build time has improved by around 7 minutes for my machine >> configuration, for building a core-image-minimal rootfs for the Xilinx >> ZC-702 FPGA with dual ARM Cortex A-9 CPUs. >> >> commit id 0260bb5c6978839c068007fcff2f704937805faftook 29 minutes >> commit id a3d5e9e6b7729319c518dcaf25bbe0643bfb25db took 22 minutes >> >> The machine configuration is an Intel i7 3770K over-clocked to 4.2GHz, with >> 16GB RAM at 1600Mhz, two 120GB SSDs configured into a striped disk array >> (Intel 330 series SSDs) with a write performance of 838MB/s and read >> performance of around 600MB/s, in RAID0 configuration, with a Corsair HT100 >> liquid CPU cooler keeping the CPU cool at around 52 degree centigrade during >> the build process. The motherboard is a gigabyte GA-Z77X-UP5TH >> >> http://www.gigabyte.com/products/product-page.aspx?pid=4279#ov >> >> This motherboard has a thunderbolt display port, so I can re-use my existing >> Apple Thunderbolt display. I've run Ubuntu 12.04.1 LTS and Ubuntu 12.10, and >> it appears to work after a few tweaks. >> >> 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. >> >> The 3TB HDD took the approximately 2 or 3 minutes longer than the 120GB x 2 >> RAID0 SSD configuration for commit id >> 0260bb5c6978839c068007fcff2f704937805faf (31 minutes vs. 29 minutes). >> >> My local.conf parallelism settings were set to 6 threads for bitbake and >> make, for the quad-core (virtual 8 cpu cores)system. >> >> Has anyone tried yocto builds with a 6-core, 8-core or 10-core Xeon >> processor system? How do those figures fare? I'm thinking my current >> bottleneck might be the CPU and not the HDD (?!), for the yocto build >> workloads, which I find curious and would like to confirm. > > > I did quite a bit of experimenting with this a while back (similar spec, but > with nearly 1000MB/s read/write SDD array). CPU was quad core with > hyper-threading, so 8 virtual cores. I generally run with 16 threads, 16 > parallel make as I find that the main performance hit is running out of stuff > to keep all the cores busy. > > Most of the time all 8 cores are maxed out, but around when the kernel gets > built (and cross tools needed for it) I see the total CPU use drop to about > 25%. This isn't because the system is I/O bound; it simply doesn't have > enough tasks ready to run at that point in time. > > I estimate that my 55 min build times would come down by 10 to 15 minutes if > I could keep the CPUs busy (still, much better than the 10 hour build times > on my previous system!). > With the poky/master branch commit 33440ee70623394d06a4b214c2be10788cba6d08, which is the tip master branch, I tried two builds 01. parallelism set to 16, which took 23 minutes 21 seconds. 02. parallelism set to 6, which took less time at 22 minutes 13 seconds. Therefore, for a quad core machine (Intel i7-3770K @ 4.2GHz over-clocked, 16GB 1600MHz RAM), setting the parallelism parameters to 6 appears to be better than setting it to 16. Run # 01 BB_NUMBER_THREADS = "16" PARALLEL_MAKE = "-j 16" Build Configuration: BB_VERSION= "1.16.0" TARGET_ARCH = "arm" TARGET_OS = "linux-gnueabi" MACHINE = "zynq-zc702" DISTRO= "poky" DISTRO_VERSION= "1.3+snapshot-20121025" TUNE_FEATURES = "armv7a vfp neon cortexa9" TARGET_FPU= "vfp-neon" meta meta-yocto= "master:33440ee70623394d06a4b214c2be10788cba6d08" toolchain-layer = "master:55855cd569fbff7182974ca08b1de8435bf0f597" meta-zynq-balister = "master-xilinx-zc702-gcc-4.7:d168cea411034d1f1530e4eacf6eb3ce4affd1c8" NOTE: Res
[yocto] [PATCH] gnu-efi: add missing sha256 checksum
Signed-off-by: Ross Burton
---
common/recipes-bsp/gnu-efi/gnu-efi_3.0m.bb |1 +
1 file changed, 1 insertion(+)
diff --git a/common/recipes-bsp/gnu-efi/gnu-efi_3.0m.bb
b/common/recipes-bsp/gnu-efi/gnu-efi_3.0m.bb
index a0d5823..f8015f2 100644
--- a/common/recipes-bsp/gnu-efi/gnu-efi_3.0m.bb
+++ b/common/recipes-bsp/gnu-efi/gnu-efi_3.0m.bb
@@ -13,6 +13,7 @@ SRC_URI =
"http://downloads.sourceforge.net/gnu-efi/gnu-efi_3.0m.orig.tar.gz \
file://parallel-make.patch \
"
SRC_URI[md5sum] = "d0a21125aee56c0c7291ad260e916cb3"
+SRC_URI[sha256sum] =
"b7fb638f5ec8faa6edebe54beb90957f01f70a2a948d1b58b834c8d7f86d"
S = "${WORKDIR}/gnu-efi-3.0"
--
1.7.10
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] build failures after pull
On 23 October 2012 22:12, Ross Burton wrote: > 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. I saw this last night, and have a patch ready. Ross ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-intel/danny][PATCH] meta-crystalforest, linux-yocto_3.4.bbappend: Pin LINUX_VERSION
On Tue, 2012-10-23 at 20:56 -0700, Khem Raj wrote: > 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. This is because the crystalforest BSP is using ancient kernel SRCREVs, corresponding to 3.4.9. Thanks for sending this patch , but I just pushed a fix for the source of the problem by updating the SRCREVs instead. Tom > > Signed-off-by: Khem Raj > --- > .../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" > + ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-intel/danny][PATCH] meta-crystalforest, linux-yocto_3.4.bbappend: Pin LINUX_VERSION
That's fine though you should still pin it since it may go out of sync with oecore again On Thursday, October 25, 2012, Tom Zanussi wrote: > On Tue, 2012-10-23 at 20:56 -0700, Khem Raj wrote: >> 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. > > This is because the crystalforest BSP is using ancient kernel SRCREVs, > corresponding to 3.4.9. > > Thanks for sending this patch , but I just pushed a fix for the source > of the problem by updating the SRCREVs instead. > > Tom > >> >> Signed-off-by: Khem Raj >> --- >> .../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" >> + > > > ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Ubuntu 10.04 don't support mirror option with parameter
Am 24.10.2012 19:02, schrieb Paul Eggleton: On Wednesday 24 October 2012 18:30:12 Stefan Herbrechtsmeier wrote: the git version of Ubuntu 10.04 is to old to support mirror option with parameter which is used by the bitbake fetch2. Regards, Stefan DEBUG: ... git remote add --mirror=fetch origin git://git.yoctoproject.org/opkg-utils ERROR: Fetcher failure: Fetch command failed with exit code 129, output: error: option `mirror' takes no value usage: git remote add [] -f, --fetch fetch the remote branches -t, --track branch(es) to track -m, --master master branch --mirror no separate remotes Which version of the build system are you using? In master and the upcoming danny / 1.3 release we have a check in the bitbake wrapper script to determine if a newer version of git needs to be built (if the host's version of git is older than 1.7.5); if so we build one (git-replacement-native). The denzil / 1.2 release does not have this, however. Sorry, you are right. Likely I have terminate the bitbake run after pseudo-native but before git-replacement-native finished. Regards, Stefan ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH v2 2/6] chiefriver: add WEBTITLE & Compliance information
> -Original Message- > From: Zanussi, Tom > Sent: Wednesday, October 24, 2012 5:15 PM > To: Kamble, Nitin A > Cc: yocto@yoctoproject.org; Hart, Darren > Subject: Re: [PATCH v2 2/6] chiefriver: add WEBTITLE & Compliance > information > > On Wed, 2012-10-24 at 13:25 -0700, nitin.a.kam...@intel.com wrote: > > From: Nitin A Kamble > > > > 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 > > --- > > meta-chiefriver/README |8 +++- > > meta-chiefriver/conf/machine/chiefriver.conf |2 ++ > > 2 files changed, 9 insertions(+), 1 deletions(-) > > > > diff --git a/meta-chiefriver/README b/meta-chiefriver/README index > > 7c47b02..249a389 100644 > > --- a/meta-chiefriver/README > > +++ b/meta-chiefriver/README > > @@ -7,6 +7,12 @@ plus the Panther Point PCH. This BSP assumes that > > the Ivy Bridge integrated graphics are being used. > > > > > > +Compliance > > +== > > +This BSP is compliant with Yocto Project as per requirements listed here: > > +http://www.yoctoproject.org/yocto-project-compatible-registration > > + > > To be consistent with the rest of the README, there should be a blank line > between the = and the 'This BSP... ' text. > > Also, for readability, it would be nice to have the URL also separated by a > blank line from the preceding text, and indented a couple spaces like similar > lines in the README. > > Also, I think the compliance text reads better as: > > This BSP is compliant with the Yocto Project as per the requirements listed > here: > > > + > > Dependencies > > > > > > @@ -20,7 +26,7 @@ This layer depends on: > >branch: master > > > >URI: git://git.yoctoproject.org/meta-intel > > - layers: intel > > + layers: meta-intel, meta-chiefriver > > If you look at the meta-intel/conf/layer.conf, you see the layer actually is > 'intel'. > > Also, this is the README for the chiefriver layer, so it can't depend on > itself > i.e. meta-chiefriver or 'chiefriver' shouldn't be listed in layers Tom, As part of the compliance we need to list all the components/layers needed to build the BSP. So even though it is README from this layer I think it should be listed as one of dependency for building the BSP. And I will incorporate the rest of the feedback in the next pull request. Nitin > > >branch: master > > > > > > diff --git a/meta-chiefriver/conf/machine/chiefriver.conf > > b/meta-chiefriver/conf/machine/chiefriver.conf > > index b8b8754..5005ce0 100644 > > --- a/meta-chiefriver/conf/machine/chiefriver.conf > > +++ b/meta-chiefriver/conf/machine/chiefriver.conf > > @@ -1,6 +1,8 @@ > > #@TYPE: Machine > > #@NAME: chiefriver > > > > +#@WEBTITLE: Intel 3rd Generations Core Platforms: Core i3, i5, i7 > > +(Ivy Bridge) > > + > > Since this is text that will appear on the website, we need to be a little > picky > about grammar: it should read '3rd Generation' rather than '3rd Generations' > > These comments apply to the other README files as well, so I won't repeat > them there, other than to fix any text that might appear on the website for > those as well... > > Tom > > > #@DESCRIPTION: Machine configuration for Chief River systems # i.e. > > Ivy Bridge + Panther Point > > > ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH v2 2/6] chiefriver: add WEBTITLE & Compliance information
> > > > If you look at the meta-intel/conf/layer.conf, you see the layer > > actually is 'intel'. > > > > Also, this is the README for the chiefriver layer, so it can't depend > > on itself i.e. meta-chiefriver or 'chiefriver' shouldn't be listed in > > layers > > Tom, >As part of the compliance we need to list all the components/layers needed > to build the BSP. So even though it is README from this layer I think it > should > be listed as one of dependency for building the BSP. Tom, It's ok, there are other places in the README where these layers are mentioned. So I can take this change out too. Thanks, Nitin ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [Patch v3 0/7] meta-intel README updates
From: Nitin A Kamble This is v3 of the pull request based on the latest feedback from Tom. Thanks, Nitin The following changes since commit 49a8eb06bd75bb898a1b9bc4212b3db3a6d26b97: meta-crystalforest: update kernel SRCREVs (2012-10-25 09:44:26 -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 (7): MAINTAINERS: correct pathname chiefriver: add WEBTITLE & Compliance information crownbay: add WEBTITLE & Compliance information emenlow: add WEBTITLE & Compliance information jasperforest: add WEBTITLE & Compliance information sugarbay: add WEBTITLE & Compliance information crownbay: add more information in README MAINTAINERS |2 +- meta-chiefriver/README |8 meta-chiefriver/conf/machine/chiefriver.conf |2 ++ meta-crownbay/README | 12 +++- meta-crownbay/conf/machine/crownbay-noemgd.conf |2 ++ meta-crownbay/conf/machine/crownbay.conf |2 ++ meta-emenlow/README |8 meta-emenlow/conf/machine/emenlow.conf |2 ++ meta-jasperforest/README |7 +++ meta-jasperforest/conf/machine/jasperforest.conf |2 ++ meta-sugarbay/README |8 meta-sugarbay/conf/machine/sugarbay.conf |2 ++ 12 files changed, 55 insertions(+), 2 deletions(-) -- 1.7.3.4 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [Patch v3 2/7] chiefriver: add WEBTITLE & Compliance information
From: Nitin A Kamble 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. Signed-off-by: Nitin A Kamble --- meta-chiefriver/README |8 meta-chiefriver/conf/machine/chiefriver.conf |2 ++ 2 files changed, 10 insertions(+), 0 deletions(-) diff --git a/meta-chiefriver/README b/meta-chiefriver/README index 7c47b02..43050de 100644 --- a/meta-chiefriver/README +++ b/meta-chiefriver/README @@ -7,6 +7,14 @@ plus the Panther Point PCH. This BSP assumes that the Ivy Bridge integrated graphics are being used. +Compliance +== + +This BSP is compliant with Yocto Project as per the requirements listed +here: + http://www.yoctoproject.org/yocto-project-compatible-registration + + Dependencies diff --git a/meta-chiefriver/conf/machine/chiefriver.conf b/meta-chiefriver/conf/machine/chiefriver.conf index 6d8d3a5..754acda 100644 --- a/meta-chiefriver/conf/machine/chiefriver.conf +++ b/meta-chiefriver/conf/machine/chiefriver.conf @@ -1,6 +1,8 @@ #@TYPE: Machine #@NAME: chiefriver +#@WEBTITLE: Intel 3rd Generation Core Platforms: Core i3, i5, i7 (Ivy Bridge) + #@DESCRIPTION: Machine configuration for Chief River systems # i.e. Ivy Bridge + Panther Point -- 1.7.3.4 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [Patch v3 4/7] emenlow: add WEBTITLE & Compliance information
From: Nitin A Kamble 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. Signed-off-by: Nitin A Kamble --- meta-emenlow/README|8 meta-emenlow/conf/machine/emenlow.conf |2 ++ 2 files changed, 10 insertions(+), 0 deletions(-) diff --git a/meta-emenlow/README b/meta-emenlow/README index 3932718..8795864 100644 --- a/meta-emenlow/README +++ b/meta-emenlow/README @@ -13,6 +13,14 @@ depending on which BSP tarball you downloaded. Please see the corresponding sections below for details. +Compliance +== + +This BSP is compliant with Yocto Project as per the requirements listed +here: + http://www.yoctoproject.org/yocto-project-compatible-registration + + Dependencies diff --git a/meta-emenlow/conf/machine/emenlow.conf b/meta-emenlow/conf/machine/emenlow.conf index d1efbc3..1a4aa81 100644 --- a/meta-emenlow/conf/machine/emenlow.conf +++ b/meta-emenlow/conf/machine/emenlow.conf @@ -1,6 +1,8 @@ #@TYPE: Machine #@NAME: emenlow +#@WEBTITLE: Intel Atom Z5xx Processor With Intel US15W Controller Hub (eMenlow) + #@DESCRIPTION: Machine configuration for eMenlow based systems, like the # Webs-2120 box. -- 1.7.3.4 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [Patch v3 6/7] sugarbay: add WEBTITLE & Compliance information
From: Nitin A Kamble 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. Signed-off-by: Nitin A Kamble --- meta-sugarbay/README |8 meta-sugarbay/conf/machine/sugarbay.conf |2 ++ 2 files changed, 10 insertions(+), 0 deletions(-) diff --git a/meta-sugarbay/README b/meta-sugarbay/README index c8a99d7..9201adf 100644 --- a/meta-sugarbay/README +++ b/meta-sugarbay/README @@ -7,6 +7,14 @@ plus the Cougar Point PCH (Q67 Express or B65 Express chipsets). This BSP assumes that the Sandy Bridge integrated graphics are being used. +Compliance +== + +This BSP is compliant with Yocto Project as per the requirements listed +here: + http://www.yoctoproject.org/yocto-project-compatible-registration + + Dependencies diff --git a/meta-sugarbay/conf/machine/sugarbay.conf b/meta-sugarbay/conf/machine/sugarbay.conf index 616c2c5..afa3328 100644 --- a/meta-sugarbay/conf/machine/sugarbay.conf +++ b/meta-sugarbay/conf/machine/sugarbay.conf @@ -1,6 +1,8 @@ #@TYPE: Machine #@NAME: sugarbay +#@WEBTITLE: Intel 2nd Generation Core Platforms: Core i3, i5, i7 (Sandy Bridge) + #@DESCRIPTION: Machine configuration for Sugar Bay systems # i.e. Sandy Bridge + Cougar Point -- 1.7.3.4 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [Patch v3 7/7] crownbay: add more information in README
From: Nitin A Kamble Mention Little Bay & Shell Bay boards from the crownbay kit in the readme. Signed-off-by: Nitin A Kamble --- meta-crownbay/README |2 ++ 1 files changed, 2 insertions(+), 0 deletions(-) diff --git a/meta-crownbay/README b/meta-crownbay/README index 1f164f4..525b2e6 100644 --- a/meta-crownbay/README +++ b/meta-crownbay/README @@ -5,6 +5,8 @@ Please see the corresponding sections below for details. The Crown Bay platform consists of the Intel Atom E6xx processor, plus the Intel EG20T Platform Controller Hub (Tunnel Creek + Topcliff). +The crownbay kit consists of two boards, Shell Bay & Little Bay. + It also supports the E6xx embedded on-chip graphics via the Intel Embedded Media and Graphics Driver (EMGD) 1.14 Driver. -- 1.7.3.4 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [Patch v3 5/7] jasperforest: add WEBTITLE & Compliance information
From: Nitin A Kamble 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. Signed-off-by: Nitin A Kamble --- meta-jasperforest/README |7 +++ meta-jasperforest/conf/machine/jasperforest.conf |2 ++ 2 files changed, 9 insertions(+), 0 deletions(-) diff --git a/meta-jasperforest/README b/meta-jasperforest/README index 12f84c2..deedb28 100644 --- a/meta-jasperforest/README +++ b/meta-jasperforest/README @@ -8,6 +8,13 @@ combined with the Intel 3420 PCH chipset (Ibex Peak) make up the 'Picket Post' CRB this BSP was developed on. +Compliance +== + +This BSP is compliant with Yocto Project as per requirements listed here: +http://www.yoctoproject.org/yocto-project-compatible-registration + + Dependencies diff --git a/meta-jasperforest/conf/machine/jasperforest.conf b/meta-jasperforest/conf/machine/jasperforest.conf index d661f7b..ba50b99 100644 --- a/meta-jasperforest/conf/machine/jasperforest.conf +++ b/meta-jasperforest/conf/machine/jasperforest.conf @@ -1,6 +1,8 @@ #@TYPE: Machine #@NAME: jasperforest +#@WEBTITLE: Intel Xeon C5500/C3500 Series Processors With Intel 3420 PCH Chipset (Jasper Forest) + #@DESCRIPTION: Machine configuration for Jasper Forest Picket Post # systems i.e. Xeon C5500/C3500 + Intel 3420 chipset (Ibex Peak) -- 1.7.3.4 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [Patch v3 3/7] crownbay: add WEBTITLE & Compliance information
From: Nitin A Kamble 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. Signed-off-by: Nitin A Kamble --- meta-crownbay/README| 10 +- meta-crownbay/conf/machine/crownbay-noemgd.conf |2 ++ meta-crownbay/conf/machine/crownbay.conf|2 ++ 3 files changed, 13 insertions(+), 1 deletions(-) diff --git a/meta-crownbay/README b/meta-crownbay/README index 4bc9f31..1f164f4 100644 --- a/meta-crownbay/README +++ b/meta-crownbay/README @@ -2,13 +2,21 @@ 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. +Compliance +== + +This BSP is compliant with Yocto Project as per the requirements listed +here: + http://www.yoctoproject.org/yocto-project-compatible-registration + + Dependencies diff --git a/meta-crownbay/conf/machine/crownbay-noemgd.conf b/meta-crownbay/conf/machine/crownbay-noemgd.conf index 4c869ee..c6f816a 100644 --- a/meta-crownbay/conf/machine/crownbay-noemgd.conf +++ b/meta-crownbay/conf/machine/crownbay-noemgd.conf @@ -1,6 +1,8 @@ #@TYPE: Machine #@NAME: crownbay-noemgd +#@WEBTITLE: Intel Atom E6xx Processor With Intel EG20T Controller Hub Development Kit (Crown Bay) With Open Source VESA Graphics + #@DESCRIPTION: Machine configuration for Crown Bay systems, without Intel-proprietary graphics bits # i.e. E660 + EG20T diff --git a/meta-crownbay/conf/machine/crownbay.conf b/meta-crownbay/conf/machine/crownbay.conf index 624ca56..1fd9fe8 100644 --- a/meta-crownbay/conf/machine/crownbay.conf +++ b/meta-crownbay/conf/machine/crownbay.conf @@ -1,6 +1,8 @@ #@TYPE: Machine #@NAME: crownbay +#@WEBTITLE: Intel Atom E6xx Processor With Intel EG20T Controller Hub Development Kit (Crown Bay) With Proprietary IEMGD Accelerated Graphics + #@DESCRIPTION: Machine configuration for Crown Bay systems # i.e. E660 + EG20T -- 1.7.3.4 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [Patch v3 1/7] MAINTAINERS: correct pathname
From: Nitin A Kamble 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 --- 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 Kamble -F: common/recipes-core/ +F: common/ CROWNBAY M: Nitin A Kamble -- 1.7.3.4 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [Patch v3 0/7] meta-intel README updates
On Thu, 2012-10-25 at 10:49 -0700, nitin.a.kam...@intel.com wrote: > From: Nitin A Kamble > > This is v3 of the pull request based on the latest feedback from Tom. > > Thanks, > Nitin > > The following changes since commit 49a8eb06bd75bb898a1b9bc4212b3db3a6d26b97: > > meta-crystalforest: update kernel SRCREVs (2012-10-25 09:44:26 -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 (7): > MAINTAINERS: correct pathname > chiefriver: add WEBTITLE & Compliance information > crownbay: add WEBTITLE & Compliance information > emenlow: add WEBTITLE & Compliance information > jasperforest: add WEBTITLE & Compliance information > sugarbay: add WEBTITLE & Compliance information Pulled into meta-intel/master. I fixed up the compliance sections a bit though i.e. changed 'Yocto Project to 'the Yocto Project' and added a blank line before the URLs. Tom > crownbay: add more information in README > > MAINTAINERS |2 +- > meta-chiefriver/README |8 > meta-chiefriver/conf/machine/chiefriver.conf |2 ++ > meta-crownbay/README | 12 +++- > meta-crownbay/conf/machine/crownbay-noemgd.conf |2 ++ > meta-crownbay/conf/machine/crownbay.conf |2 ++ > meta-emenlow/README |8 > meta-emenlow/conf/machine/emenlow.conf |2 ++ > meta-jasperforest/README |7 +++ > meta-jasperforest/conf/machine/jasperforest.conf |2 ++ > meta-sugarbay/README |8 > meta-sugarbay/conf/machine/sugarbay.conf |2 ++ > 12 files changed, 55 insertions(+), 2 deletions(-) > ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-intel/danny][PATCH] meta-crystalforest, linux-yocto_3.4.bbappend: Pin LINUX_VERSION
On Thu, 2012-10-25 at 08:36 -0700, Khem Raj wrote: > That's fine though you should still pin it since it may go out of sync > with oecore again > Good point. I think I'm going to start submitting weekly kernel SRCREV updates for all the meta-intel BSPs along with the matching LINUX_VERSIONs to avoid this problem in the future... Tom > On Thursday, October 25, 2012, Tom Zanussi > wrote: > > On Tue, 2012-10-23 at 20:56 -0700, Khem Raj wrote: > >> 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. > > > > This is because the crystalforest BSP is using ancient kernel > SRCREVs, > > corresponding to 3.4.9. > > > > Thanks for sending this patch , but I just pushed a fix for the > source > > of the problem by updating the SRCREVs instead. > > > > Tom > > > >> > >> Signed-off-by: Khem Raj > >> --- > >> .../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" > >> + > > > > > > ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [ANNOUNCEMENT] Yocto Project 1.3 "danny" Released
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The latest major release of the Yocto Project, 1.3 "danny", is now available for download at: * http://downloads.yoctoproject.org/releases/yocto/yocto-1.3/poky-danny-8.0.tar.bz2 * http://mirrors.kernel.org/yocto/yocto/yocto-1.3/poky-danny-8.0.tar.bz2 Improvements over the last 6 months include: - A new terminal based UI, knotty 2, that avoids burying any warnings and indicates parallelism - A relocatable SDK - Hob usability improvements - Upgraded gcc, eglibc, and kernel - Over 500 bugs fixed Thanks go out to everyone for all their hard work during this release! Sincerely, Beth Flanagan Yocto Project Build and Release - yocto-1.3 Errata - Release Name: poky-danny-8.0 Branch : danny Tag : 1.3 Hash: 27af23e65f63b41962a7cfddba9e9372d5212396 md5 : b61c39b96d02d98c07a826abdf79f06d Download Locations: http://downloads.yoctoproject.org/releases/yocto/yocto-1.3/poky-danny-8.0.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-1.3/poky-danny-8.0.tar.bz2 Release Name: eclipse-poky-danny-8.0 Branch : danny Tag : 1.3 Hash: cb8a0eff776d2cbd1b5f596a94dce825860574ab md5 : cea2b89dd7f8df32399199239a518e03 Download Locations: http://downloads.yoctoproject.org/releases/yocto/yocto-1.3/eclipse-poky-danny-8.0.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-1.3/eclipse-poky-danny-8.0.tar.bz2 Release Name: meta-qt3-danny-8.0 Branch : danny Tag : 1.3 Hash: c86fb1727ae09526c442ec29fffde3f010aa70eb md5 : 74e5d782e36a0a720f01f287d28f5984 Download Locations: http://downloads.yoctoproject.org/releases/yocto/yocto-1.3/meta-qt3-danny-8.0.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-1.3/meta-qt3-danny-8.0.tar.bz2 Release Name: yocto-autobuilder-danny-8.0 Branch : danny Tag : 1.3 Hash: 2fe295ebc00f9661e47702bf9dc392a3826f5469 md5 : 3719e4a7e4f5ce58bb14b77c966814e4 Download Locations: http://downloads.yoctoproject.org/releases/yocto/yocto-1.3/yocto-autobuilder-danny-8.0.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-1.3/yocto-autobuilder-danny-8.0.tar.bz2 - Features - - - Improved terminal UI, which makes it easy to see the tasks that are currently executing, and avoids burying any warnings that are printed - - Eliminated intermediate step when building cross compiler toolchain - - Relocatable SDK - - Large number of usability improvements in the Hob image building UI - - Upgraded eglibc to version 2.16 - - Upgraded gcc to version 4.7 - - upgraded Linux kernel version to 3.4.11 - - Added yocto-bsp script for automating the initial parts of creating a new BSP - - Python functions now consistently use four spaces for indentation - no more having to try to match the mix of tabs and spaces in your recipes - - Disabled sharing shared state between machines using different distros by default to avoid glibc version problems - - qemu-native can now be built on host systems without X11 (i.e. for console use only) - - Enabled python and perl scripting for perf as well as text-mode UI - - Added ability to produce a companion SDK together with an image - - Allow forced rebuilds of a recipe (new -C and improved -f options) - - Enabled EFI in grub installer - - Release of the J.A.R.V.I.S. reference layer at http://git.yoctoproject.org/cgit/cgit.cgi/meta-jarvis/ - - Mesa can now provide GLES accelerated graphics without X11 (through EGL) - - Added script for producing "bootcharts" from buildstats so you can see the timeline of the build - - Checksums for local files referred to in SRC_URI are now included in task signatures so that changing their contents causes the relevant tasks to be re-executed - - Extended bitbake-diffsigs to look up signature files from task and recipe name, and trace back recursively through dependent task changes - - Moved from module-init-tools to kmod - - Added create-recipe script to automate some of the parts of creating a brand new recipe - - Buildhistory improvements: better performance, track postinst/postrm scripts - - Added bin_package bbclass for recipes that package pre-built binaries - - Added doc-pkgs IMAGE_FEATURES feature to install all documentation - - Added class-* overrides - particularly useful for target/cross/crosssdk but works with all classes - - Reference hardware BSPs are now separate from Poky reference distro configuration - - nativesdk is now a prefix rather than a suffix, greatly simplifying packaging in nativesdk recipes - - Detections and warnings when files in the sysroot are potentially written to by multiple recipes - - Automatic launching of "screen" within terminal for devshell/patch resolution - - task-* recipes renamed to packagegroup-* and tidied up significantly - - Improved mirror handli
[yocto] [PATCH 0/1][meta-intel]meta-cedartrail: add WEBTITLE & Compliance information
From: Rahul Saxena The WEBTITLE will be used to publish the BSP on the Yocto Project Website. Also adding the Yocto Project Compliance information for the 1.3 release. Signed-off-by: Rahul Saxena -- The following changes since commit c19e9f51ebbdc603124994f3694fc79b0a83cf41: sugarbay: add WEBTITLE & Compliance information (2012-10-25 15:05:49 -0500) are available in the git repository at: git://git.pokylinux.org/meta-intel-contrib rsaxena-webtitle25Oct http://git.pokylinux.org/cgit.cgi/meta-intel-contrib/log/?h=rsaxena-webtitle25Oct Rahul Saxena (1): cedartrail: add WEBTITLE & Compliance information meta-cedartrail/README | 16 +--- meta-cedartrail/conf/machine/cedartrail-nopvr.conf |8 +--- meta-cedartrail/conf/machine/cedartrail.conf |8 +--- 3 files changed, 23 insertions(+), 9 deletions(-) -- 1.7.4.1 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH 1/1] cedartrail: add WEBTITLE & Compliance information
From: Rahul Saxena 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. Signed-off-by: Rahul Saxena --- meta-cedartrail/README | 16 +--- meta-cedartrail/conf/machine/cedartrail-nopvr.conf |8 +--- meta-cedartrail/conf/machine/cedartrail.conf |8 +--- 3 files changed, 23 insertions(+), 9 deletions(-) diff --git a/meta-cedartrail/README b/meta-cedartrail/README index e765e66..0d166b2 100755 --- a/meta-cedartrail/README +++ b/meta-cedartrail/README @@ -2,13 +2,23 @@ This README file contains information on building the meta-cedartrail BSP layer, and booting the images contained in the /binary directory. Please see the corresponding sections below for details. -The 'Cedar Trail' platform consists of the Cedarview (Intel® Atom™ -N2600, N2800 and D2550) processor, plus the Tiger Point -(Intel® NM10 Express) Chipset. +The 'Cedar Trail' platform consists of the Intel® Atom™ +N2600/N2800/D2550 processor, plus the Intel® NM10 Express Chispset +(Cedarview + Tiger Point). It also supports on-chip SGX545 graphics and media accelerator via the Cedar Trail Power VR (PVR) graphics driver. + +Compliance +== + +This BSP is compliant with the Yocto Project as per the requirements +listed here: + + http://www.yoctoproject.org/yocto-project-compatible-registration + + Dependencies diff --git a/meta-cedartrail/conf/machine/cedartrail-nopvr.conf b/meta-cedartrail/conf/machine/cedartrail-nopvr.conf index 767137e..7ccc6e1 100644 --- a/meta-cedartrail/conf/machine/cedartrail-nopvr.conf +++ b/meta-cedartrail/conf/machine/cedartrail-nopvr.conf @@ -1,8 +1,10 @@ #@TYPE: Machine -#@NAME: Cedartrail +#@NAME: cedartrail-nopvr -#@DESCRIPTION: Machine configuration for Cedartrail systems -# i.e. Cedarview processor + Tiger Point Chipset +#@WEBTITLE: Intel Atom N2600/N2800/D2550 (Formerly Cedarview) Processor with NM10 Chipset (Cedar Trail Platform) with Open Source VESA Graphics + +#@DESCRIPTION: Machine configuration for Cedar Trail systems +# i.e. N2600/N2800/D2550 + NM10 require conf/machine/include/tune-atom.inc require conf/machine/include/ia32-base.inc diff --git a/meta-cedartrail/conf/machine/cedartrail.conf b/meta-cedartrail/conf/machine/cedartrail.conf index 1463ae2..7efe584 100644 --- a/meta-cedartrail/conf/machine/cedartrail.conf +++ b/meta-cedartrail/conf/machine/cedartrail.conf @@ -1,8 +1,10 @@ #@TYPE: Machine -#@NAME: Cedartrail +#@NAME: cedartrail -#@DESCRIPTION: Machine configuration for Cedartrail systems -# i.e. Cedarview processor + Tiger Point Chipset +#@WEBTITLE: Intel Atom N2600/N2800/D2550 (Formerly Cedarview) Processor with NM10 Chipset (Cedar Trail Platform) and PVR Accelerated Graphics + +#@DESCRIPTION: Machine configuration for Cedar Trail systems +# i.e. N2600/N2800/D2550 + NM10 require conf/machine/include/tune-atom.inc require conf/machine/include/ia32-base.inc -- 1.7.4.1 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [Patch v3 7/7] crownbay: add more information in README
On Thu, 2012-10-25 at 10:49 -0700, nitin.a.kam...@intel.com wrote: > From: Nitin A Kamble > > Mention Little Bay & Shell Bay boards from the crownbay kit > in the readme. > > Signed-off-by: Nitin A Kamble > --- > meta-crownbay/README |2 ++ > 1 files changed, 2 insertions(+), 0 deletions(-) > > diff --git a/meta-crownbay/README b/meta-crownbay/README > index 1f164f4..525b2e6 100644 > --- a/meta-crownbay/README > +++ b/meta-crownbay/README > @@ -5,6 +5,8 @@ Please see the corresponding sections below for details. > The Crown Bay platform consists of the Intel Atom E6xx processor, > plus the Intel EG20T Platform Controller Hub (Tunnel Creek + Topcliff). > > +The crownbay kit consists of two boards, Shell Bay & Little Bay. > + This seems like a sort of random fact thrown in and doesn't explain what Shell Bay or Little Bay are (and shouldn't it be Crown Bay kit to match, instead of crownbay?). I guess I'd like to see the text explaining the hardware fit together as a whole and not just be a collection of facts about various aspects of the hardware listed out randomly. Tom > It also supports the E6xx embedded on-chip graphics via the Intel > Embedded Media and Graphics Driver (EMGD) 1.14 Driver. > ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
