Date   

[PATCH 1/5] virtex4: add u-boot image to rootfs

Adrian Alonso <aalonso@...>
 

* Add u-boot image to EXTRA_IMAGEDEPENDS
Trigger u-boot elf built and to be exported to hardware
project path (see xilinx-boot.bbclass).

Signed-off-by: Adrian Alonso <aalonso@secretlab.ca>
---
conf/machine/virtex4.conf | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)

diff --git a/conf/machine/virtex4.conf b/conf/machine/virtex4.conf
index f9643cb..114b4b7 100644
--- a/conf/machine/virtex4.conf
+++ b/conf/machine/virtex4.conf
@@ -13,6 +13,8 @@ require conf/machine/include/tune-ppc405.inc

PREFERRED_PROVIDER_virtual/kernel = "linux-xilinx"
PREFERRED_VERSION_u-boot_virtex4 = "u-boot-xilinx"
+# Add u-boot image
+EXTRA_IMAGEDEPENDS += "u-boot-xilinx"

KERNEL_IMAGETYPE = "uImage"

--
1.7.4


[PATCH 0/5][PULL] meta-xilinx powerpc bsp

Adrian Alonso <aalonso@...>
 

Several fixes for meta-xilinx powerpc bsp support

Pull URL: git://git.pokylinux.org/meta-xilinx.git
Branch: powerpc-support
Browse: http://git.pokylinux.org/cgit.cgi/meta-xilinx/log/?h=powerpc-support

Thanks,
Adrian Alonso <aalonso@secretlab.ca>
---


Adrian Alonso (5):
virtex4: add u-boot image to rootfs
virtex5: add u-boot image to rootfs
u-boot-xilinx: fix missing license definition
openssl: Fix files search path
linux-xilinx: update kernel version

conf/machine/virtex4.conf | 2 +
conf/machine/virtex5.conf | 2 +
recipes-bsp/uboot/u-boot-xilinx_git.bb | 6 +-
...enssl-linux-gnueabi-powerpc-configuration.patch | 0
.../openssl/openssl_0.9.8p.bbappend | 5 +-
recipes-kernel/linux/linux-xilinx_git.bb | 8 +-
recipes-kernel/linux/linux.inc | 95 ++++++++++++++++++++
7 files changed, 109 insertions(+), 9 deletions(-)
rename recipes-connectivity/openssl/{openssl-0.9.8p => files}/openssl-linux-gnueabi-powerpc-configuration.patch (100%)
create mode 100644 recipes-kernel/linux/linux.inc

--
1.7.4


[PATCH 1/1] kernel: remove explicit bash call in do_menuconfig

Bruce Ashfield <bruce.ashfield@...>
 

Fixes [BUGID #598]

The explicit addition of "bash" before "make menuconfig"
is clearing variables that are required for pseudo. The
end result is that menuconfig often fails silently with:

ERROR: ld.so: object 'libpseudo.so' from LD_PRELOAD cannot be preloaded: ignored.

Removing bash from the menuconfig SHELLCMDS variable fixes
the psudo problem.

Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
---
meta/classes/kernel.bbclass | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/meta/classes/kernel.bbclass b/meta/classes/kernel.bbclass
index 5d9b86a..a1b1354 100644
--- a/meta/classes/kernel.bbclass
+++ b/meta/classes/kernel.bbclass
@@ -202,7 +202,7 @@ do_menuconfig() {
export DBUS_SESSION_BUS_ADDRESS='${DBUS_SESSION_BUS_ADDRESS}'
export XAUTHORITY='${XAUTHORITY}'
export TERMWINDOWTITLE="${PN} Kernel Configuration"
- export SHELLCMDS="bash make menuconfig"
+ export SHELLCMDS="make menuconfig"
${TERMCMDRUN}
if [ $? -ne 0 ]; then
echo "Fatal: '${TERMCMD}' not found. Check TERMCMD variable."
--
1.7.0.4


[PATCH 0/1] kernel: fix menuconfig

Bruce Ashfield <bruce.ashfield@...>
 

Fixes [BUGID #598]

The explicit addition of "bash" before "make menuconfig"
is clearing variables that are required for pseudo. The
end result is that menuconfig often fails silently with:

ERROR: ld.so: object 'libpseudo.so' from LD_PRELOAD cannot be preloaded: ignored.

Removing bash from the menuconfig SHELLCMDS variable fixes
the pseudo problem.

As near as I can tell this is unversally safe (i.e. with
a different TERMCMD), but I'm willing to be correct and/or
replaced by a better patch. But this definitely fixed the
problem for me.

Pull URL: git://git.pokylinux.org/poky-contrib.git
Branch: zedd/kernel
Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel

Thanks,
Bruce Ashfield <bruce.ashfield@windriver.com>
---


Bruce Ashfield (1):
kernel: remove explicit bash call in do_menuconfig

meta/classes/kernel.bbclass | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)


Re: [poky] [PATCH 0/1] u-boot: don't install host mkimage on non-native builds

Saul Wold <saul.wold@...>
 

On 03/01/2011 09:49 AM, Bruce Ashfield wrote:
Richar/Saul,

This fixes BUG 777.

The u-boot package clearly uses HOST_CC and HOST_STRIP to build
mkimage, so installing it into ${D}${bindir} for anything but the
native mkimage is a bad idea. The native recipe has its own install
function, so we can safely delete the entire do_install from
u-boot.inc


Pull URL: git://git.pokylinux.org/poky-contrib.git
Branch: zedd/uboot
Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/uboot

Thanks,
Bruce Ashfield<bruce.ashfield@windriver.com>
---


Bruce Ashfield (1):
u-boot: remove do_install from u-boot.inc

meta/recipes-bsp/uboot/u-boot.inc | 5 -----
1 files changed, 0 insertions(+), 5 deletions(-)

_______________________________________________
poky mailing list
poky@yoctoproject.org
https://lists.yoctoproject.org/listinfo/poky
Pulled into Master and Bernard

Thanks
Sau!


[PATCH 1/1] u-boot: remove do_install from u-boot.inc

Bruce Ashfield <bruce.ashfield@...>
 

Fixes [BUGID #777]

The do_install rule in u-boot.inc was installing a host
tool into the target ${bindir}, which is subsequently
stripped with target strip during packaging, and the
obvious error ensues.

The native u-boot recipe has its own install rule, and
the machine specific u-boot doesn't require mkimage or
anything else in the do_install function. So we remove
it completely until it is needed again.

Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
---
meta/recipes-bsp/uboot/u-boot.inc | 5 -----
1 files changed, 0 insertions(+), 5 deletions(-)

diff --git a/meta/recipes-bsp/uboot/u-boot.inc b/meta/recipes-bsp/uboot/u-boot.inc
index 1457c04..d1cebee 100644
--- a/meta/recipes-bsp/uboot/u-boot.inc
+++ b/meta/recipes-bsp/uboot/u-boot.inc
@@ -31,8 +31,3 @@ do_deploy () {
ln -sf ${UBOOT_IMAGE} ${UBOOT_SYMLINK}
}
addtask deploy before do_build after do_compile
-
-do_install() {
- install -d ${D}${bindir}
- install -m 755 tools/mkimage ${D}${bindir}/
-}
--
1.7.0.4


[PATCH 0/1] u-boot: don't install host mkimage on non-native builds

Bruce Ashfield <bruce.ashfield@...>
 

Richar/Saul,

This fixes BUG 777.

The u-boot package clearly uses HOST_CC and HOST_STRIP to build
mkimage, so installing it into ${D}${bindir} for anything but the
native mkimage is a bad idea. The native recipe has its own install
function, so we can safely delete the entire do_install from
u-boot.inc


Pull URL: git://git.pokylinux.org/poky-contrib.git
Branch: zedd/uboot
Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/uboot

Thanks,
Bruce Ashfield <bruce.ashfield@windriver.com>
---


Bruce Ashfield (1):
u-boot: remove do_install from u-boot.inc

meta/recipes-bsp/uboot/u-boot.inc | 5 -----
1 files changed, 0 insertions(+), 5 deletions(-)


Notes from March 1st Yocto Release Tracking Meeting

Fleischer, Julie N <julie.n.fleischer@...>
 

Here are the notes from the March 1st Yocto Release Tracking meeting.
Thanks.
- Julie

Attendees: Dave, Saul, Julie, Mark, Darren, Beth, Jeff P., Jessica, Joshua, Jeff O., Tom, Richard

Agenda:
1) New Introductions (See https://lists.yoctoproject.org/pipermail/yocto/2011-February/001058.html for those already introduced)
Jeff Osier-Mixon (Jefro) - Yocto Community Manager

2) Review Yocto 1.0 Release Criteria
See https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.0_Release_Criteria for updates

Darren noted that Beagleboard XM will be enhanced with video for the demo (bugzilla report exists to add this). Some people at Wind River may help.

3) Opens/Risks
Mark gave some status on Open Embedded: As Richard noted, he will split Yocto into meta-yocto and OE Core. OE Core will be moved under the control of OE steering committee.

Note to developers: If you are updating software, you need to send patch to OE group if code is under OE Core (follow their rules). If you are updating software in meta-yocto, send it to the Yocto mailing list. If in doubt, code goes into Yocto meta-layer. Richard is assigning what is OE Core vs. meta-yocto right now.

We discussed that it would be useful to document submission requirements for Yocto. OE Core has a separate bugzilla, but they are shutting it down. Richard's vision is to use Yocto bugzilla for OE Core and meta-yocto issues to have one central repository.

-----------------------
Julie Fleischer
Open Source Technology Center
Intel Corporation


Yocto weekly bug trend charts -- WW09

Xu, Jiajun <jiajun.xu@...>
 

Hi all,
This is latest Yocto bug trend chart for WW09. With developers' hard work, we have open bug number decreased a lot (from 160 to 131). And from this week, we introduce a new chart "weighted defect density", which could show overall bug status of project.

Note:
How we calculate the data of "weighted defect density"?
We define a weight for each severity. And the sum of these weights for all open bugs are the data we record in chart.
The weight we use for each severity:
Critical: 10
Major: 7
Normal: 5
Minor: 3
Enhancement: 1

Best Regards,
Jiajun


Re: Status of release candidate: bernard-1.0rc1

Tom Zanussi <tom.zanussi@...>
 

On Mon, 2011-02-28 at 10:40 -0600, Tom Zanussi wrote:
On Mon, 2011-02-28 at 01:51 -0600, Tom Zanussi wrote:
On Sun, 2011-02-27 at 18:57 -0800, Elizabeth Flanagan wrote:
Summary
=======

This weekend, we generated a release candidate for bernard based on the bernard branch
of master at commit:
e08dc5aaaeba61e332caab4a3df5750df6b49ac1

and for BSPs based on the bernard branch of meta-intel at commit:
16f47f04a2baaeaf9b5a9b381fc7a3c7755d6ff6

Issues seen:
===========

Build Infrastructure issues:
----------------------------

- We had an issue with builder02 running out of disk space, so some of the build
copying was done post-build. This did not effect the build and was dealt with
manually after cleaning up the partition.

- There is an issue with how package-index is being run. I will need to sync up
with Jessica to verify how this should be incorporated into the build.

- The sanity tests on builder02 failed because builder02 was unable to resolve
"localhost". This has been corrected and the sanity tests re-run incrementally:
http://autobuilder.pokylinux.org:8010/builders/nightly-internal-sanity/builds/3

- The tarball generation buildstep is not branch aware. This will be fixed this week.
In the meantime it was run manually.


Sanity Test Issues:
----------------------------

- zypper-search failed on qemux-x86_64 on poky-image-lsb and poky-image-sato


Build Issues:
----------------------------

- BSPs did not complete successfully. There were some issue in the actual build mostly centering around:
- Failing to do_kernel_checkout
There are a couple problems with the jasperforest BSP. First, the
SRCREVs need updating, which I just submitted a patch for.

Even after that, though, there seems to be a problem with the kernel
repo the fetcher is getting. Even after clearing it out of git2, the
kernel repo that gets fetched into git2 and the build doesn't have the
jasperforest branch. A manual local clone of linux-yocto-2.6.37 does
contain the branch, though, and pointing the build to the local clone
finds the branch and builds(*) ok.

(*) until it gets to compiling perf - at that point it fails since the
branch doesn't yet have the perf compile fix moved from master.
The jasperforest branch just got updated, and I just submitted a SRCREV
update to use that, which takes care of the perf compile error.

I still see the problem with the the fetcher not getting the current
linux-yocto-2.6.37, so it looks like either a problem with the fetcher
or some stale cache lodged somewhere.
Yeah, it looks like stale cache.
http://autobuilder.yoctoproject.org/sources/git2_git.pokylinux.org.linux-yocto-2.6.37.tar.gz
doesn't have local branches for yocto/standard/common-pc-64/jasperforest
or yocto/standard/crownbay.

Tom


An interesting related thing is that I also see it with the 2.6.37
crownbay branch - a local clone works fine, but in the repo fetched into
git2 and the build the crownbay branch is missing, but in that case even
though the branch doesn't appear, its commits are actually in the repo
e.g. git log <commitid> shows the commits there.

Tom

Tom

- Unpack issues around svn://svn.o-hand.com/repos

- Beagleboard failed doing runstrip on uboot during do_populate_sysroot


Build statistic:
----------------------------

Using RP__'s machine as a baseline, our current build stats for poky-image-sato is:

real 109m52.400s
user 393m58.840s
sys 59m25.380s

Build statistics for nightly-external are available at:

http://autobuilder.pokylinux.org/nightly/20110226-1/buildstats/buildstats/

Open Defects:
----------------------------

As of right now we have:
76 total open defects targeted for 1.0

Critical: 0
High: 14
Medium: 53
Low: 7
Undetermined: 2


Thanks for all those who helped with this weekends RC generation, especially sgw and RP__

------------------
Elizabeth Flanagan
Yocto Project
Release Engineer
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: About repo

Ke, Liping <liping.ke@...>
 

Oh, the correct information is that RC2 will be ready @ this weekend.

Thanks& Regards,
criping

-----Original Message-----
From: yocto-bounces@yoctoproject.org [mailto:yocto-
bounces@yoctoproject.org] On Behalf Of Ke, Liping
Sent: Tuesday, March 01, 2011 10:03 AM
To: Zhang, Jessica
Cc: yocto@yoctoproject.org
Subject: [yocto] About repo

Hi, Jessica

JiaJun told me that RC2 image will soon come out (Hopefully on
Wednesday). So my question is that
When will the repo be ready (With RC2 image). Seems we need to have
some formal data for adt-installer testing. I want
to do a full test asap.

Thanks & regards,
criping
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Release Readiness Review for Bernard RC1

Elizabeth Flanagan <elizabeth.flanagan@...>
 

All,

This morning we had the Yocto RC1 Release Readiness Review. Notes follow.

Attendees: Beth, Dave, Jessica, Paul, Joshua, Julie, Saul, Jeff O, Richard

Feature Status:
* We are currently feature complete!

Status of the Release Candidate Build:
* Build infrastructure issues noted on weekend were mostly fixed.
* builder02 is fixed.
* package-index issue is being worked on by Beth and Jessica; may be related to the fact that building two meta-tool
chains at once.
* builder02 moved on Thursday and needed network config issues checked. Sanity tests failed b/c builder02 couldn't
resolve "localhost." This was corrected. Tests passed except for zipper (known issue).
* Tarball generation build step was made branch aware this morning. Still needs to be implemented this afternoon.
* Beth needs to nail down targets we are building. She sent out an email to verify we are building the right targets.

Sanity tests
* Zypper-search failure still exists.

BSP Issues:
* do-kernel_checkout is failing
* Beagleboard failed doing runstrip on uboot during do_populate_sysroot

Jiajun sent out a QA report to mailing list.
* BSP tests were blocked because builds were missing BSP images due to failures
* Open issues have been assigned.

Decision: RC1 is not the Gold release, but no data that shows we can't code freeze on March 18th.

RC2 will kick off Friday afternoon. Remember to match master and Bernard branch. Keep in mind master branch is
undergoing changes due to alignment with OE structure.

For this next cycle, the team priorities are:
1) Fix autobuilder failures.
2) Fix anything that fails in sanity tests <-- Those bugs are highest priority.
3) Fix bugs in bugzilla (in priority order).


About repo

Ke, Liping <liping.ke@...>
 

Hi, Jessica

JiaJun told me that RC2 image will soon come out (Hopefully on Wednesday). So my question is that
When will the repo be ready (With RC2 image). Seems we need to have some formal data for adt-installer testing. I want
to do a full test asap.

Thanks & regards,
criping


Yocto Release Tracking Meeting - Tuesday, March 1st 8am Pacific

Fleischer, Julie N <julie.n.fleischer@...>
 

Thanks to those that attended last week's Yocto Release Tracking Meeting! We'll have another this week. Details below.

Time/Date: Tuesday, March 01, 2011, 08:00 AM US Pacific Time
Dial in: 916-356-2663, Bridge: 1, Passcode: 5857771

Agenda:
1) New Introductions (See https://lists.yoctoproject.org/pipermail/yocto/2011-February/001058.html for those already introduced)
2) Review Yocto 1.0 Release Criteria: https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.0_Release_Criteria
3) Opens/Risks

-----------------------
Julie Fleischer
Open Source Technology Center
Intel Corporation


Re: [poky] [PATCH 0/1] linux-yocto: enable audio for qemux86 and qemux86-64

Bruce Ashfield <bruce.ashfield@...>
 

On 11-02-28 01:53 PM, Darren Hart wrote:
On 02/22/2011 06:49 PM, Bruce Ashfield wrote:
Richard/Saul,
Hi Bruce, I'm a little late to the party, but was wondering what your
thoughts are on the whole OSS thing. It seems we should be as consistent
as possible in our various Yocto Linux kernel images. Do we want to
support OSS? I recall several years ago that OSS had drivers that Alsa
did not and was needed for some boards - is that still the case? My
feeling is, if possible, I'd like to just have alsa in our kernels and
help reduce the raging redundancy in the audio API space.
alsa is the defacto / first choice for me.

That's partially why I chose to make this an
optional config block for this feature. That way
it is optional, and only applied to the specific qemu
images that we decided to add it for. All other kernels
and BSPs are unaffected.

If/when we get ALSA working for these qemu based machines,
we can easily drop this. But it looks like the only avenue
for the sound support immediately, so we slide it in
in as shallow a manner as possible.

Any and all patches to convert back to ALSA will be
happily merged! :)

Bruce


--
Darren


This Fixes [BUGID #488 #734]

As discussed, this enables the configuration options for qemu
audio for x86/x86-64 (limited to this for now). I did build and
boot testing (but couldn't directly test audio) for the impacted
qemu boards.

The commit message from the patch tells the rest of the story:

Enable audio for qemux86/qemux86-64 via the following kernel
configuration options.

CONFIG_SOUND_OSS_CORE=y
CONFIG_SOUND_OSS_CORE_PRECLAIM=ythe
CONFIG_SND_RAWMIDI=m
CONFIG_SND_SEQUENCER=y
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=y
CONFIG_SND_PCM_OSS=y
CONFIG_SND_PCM_OSS_PLUGINS=y
CONFIG_SND_SEQUENCER_OSS=y
CONFIG_SND_RAWMIDI_SEQ=m
CONFIG_SND_AC97_CODEC=m
CONFIG_SND_ENS1370=m
CONFIG_SND_INTEL8X0=m
CONFIG_AC97_BUS=m

The mechanism to trigger these options is in the form of an
optional kernel feature that is only appended for qemux86
and qemux86-64, but is contained within the kernel tree.

This allows several things:

- the options to be available/shared for all boards
- the options to be in tree
- to not add the options to every board, which unecessarily
bloats the default configuration.


Pull URL: git://git.pokylinux.org/poky-contrib.git
Branch: zedd/kernel
Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel

Thanks,
Bruce Ashfield<bruce.ashfield@windriver.com>
---


Bruce Ashfield (1):
linux-yocto: enable audio for selected qemu targets

meta/classes/kernel-yocto.bbclass | 4 +++-
.../conf/distro/include/poky-default-revisions.inc | 4 ++--
meta/recipes-kernel/linux/linux-yocto_git.bb | 6 ++++--
3 files changed, 9 insertions(+), 5 deletions(-)

_______________________________________________
poky mailing list
poky@yoctoproject.org
https://lists.yoctoproject.org/listinfo/poky


Re: [poky] [PATCH 0/1] linux-yocto: enable audio for qemux86 and qemux86-64

Richard Purdie
 

On Mon, 2011-02-28 at 10:53 -0800, Darren Hart wrote:
On 02/22/2011 06:49 PM, Bruce Ashfield wrote:
Richard/Saul,
Hi Bruce, I'm a little late to the party, but was wondering what your
thoughts are on the whole OSS thing. It seems we should be as consistent
as possible in our various Yocto Linux kernel images. Do we want to
support OSS? I recall several years ago that OSS had drivers that Alsa
did not and was needed for some boards - is that still the case? My
feeling is, if possible, I'd like to just have alsa in our kernels and
help reduce the raging redundancy in the audio API space.
I'd wondered about this too. In general I'd suggest Yocto's position is
to push for alsa drivers and see OSS as a legacy thing. As the author of
chunks of ALSA SoC code, I've put that into practise myself too! :)

Cheers,

Richard


Re: [poky] [PATCH 0/1] linux-yocto: enable audio for qemux86 and qemux86-64

Darren Hart <dvhart@...>
 

On 02/22/2011 06:49 PM, Bruce Ashfield wrote:
Richard/Saul,
Hi Bruce, I'm a little late to the party, but was wondering what your thoughts are on the whole OSS thing. It seems we should be as consistent as possible in our various Yocto Linux kernel images. Do we want to support OSS? I recall several years ago that OSS had drivers that Alsa did not and was needed for some boards - is that still the case? My feeling is, if possible, I'd like to just have alsa in our kernels and help reduce the raging redundancy in the audio API space.

--
Darren


This Fixes [BUGID #488 #734]

As discussed, this enables the configuration options for qemu
audio for x86/x86-64 (limited to this for now). I did build and
boot testing (but couldn't directly test audio) for the impacted
qemu boards.

The commit message from the patch tells the rest of the story:

Enable audio for qemux86/qemux86-64 via the following kernel
configuration options.

CONFIG_SOUND_OSS_CORE=y
CONFIG_SOUND_OSS_CORE_PRECLAIM=y
CONFIG_SND_RAWMIDI=m
CONFIG_SND_SEQUENCER=y
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=y
CONFIG_SND_PCM_OSS=y
CONFIG_SND_PCM_OSS_PLUGINS=y
CONFIG_SND_SEQUENCER_OSS=y
CONFIG_SND_RAWMIDI_SEQ=m
CONFIG_SND_AC97_CODEC=m
CONFIG_SND_ENS1370=m
CONFIG_SND_INTEL8X0=m
CONFIG_AC97_BUS=m

The mechanism to trigger these options is in the form of an
optional kernel feature that is only appended for qemux86
and qemux86-64, but is contained within the kernel tree.

This allows several things:

- the options to be available/shared for all boards
- the options to be in tree
- to not add the options to every board, which unecessarily
bloats the default configuration.


Pull URL: git://git.pokylinux.org/poky-contrib.git
Branch: zedd/kernel
Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel

Thanks,
Bruce Ashfield<bruce.ashfield@windriver.com>
---


Bruce Ashfield (1):
linux-yocto: enable audio for selected qemu targets

meta/classes/kernel-yocto.bbclass | 4 +++-
.../conf/distro/include/poky-default-revisions.inc | 4 ++--
meta/recipes-kernel/linux/linux-yocto_git.bb | 6 ++++--
3 files changed, 9 insertions(+), 5 deletions(-)

_______________________________________________
poky mailing list
poky@yoctoproject.org
https://lists.yoctoproject.org/listinfo/poky

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


Re: Status of release candidate: bernard-1.0rc1

Tom Zanussi <tom.zanussi@...>
 

On Mon, 2011-02-28 at 01:51 -0600, Tom Zanussi wrote:
On Sun, 2011-02-27 at 18:57 -0800, Elizabeth Flanagan wrote:
Summary
=======

This weekend, we generated a release candidate for bernard based on the bernard branch
of master at commit:
e08dc5aaaeba61e332caab4a3df5750df6b49ac1

and for BSPs based on the bernard branch of meta-intel at commit:
16f47f04a2baaeaf9b5a9b381fc7a3c7755d6ff6

Issues seen:
===========

Build Infrastructure issues:
----------------------------

- We had an issue with builder02 running out of disk space, so some of the build
copying was done post-build. This did not effect the build and was dealt with
manually after cleaning up the partition.

- There is an issue with how package-index is being run. I will need to sync up
with Jessica to verify how this should be incorporated into the build.

- The sanity tests on builder02 failed because builder02 was unable to resolve
"localhost". This has been corrected and the sanity tests re-run incrementally:
http://autobuilder.pokylinux.org:8010/builders/nightly-internal-sanity/builds/3

- The tarball generation buildstep is not branch aware. This will be fixed this week.
In the meantime it was run manually.


Sanity Test Issues:
----------------------------

- zypper-search failed on qemux-x86_64 on poky-image-lsb and poky-image-sato


Build Issues:
----------------------------

- BSPs did not complete successfully. There were some issue in the actual build mostly centering around:
- Failing to do_kernel_checkout
There are a couple problems with the jasperforest BSP. First, the
SRCREVs need updating, which I just submitted a patch for.

Even after that, though, there seems to be a problem with the kernel
repo the fetcher is getting. Even after clearing it out of git2, the
kernel repo that gets fetched into git2 and the build doesn't have the
jasperforest branch. A manual local clone of linux-yocto-2.6.37 does
contain the branch, though, and pointing the build to the local clone
finds the branch and builds(*) ok.

(*) until it gets to compiling perf - at that point it fails since the
branch doesn't yet have the perf compile fix moved from master.
The jasperforest branch just got updated, and I just submitted a SRCREV
update to use that, which takes care of the perf compile error.

I still see the problem with the the fetcher not getting the current
linux-yocto-2.6.37, so it looks like either a problem with the fetcher
or some stale cache lodged somewhere.

An interesting related thing is that I also see it with the 2.6.37
crownbay branch - a local clone works fine, but in the repo fetched into
git2 and the build the crownbay branch is missing, but in that case even
though the branch doesn't appear, its commits are actually in the repo
e.g. git log <commitid> shows the commits there.

Tom

Tom

- Unpack issues around svn://svn.o-hand.com/repos

- Beagleboard failed doing runstrip on uboot during do_populate_sysroot


Build statistic:
----------------------------

Using RP__'s machine as a baseline, our current build stats for poky-image-sato is:

real 109m52.400s
user 393m58.840s
sys 59m25.380s

Build statistics for nightly-external are available at:

http://autobuilder.pokylinux.org/nightly/20110226-1/buildstats/buildstats/

Open Defects:
----------------------------

As of right now we have:
76 total open defects targeted for 1.0

Critical: 0
High: 14
Medium: 53
Low: 7
Undetermined: 2


Thanks for all those who helped with this weekends RC generation, especially sgw and RP__

------------------
Elizabeth Flanagan
Yocto Project
Release Engineer
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


OE-Core - What this means for Yocto/Poky and what we need to do

Richard Purdie
 

Hi,

As most have gathered, there are changes afoot in the OE world and we
want to start increasing collaboration between Yocto and OE through the
creation of an OE-Core repository which both projects share.

This was going to be too much change for inclusion for the 1.0 release
but now that has branched we need to start working on this. I appreciate
that people have a number of different priorities but I'd ask that
people do read this email, take time to understand these changes and
bare with the inevitable disruption this change is going to cause.
Obviously we'll try and keep disruption to a minimum.

The implication for Yocto/Poky is that what is currently the meta
directory in the Poky repo is going to get split into two pieces. One
will be a mirror of the OE-Core repo (meta), the other will be yocto
specific pieces (meta-yocto). Each of these will be a layer.

For anything within the OE-Core directory, the patches need to be
submitted on the OE-Core mailing list. Patches to the other components
need to be separate and on the Poky list as things are today. I expect
the distro team to subscribe to the OE-Core list and participate there
on for discussions on core components:

http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

meta-yocto patches and discussion should continue on the poky list as
today.

I am prepared for now to help out getting user submitted patches for
Yocto/Poky, split up and submitted to OE-Core as needed. Ultimately, I'm
hoping we can enhance the tooling to understand layers and be able to
put send patches to the right places but we don't have such tools yet
and its a chicken and egg problem.

I also want to change the Poky repo so all the pieces contained within
are mirror copies of the appropriate upstreams. I've been working on
resolving the delta with upstream bitbake and for some components (docs,
meta-yocto, yocto-glue) we'll need to create them.

I'm going to start making these changes on the master branch as we're
under a lot of pressure from OE to start doing this *now*. I want to be
clear these changes are not destined for the 1.0 release.

Cheers,

Richard


Re: Status of release candidate: bernard-1.0rc1

Tom Zanussi <tom.zanussi@...>
 

On Sun, 2011-02-27 at 18:57 -0800, Elizabeth Flanagan wrote:
Summary
=======

This weekend, we generated a release candidate for bernard based on the bernard branch
of master at commit:
e08dc5aaaeba61e332caab4a3df5750df6b49ac1

and for BSPs based on the bernard branch of meta-intel at commit:
16f47f04a2baaeaf9b5a9b381fc7a3c7755d6ff6

Issues seen:
===========

Build Infrastructure issues:
----------------------------

- We had an issue with builder02 running out of disk space, so some of the build
copying was done post-build. This did not effect the build and was dealt with
manually after cleaning up the partition.

- There is an issue with how package-index is being run. I will need to sync up
with Jessica to verify how this should be incorporated into the build.

- The sanity tests on builder02 failed because builder02 was unable to resolve
"localhost". This has been corrected and the sanity tests re-run incrementally:
http://autobuilder.pokylinux.org:8010/builders/nightly-internal-sanity/builds/3

- The tarball generation buildstep is not branch aware. This will be fixed this week.
In the meantime it was run manually.


Sanity Test Issues:
----------------------------

- zypper-search failed on qemux-x86_64 on poky-image-lsb and poky-image-sato


Build Issues:
----------------------------

- BSPs did not complete successfully. There were some issue in the actual build mostly centering around:
- Failing to do_kernel_checkout
There are a couple problems with the jasperforest BSP. First, the
SRCREVs need updating, which I just submitted a patch for.

Even after that, though, there seems to be a problem with the kernel
repo the fetcher is getting. Even after clearing it out of git2, the
kernel repo that gets fetched into git2 and the build doesn't have the
jasperforest branch. A manual local clone of linux-yocto-2.6.37 does
contain the branch, though, and pointing the build to the local clone
finds the branch and builds(*) ok.

(*) until it gets to compiling perf - at that point it fails since the
branch doesn't yet have the perf compile fix moved from master.

Tom

- Unpack issues around svn://svn.o-hand.com/repos

- Beagleboard failed doing runstrip on uboot during do_populate_sysroot


Build statistic:
----------------------------

Using RP__'s machine as a baseline, our current build stats for poky-image-sato is:

real 109m52.400s
user 393m58.840s
sys 59m25.380s

Build statistics for nightly-external are available at:

http://autobuilder.pokylinux.org/nightly/20110226-1/buildstats/buildstats/

Open Defects:
----------------------------

As of right now we have:
76 total open defects targeted for 1.0

Critical: 0
High: 14
Medium: 53
Low: 7
Undetermined: 2


Thanks for all those who helped with this weekends RC generation, especially sgw and RP__

------------------
Elizabeth Flanagan
Yocto Project
Release Engineer
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto