On 07/26/2011 12:47 PM, Gary Thomas wrote:

On 2011-07-15 09:30, Jeff Mitchell wrote:

Darren Hart suggested I send this to the list...

Attached is a picture of my screen running Terminal. This is on a BeagleBoard xM rev C connected via its HDMI out to a DVI adapter and then into a Dell UltraSharp monitor. Angstrom
doesn't display these problems, so the setup should be fine.

I'm not quite sure what is causing this. The resolution is also fairly low, and I haven't had any success using boot parameters (either the older video=omapfb:mode variant or the
newer DSS2 omapfb.mode variant).

Did you ever find out what is causing this?

No, but I'll be testing out a new build soon -- haven't been able to for a bit.

When you say that it works on one system (Poky?) vs another (Angstrom?)
are they both running the same version of U-Boot? I'm seeing this same
behaviour on one of my boards, but only when I run U-Boot from 2011.06

Yes -- Yocto/Poky/Sato vs. Angstrom. I doubt they're running the same version of U-Boot, but I don't know the version numbers offhand.

BTW - why did you send your original query to the Poky list?

Because Darren suggested that I do so, to get various eyes on it :-)

Thanks,
jeff

On 2011-07-15 09:30, Jeff Mitchell wrote:

Darren Hart suggested I send this to the list...

Attached is a picture of my screen running Terminal. This is on a BeagleBoard xM rev C connected via its HDMI out to a DVI adapter and then into a Dell UltraSharp monitor. Angstrom
doesn't display these problems, so the setup should be fine.

I'm not quite sure what is causing this. The resolution is also fairly low, and I haven't had any success using boot parameters (either the older video=omapfb:mode variant or the
newer DSS2 omapfb.mode variant).

Did you ever find out what is causing this?

When you say that it works on one system (Poky?) vs another (Angstrom?)
are they both running the same version of U-Boot? I'm seeing this same
behaviour on one of my boards, but only when I run U-Boot from 2011.06

BTW - why did you send your original query to the Poky list?

--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------

From: Tom Zanussi <tom.zanussi@...>

Switch sugarbay to the 3.0 kernel, lock it down, and update kernel
SRCREVs.

Signed-off-by: Tom Zanussi <tom.zanussi@...>
---
meta-sugarbay/conf/machine/sugarbay.conf | 1 +
.../recipes-kernel/linux/linux-yocto_3.0.bbappend | 7 +++++++
2 files changed, 8 insertions(+), 0 deletions(-)
create mode 100644 meta-sugarbay/recipes-kernel/linux/linux-yocto_3.0.bbappend

diff --git a/meta-sugarbay/conf/machine/sugarbay.conf b/meta-sugarbay/conf/machine/sugarbay.conf
index ebc6dbc..9450d97 100644
--- a/meta-sugarbay/conf/machine/sugarbay.conf
+++ b/meta-sugarbay/conf/machine/sugarbay.conf
@@ -15,6 +15,7 @@ MACHINE_FEATURES = "kernel26 screen keyboard pci usbhost ext2 ext3 x86 \
KERNEL_IMAGETYPE = "bzImage"

PREFERRED_PROVIDER_virtual/kernel = "linux-yocto"
+PREFERRED_VERSION_linux-yocto = "3.0+git%"
PREFERRED_PROVIDER_linux-libc-headers ?= "linux-libc-headers-yocto"

PREFERRED_PROVIDER_virtual/libx11 ?= "libx11-trim"
diff --git a/meta-sugarbay/recipes-kernel/linux/linux-yocto_3.0.bbappend b/meta-sugarbay/recipes-kernel/linux/linux-yocto_3.0.bbappend
new file mode 100644
index 0000000..57420f2
--- /dev/null
+++ b/meta-sugarbay/recipes-kernel/linux/linux-yocto_3.0.bbappend
@@ -0,0 +1,7 @@
+FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
+
+COMPATIBLE_MACHINE_sugarbay = "sugarbay"
+KMACHINE_sugarbay = "yocto/standard/common-pc-64/sugarbay"
+
+SRCREV_machine_pn-linux-yocto_sugarbay ?= "3216e7d5c3cada16161481826cdb39c930457587"
+SRCREV_meta_pn-linux-yocto_sugarbay ?= "9010d1cbef2633dac7e559a7705c326b7601dd4c"
--
1.7.0.4

From: Tom Zanussi <tom.zanussi@...>

Built and booted into sato - basic testing shows everything
works as expected.

The following changes since commit 96c247dad88b9fc0159b2a929216876d9fbb06dc:
Tom Zanussi (1):
meta-emenlow: fix glx bug

are available in the git repository at:

git://git.yoctoproject.org/meta-intel.git tzanussi/sugarbay-linux-3.0-switchover
http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/log/?h=tzanussi/sugarbay-linux-3.0-switchover

Tom Zanussi (2):
meta-sugarbay: switch to linux-yocto 3.0 kernel

meta-jasperforest/conf/machine/jasperforest.conf | 1 +
.../recipes-kernel/linux/linux-yocto_3.0.bbappend | 8 ++++++++
meta-sugarbay/conf/machine/sugarbay.conf | 1 +
.../recipes-kernel/linux/linux-yocto_3.0.bbappend | 7 +++++++
4 files changed, 17 insertions(+), 0 deletions(-)
create mode 100644 meta-jasperforest/recipes-kernel/linux/linux-yocto_3.0.bbappend
create mode 100644 meta-sugarbay/recipes-kernel/linux/linux-yocto_3.0.bbappend

Attendees:
Saul, Tom, Paul, Jessica, Rahul, Koen, Joshua, Mark, Denys, Richard, Bruce, Song
 
Action Item List:
------------------------------------------------------------------------------------------------------------------------------------
* The team to review ALL bugs each owns and do some estimation. Please put the estimation on the white board by next Thursday (8/4/11)
------------------------------------------------------------------------------------------------------------------------------------
* Saul: talk to Jianjun, QA should work with developers to make sure we can cover more distro testing (informal) before major release. Joshua and Darren volunteers for some of these testing.
* Beth/Darren/ScottR: document the central location in the release, and put any doc changes in the location after release.
* Song will follow up with Tracey to make sure marketing planning happens between milestones so that there is no disruption to the development schedule.
  
Agenda:
 
- opens collection - 5 min (Song)
- Review M3 status and open issues - 15 min (team)
------------------------------------------------------
* Feature cut-off time is mid-day 27th, US pacific time. All committed features should be in by then and M3 will branch out.
------------------------------------------------------
* Beth's autobuilder infrastructure will move to M4 due to hardware issues. No impact to Yocto 1.1 release.
* Multi-lib plan: merge multi-lib tree with M3 branch at the point when M3 branches out.
* Mark needs to get some licensing statement for some of the code. Targeting today to get it done.
* HOB for M3 is on track.
* Demos: No resources allocated for demo during M3. Song will follow up with Tracey.
* Overall, M3 is on track to get us to point of the feature complete.
- M4
* The focus of M4 is bug fixing for 1.1. After M3 Sprint A, the team should review ALL the bugs they own and estimate the effort, then put the estimation on the white board. We will use that information to do M4 planning next Thursday (8/4/11)
- Action item review
* Team: please take a look at the post 1.1 items on the wiki page and let Song know if there is any comment or concerns. (Done, CCB approved)
* Saul: talk to Jianjun, QA should work with developers to make sure we can cover more distro testing (informal) before major release. Joshua and Darren volunteers for some of these testing.
* Beth/Darren/ScottR: document the central location in the release, and put any doc changes in the location after release.
* Song to setup go/no-go meeting next Monday to decide on the M2 release. (Done)

All,

We are pleased to announce the second milestone of the coming
October release of Yocto 1.1. This milestone release is available at:

http://mirrors.kernel.org/yocto/poky/poky-bernard-5.1.0-m2.tar.bz2

Additional tarballs for the meta-intel, meta-qt3 and eclipse plugin are
available at:

http://mirrors.kernel.org/yocto/poky/meta-intel-bernard-5.1.0-m2.tar.bz2
http://mirrors.kernel.org/yocto/poky/meta-qt3-bernard-5.1.0-m2.tar.bz2
http://mirrors.kernel.org/yocto/poky/eclipse-poky-bernard-5.1.0-m2.tar.bz2

Thanks you everyone for all the hard work.

------------------
Elizabeth Flanagan
Yocto Project
Release Engineer

--------------------
Bernard 5.1.0-m2 Errata
--------------------
Release name: poky-bernard-5.1.0-m2
Repo: git://git.yoctoproject.org/poky.git
Branch: 1.1_M2
Tag: 1.1_M2.final
Hash: a62982ffb6b35acc70bb30a429fc854cf9a8873f
Download locations:
http://autobuilder.yoctoproject.org/downloads/poky/poky-bernard-5.1.0-m2.tar.bz2
http://mirrors.kernel.org/yocto/poky/poky-bernard-5.1.0-m2.tar.bz2

--------------------
Features
--------------------
1. Layer tooling
2. Basic functions of the HOB.
3. Share gcc work directory.
4. Cache redesign and reimplementation.
5. Some performance improvement measures such as splitting libc,
removing perl-native from bld dep.
6. Beagle board XM update.
7. Tracing: Add Systemtap support for user space tracing
8. 3G support

--------------------
Known Issues
--------------------
766 [mpc8315e-rdb] USB does not work on mpc8315e-rdb
638 need documentation for sstate
689 BB_ENV_EXTRAWHITE does not respect CCACHE_DIR


--------------------
Bugs Fixed
--------------------
1208 busybox powertop mess up our eclipse plugin
1218 [HOB] package selection logic inconsistent after select/deselect
several times
1219 [HOB] lots of bug traces when launching hob
1237 [sugarbay] Inconsistency detected by ld.so: dl-deps.c: 622:
_dl_map_object_deps: Assertion `nlist > 1' failed!
1215 Can't build minimal image with IMAGE_LINGUAS set
773 [routerstationpro] USB does not work on routerstationpro
1038 Recipe alsa-tools does not build
1209 eglibc 2.13 r5: cannot stat localedef when
ENABLE_BINARY_LOCALE_GENERATION = "0"
1072 machine-specific xorg.confs not being picked up
1037 web browser can't handle https pages
1040 Recipe clutter-box2d does not build
1107 Open or add person in contacts may segfault on blacksand
1025 Release of documentation needs to be rethought.
1195 [mips toolchain] cvs configure fail with no cvs_cv_func_printf_ptr set
868 GUI Progress bar sits at 0% until done when using GUI's with none server
1132 libxml-simple-perl do_configure Failed if being built after libxml-sax-perl
891 clutter is not included in the poky-image-sato-sdk
896 [N450] poky-image-clutter build failure
963 kernel tarballs being served up by autobuilder contain
missing/corrupted branches
1085 fetcher2: try mirror after failing checksum from upstream
1194 support DSF debugger
1213 btrfs-tools parallel make failure
1180 bitbake -c listtasks doesn't print to the console
1091 Adding .bbappend should invalidate cache
1140 Can't build update-rc.d if BB_NO_NETWORK=1
1182 poky-init-build-env user feedback need updated
1148 libxml2.so.2 unknown version errors on bootup
1197 Refresh x-load to include 2efa178acd56d83c86210b5934895cfb9ea62125
1198 refresh u-boot to include a 2011.06 recipe
1009 Building world fails with errors of conflicting providers of ssh
1128 Meaningless error message when python v3 is the only python available
904 LSB 4.1:Printing absent cups, foomatic and gs
1090 LSB4.1: lsb graphic library can't be installed into lsb-image
1118 LSB 4.1: Param_Value error
1196 LSB 4.1: Compilation error from startup-notification_0.12.bb
1136 do_menuconfig for linux-yocto needs ${B} exists
933 Add a build profile which checks the things which may need a proxy
790 Layer dependency support
1142 git fetcher error when wrong protocol is specified is not helpful
1163 gcc-cross-canadian needs set to TRANSLATED_TARGET_ARCH
1173 toolchain build failed with 20110613 build on autobuilder
1156 BSP formfactors not being picked up
1168 qt4-tools-nativesdk does not build
1186 Recent bitbake change results in git fetch during parse
1170 login.defs file shipped with base-passwd causes runtime warnings
1020 LSB4.1: LSB test suite need libQtOpenGL.so for hardware ppc, x86 and x86-64

From: Tom Zanussi <tom.zanussi@...>

Switch jasperforest to the 3.0 kernel, lock it down, and update kernel
SRCREVs.

Signed-off-by: Tom Zanussi <tom.zanussi@...>
---
meta-jasperforest/conf/machine/jasperforest.conf | 1 +
.../recipes-kernel/linux/linux-yocto_3.0.bbappend | 8 ++++++++
2 files changed, 9 insertions(+), 0 deletions(-)
create mode 100644 meta-jasperforest/recipes-kernel/linux/linux-yocto_3.0.bbappend

diff --git a/meta-jasperforest/conf/machine/jasperforest.conf b/meta-jasperforest/conf/machine/jasperforest.conf
index 3f8591a..1d875b5 100644
--- a/meta-jasperforest/conf/machine/jasperforest.conf
+++ b/meta-jasperforest/conf/machine/jasperforest.conf
@@ -15,6 +15,7 @@ MACHINE_FEATURES = "kernel26 screen keyboard pci usbhost ext2 ext3 x86 \
KERNEL_IMAGETYPE = "bzImage"

PREFERRED_PROVIDER_virtual/kernel = "linux-yocto"
+PREFERRED_VERSION_linux-yocto = "3.0+git%"
PREFERRED_PROVIDER_linux-libc-headers ?= "linux-libc-headers-yocto"

PREFERRED_PROVIDER_virtual/libx11 ?= "libx11-trim"
diff --git a/meta-jasperforest/recipes-kernel/linux/linux-yocto_3.0.bbappend b/meta-jasperforest/recipes-kernel/linux/linux-yocto_3.0.bbappend
new file mode 100644
index 0000000..52f0a6e
--- /dev/null
+++ b/meta-jasperforest/recipes-kernel/linux/linux-yocto_3.0.bbappend
@@ -0,0 +1,8 @@
+FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
+
+COMPATIBLE_MACHINE_jasperforest = "jasperforest"
+
+KMACHINE_jasperforest = "yocto/standard/common-pc-64/jasperforest"
+
+SRCREV_machine_pn-linux-yocto_jasperforest ?= "3216e7d5c3cada16161481826cdb39c930457587"
+SRCREV_meta_pn-linux-yocto_jasperforest ?= "9010d1cbef2633dac7e559a7705c326b7601dd4c"
--
1.7.0.4

From: Tom Zanussi <tom.zanussi@...>

Built and booted into sato - basic testing shows everything
works as expected.

The following changes since commit 96c247dad88b9fc0159b2a929216876d9fbb06dc:
Tom Zanussi (1):
meta-emenlow: fix glx bug

are available in the git repository at:

git://git.yoctoproject.org/meta-intel.git tzanussi/jasperforest-linux-3.0-switchover
http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/log/?h=tzanussi/jasperforest-linux-3.0-switchover

Tom Zanussi (1):
meta-jasperforeset: switch to linux-yocto 3.0 kernel

meta-jasperforest/conf/machine/jasperforest.conf | 1 +
.../recipes-kernel/linux/linux-yocto_3.0.bbappend | 8 ++++++++
2 files changed, 9 insertions(+), 0 deletions(-)
create mode 100644 meta-jasperforest/recipes-kernel/linux/linux-yocto_3.0.bbappend

Folks,

There is a build available from the autobuilder

http://autobuilder.yoctoproject.org/nightly/20110723-2/

There were a couple of failures in the LSB-QT3 Builds that are being looked into. The failures occur in differnt packages for qemuarm and qemux86 LSB builds. I am trying to determine this is related to some shared state issues I have been seeing.

The meta-toolchain builds are running again due to an autobuilder related issue.

Please begin weekly testing with what is available.

Thanks
--
Sau!

Saul Wold
Yocto Component Wrangler @ Intel
Yocto Project / Poky Build System

Hi all,
RC3 is built out last week and QA is testing it. The new-submit vs. fixed bug is 26 vs. 24 for last week. The open bug number increased to 185 (No enhancement bugs counted). WDD number increased from 933 to 943. Several Critical and Major bugs are fixed in RC3. Meanwhile, a lot of hob bugs are submitted. Bug status of WW30 could be found on https://wiki.pokylinux.org/wiki/Yocto_Bug_Trend.

Best Regards,
Jiajun

On Monday July 25th from 10 to 11am PDT we will move git.yoctoproject.org and git.pokylinux.org to new hardware hosted at the OSU Open Source Lab. Read only access will be available during the entire process. Pushes will be refused until the transition is complete. If your push is accepted then the process has completed for you. Due to the nature of DNS propagation service will not become available to all users simultaneously.

Michael Halstead
Intel OTC Yocto

this is something i noticed a couple days back -- trying to "bitbake
-c fetchall world" failed on the sat-solver package:


NOTE: Running task 478 of 1358 (ID: 486,
/home/rpjday/yocto/poky.git/meta/recipes-extended/sat-solver/sat-solver_git.bb,
do_fetch)
NOTE: package
sat-solver-0.0-git1+0a7378d5f482f477a01cf1690d76871ab8bdcc32-r11: task
do_fetch: Started
ERROR: Function 'Fetcher failure for URL:
'git://gitorious.org/opensuse/sat-solver.git;protocol=git'. Unable to
fetch URL git://gitorious.org/opensuse/sat-solver.git;protocol=git
from any source.' failed
ERROR: Logfile of failure stored in:
/home/rpjday/yocto/build/tmp/work/qemux86-poky-linux/sat-solver-0.0-git1+0a7378d5f482f477a01cf1690d76871ab8bdcc32-r11/temp/log.do_fetch.10656
Log data follows:
| fatal: Not a git repository (or any of the parent directories): .git
| fatal: Not a git repository (or any of the parent directories):
.git
| ERROR: Function 'Fetcher failure for URL:
'git://gitorious.org/opensuse/sat-solver.git;protocol=git'. Unable to
fetch URL git://gitorious.org/opensuse/sat-solver.git;protocol=git
from any source.' failed
|
NOTE: package
sat-solver-0.0-git1+0a7378d5f482f477a01cf1690d76871ab8bdcc32-r11: task
do_fetch: Failed


rday

--

========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================

On 07/22/2011 10:13 AM, Saul Wold wrote:

On 07/14/2011 09:56 PM, Kumar Gala wrote:

The MPC8315E has a e300c3 core in it with 'classic' or normal PPC
floating point.

'SPE' floating point is what exists on the e500v2 core.

Signed-off-by: Kumar Gala<galak@...>
---
meta-yocto/conf/machine/mpc8315e-rdb.conf | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/meta-yocto/conf/machine/mpc8315e-rdb.conf b/meta-yocto/conf/machine/mpc8315e-rdb.conf
index 095d113..3f946a0 100644
--- a/meta-yocto/conf/machine/mpc8315e-rdb.conf
+++ b/meta-yocto/conf/machine/mpc8315e-rdb.conf
@@ -2,7 +2,7 @@
#@DESCRIPTION: Machine configuration for running

TARGET_ARCH = "powerpc"
-TARGET_FPU = "spe"
+TARGET_FPU = "hard"

This doesn't match the documentation:
./meta/conf/documentation.conf:TARGET_FPU[doc] = "Floating point option (mostly for FPU-less systems), can be 'soft' or empty
The file
meta/classes/icecc.bbclass
seems to be the only place where TARGET_FPU="hard" means anything.

--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------

On 07/14/2011 09:56 PM, Kumar Gala wrote:

The MPC8315E has a e300c3 core in it with 'classic' or normal PPC
floating point.

'SPE' floating point is what exists on the e500v2 core.

Signed-off-by: Kumar Gala<galak@...>
---
meta-yocto/conf/machine/mpc8315e-rdb.conf | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/meta-yocto/conf/machine/mpc8315e-rdb.conf b/meta-yocto/conf/machine/mpc8315e-rdb.conf
index 095d113..3f946a0 100644
--- a/meta-yocto/conf/machine/mpc8315e-rdb.conf
+++ b/meta-yocto/conf/machine/mpc8315e-rdb.conf
@@ -2,7 +2,7 @@
#@DESCRIPTION: Machine configuration for running

TARGET_ARCH = "powerpc"
-TARGET_FPU = "spe"
+TARGET_FPU = "hard"

require conf/machine/include/tune-ppc603e.inc

Pulled into Yocto/Master

Thanks
Sau!

On Jul 14, 2011, at 11:56 PM, Kumar Gala wrote:

The MPC8315E has a e300c3 core in it with 'classic' or normal PPC
floating point.

'SPE' floating point is what exists on the e500v2 core.

Signed-off-by: Kumar Gala <galak@...>
---
meta-yocto/conf/machine/mpc8315e-rdb.conf | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)

Richard,

ping. Bruce has ack'd this.

https://lists.yoctoproject.org/pipermail/yocto/2011-July/001915.html

- k

diff --git a/meta-yocto/conf/machine/mpc8315e-rdb.conf b/meta-yocto/conf/machine/mpc8315e-rdb.conf
index 095d113..3f946a0 100644
--- a/meta-yocto/conf/machine/mpc8315e-rdb.conf
+++ b/meta-yocto/conf/machine/mpc8315e-rdb.conf
@@ -2,7 +2,7 @@
#@DESCRIPTION: Machine configuration for running

TARGET_ARCH = "powerpc"
-TARGET_FPU = "spe"
+TARGET_FPU = "hard"

require conf/machine/include/tune-ppc603e.inc

--
1.7.3.4

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

My target machine is atom-pc and my build host is Fedora 13 in a
VirtualBox machine.

I've not seen this before. You could run
"file /home/ahaupt/yocto-git/build/tmp/sysroots/atom-pc/usr/lib/libgdbm.so.3.0.0" and check that its of the correct architecture since the invalid instruction is a weird error to see. I'm not 100% sure its that file its complaining about the instruction from though.

this is the output of the file command:
libgdbm.so.3.0.0: ELF 32-bit LSB shared object, Intel 80386, version 1
(SYSV), dynamically linked, not stripped

Sounds correct...

Does it do this every build, erroring in the same way? I know we did see
some emulation corruption type issues with virtualbox in the past
although they've not been reported for a while. It might be worth
starting a new build of "bitbake python" and see if the error is
reproducible too...

It happens reproducible when i do a "bitbake python".

Is this on a fresh clean build directory?

I did a fresh build in a new clean directory now and it fails too. The
error log (attached) is a bit different though.

What i did:

- source poky-init-build-env build python
- edit conf/local.conf to set
BB_NUMBER_THREADS = "2"
PARALLEL_MAKE = "-j 2"
MACHINE ??= "atom-pc"
- source poky-init-build-env build python, again (not sure if this is needed)
- bitbake python

You could also try "bitbake -c cleansstate python gdbm" on your existing
build directory and retry "bitbake python" to see if its reproducible
that way.

hmmh, the cleansstate task does neither exist for python nor for gdbm.

ERROR: Task do_cleansstate does not exist for target python

regards,

Andre