Date   

Re: Weekly Test Report for Yocto 1.1 M1 RC2 - 20110528

Liu, Song <song.liu@...>
 

I don’t see anyone reply to this. Which bug is opened for the Beagleboard BSP build failure? It seem to be a critical issue.

 

Tom, shall you or someone else look into this?

 

Song

 

From: poky-bounces@... [mailto:poky-bounces@...] On Behalf Of Xu, Jiajun
Sent: Tuesday, May 31, 2011 8:41 AM
To: poky@...; yocto@...
Subject: [poky] Weekly Test Report for Yocto 1.1 M1 RC2 - 20110528

 

Hi all,

       This is the weekly test report for Yocto 1.1 M1 RC2 build. There is no new bugs found in this testing. 3 BLOCK issues found in RC1 are fixed. The only one block issue is beagleboard build failed on autobuilder. There are still 9 old open bugs. Grub installation fail on 3 intel BSPs. Graphics testing on sugarbay is blocked.

       For bug fixing, the keyboard not work issue and toolchain not built out issue are fixed. Meanwhile, the cvs compile issue is marked as INVALID because it also fails on native. We also remove sudoku-savant compile test in qemu because such error may be caused by limited memory in qemu.

       If there is no new build for M1, QA will continue fullpass testing against RC2.

 

Test Summary

---------------------------------------

Test Result Summary

 

Component

Target

Status

Comments

 

BSP

SugarBay

GOOD

Graphics testing is blocked; soft keyboard will be triggered with terminal icon;

 

 

CrownBay

GOOD

Grub installation failed;

 

 

JasperForest

GOOD

Everything runs well

 

 

Blacksand

GOOD

Grub installation failed; S3 does not work;

 

 

eMenlow

GOOD

System installation failed; S3 does not work;

 

 

Beagleboard

BLOCK

Build failed

 

 

Routerstationpro

GOOD

Everything runs well

 

 

Mpc8315e-rdb

GOOD

Everything runs well

 

QEMU

qemux86

GOOD

Everything runs well

 

 

qemux86-64

GOOD

Everything runs well

 

 

qemuarm

GOOD

Everything runs well

 

 

qemuppc

GOOD

unfs does not work with qemuppc

 

 

qemumips

GOOD

Everything runs well

 

ADT

 

Buggy

unfs does not work with qemuppc

 

 

 

Critical bugs, more than 50% test cases are blocked

 

 

Only Normal, Minor or Enhancement bugs, less than 10% test cases failed

 

 

Normal, Major and Critical bugs, more than 10% test cases failed

 

Detailed Test Result for each component

 

Target

Total TCs

Not Run

Passed

Failed

Not testable (Blocked)

 

Sugarbay Sato-SDK

55

0

53

1 (bug 1101)

1 (bug 1112)

 

Crownbay Sato-SDK

54

0

49

1 (bug 1099)

4

 

Jasperforest LSB-SDK

31

0

31

0

0

 

n450 Sato-SDK

54

0

48

2 (bug 613, 1099)

4

 

eMenlow Sato-SDK

54

0

48

2 (bug 1099, 503)

4

 

Routerstationpro Sato-SDK

29

0

29

0

0

 

Mpc8315e-rdb Sato-SDK

30

0

26

4 (bug 766)

0

 

Qemux86-64 Sato

27

0

27

0

0

 

Qemux86-64 Sato-SDK

30

0

30

0

0

 

Qemux86 Sato

27

0

27

0

0

 

Qemux86 Sato-SDK

30

0

30

0

0

 

Qemumips Sato

26

0

26

0

0

 

Qemumips Sato-SDK

32

0

32

0

0

 

Qemuppc Sato

20

0

19

0

1 (bug 414)

 

Qemuppc Sato-SDK

26

0

25

0

1 (bug 414)

 

Qemuarm Sato

26

0

26

0

0

 

Qemuarm Sato-SDK

32

0

32

0

0

 

ADT

6

0

5

1 (bug 414)

0

 

Total

589

0

563

11

15

 

 

* You can check the detailed test result in attachment for each target.

** The failed/blocked case number is listed with failed cases’ bug number.

 

Commit Information

---------------------------------------

Tree/Branch: Poky/1.1_M1

Poky Commit: 4ff7af11ef69849ef9c16f585eae58ac920b222b

Meta Branch: 1.1_M1

Meta Commit: fc719f0cd6530ce15148b4aa274f1644b461b298

 

Issue Summary

---------------------------------------

Component

Bug Number

Target Milestone

System & Core OS

Installation & Boot

Bug 1099: [blacksand/emenlow/crownbay] grub install failed with sato-sdk live image

1.1 M2

Power Mangement

Bug 613: [Blacksand]system cannot enter S3 standby mode

1.1

Bug 503: [emenlow] system cannot enter S3 standby mode

1.1

Others

Bug 1101: keyboard pop up when clicking terminal icon

1.0 M2

Bug 1107: Open or add person in contacts may segfault on sugarbay/blacksand

1.1 M2

Bug 1097: The mouse can not click accurate to the icons in qemumips X

1.1 M2

Graphics

Bug 1112: [sugarbay] mesa-demos should be added into sato image for graphics testing

Not specified

Bug 883: [Sugarbay] GFX 3D game test fail to run with sugarbay BSP image due to libsdl.so

1.1

Multimedia

Works well in sugarbay/n450/eMenlow/crownbay

 

ADT

Bug 414: [PPC] kernel panic when booting poky-image-sdk-qemuppc through UNFS

1.1 M3

 

Verified Fixed Bugs:

1.     Bug 1100: [emenlow/crownbay-noemgd] X window could not start up with sato-sdk image

2.     Bug 1108: keyboard could not work in qemux86/x86-64

3.     Bug 1093: meta-toolchain-gmae: eglibc fails to build with 4.6

 

Best Regards,

Jiajun


Re: FW: problem in LIC_FILES_CHKSUM

Saul Wold <sgw@...>
 

On 06/01/2011 07:42 AM, Nikhil Kamath wrote:
Hi,

We are trying to build a linux kernel 2.6.35.3 for imx platform. We are
facing a problem as attached in the mail.


The following steps followed are as follows

1.Initially we have run the $bitbake poky-image-minimal for ‘qemuarm’
machine. It got compiled.

2.Next I added a folder named ‘ linux-imx’ in
‘\poky-bernard-5.0\meta\recipes-kernel\linux’ to create a kernel image
for imx platform.

3.The linux-imx folder contains mx35pdk folder, which inturn contains
defconfig file for imx35pdk board.

4.The linux.inc & linux-imx_git.bb is added in linux folder
‘\poky-bernard-5.0\meta\recipes-kernel\linux’.

5.Added mx35pdk.conf file in ‘\poky-bernard-5.0\meta\conf\machine’.

6.Then I ran $bitbake linux-imx

Please see the following attached image.
You need to setup the LIC_FILES_CHKSUM correctly, is your linux-imx a regular kernel source or does it contain other source?

LIC_FILES_CHKSUM is looking for a COPYING in the source directory, which may not be in your source area, you can look at tmp/work/mx35pdk-poky-linux/linux-imx-2.6.35.3-r0/git to check for the correct licensing files.


Sau!

Thanks,
Prashanth Shiva
EmSyS, Larsen & Toubro Limited,
Mysore | Ph: +91-821-2405582
http://www.Lntemsys.com



This mail is classified as :
( ) L&T EmSyS Proprietary ( ) L&T EmSyS Confidential ( x ) L&T EmSyS
Internal Use ( ) L&T EmSyS General Business

This email may contain confidential or privileged information for the
intended recipient(s). If you are not the intended recipient, please do
not use or disseminate the information, notify the sender and delete it
from your system. Thanks!!



*Larsen & Toubro Limited

www.larsentoubro.com <http://www.larsentoubro.com>

*This Email may contain confidential or privileged information for the
intended recipient (s) If you are not the intended recipient, please do
not use or disseminate the information, notify the sender and delete it
from your system.



*Larsen & Toubro Limited

www.larsentoubro.com

*This Email may contain confidential or privileged information for the
intended recipient (s) If you are not the intended recipient, please do
not use or disseminate the information, notify the sender and delete it
from your system.



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


FW: problem in LIC_FILES_CHKSUM

Nikhil Kamath <Nikhil.Kamath@...>
 

 

Hi,

 

We are trying to build a linux kernel 2.6.35.3 for imx platform. We are facing a problem as  attached in the mail.


The following steps followed are as follows

 

1.       Initially we have run the $bitbake poky-image-minimal for ‘qemuarm’ machine. It got compiled.

2.       Next I added a folder named ‘ linux-imx’  in ‘\poky-bernard-5.0\meta\recipes-kernel\linux’ to create a kernel image for imx platform.

3.       The linux-imx folder contains mx35pdk folder, which inturn contains defconfig file for imx35pdk board.

4.       The linux.inc &  linux-imx_git.bb is added in linux folder ‘\poky-bernard-5.0\meta\recipes-kernel\linux’.

5.       Added mx35pdk.conf file in ‘\poky-bernard-5.0\meta\conf\machine’.

6.       Then I ran $bitbake linux-imx

 

 

Please see the following attached image.

 

 

Thanks,
Prashanth Shiva
EmSyS, Larsen & Toubro Limited,
Mysore | Ph: +91-821-2405582
http://www.Lntemsys.com



This mail is classified as :
( ) L&T EmSyS Proprietary ( ) L&T EmSyS Confidential ( x  ) L&T EmSyS Internal Use ( ) L&T EmSyS General Business

This email may contain confidential or privileged information for the intended recipient(s). If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system. Thanks!!

 



Larsen & Toubro Limited

www.larsentoubro.com

This Email may contain confidential or privileged information for the intended recipient (s) If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system.



Larsen & Toubro Limited

www.larsentoubro.com

This Email may contain confidential or privileged information for the intended recipient (s) If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system.


FW: Problem in kernel building

Nikhil Kamath <Nikhil.Kamath@...>
 

Hi,

 

Thanks for the last reply.

We are trying to build a linux kernel 2.6.35.3 for imx platform. We are facing a problem as  attached in the mail.


The following steps followed are as follows

 

1.       Initially we have run the $bitbake poky-image-minimal for ‘qemuarm’ machine. It got compiled.

2.       Next I added a folder named ‘ linux-imx’  in ‘\poky-bernard-5.0\meta\recipes-kernel\linux’ to create a kernel image for imx platform.

3.       The linux-imx folder contains mx35pdk folder, which inturn contains defconfig file for imx35pdk board.

4.       The linux.inc &  linux-imx_git.bb is added in linux folder ‘\poky-bernard-5.0\meta\recipes-kernel\linux’.

5.       Added mx35pdk.conf file in ‘\poky-bernard-5.0\meta\conf\machine’.

6.       Then I ran $bitbake linux-imx

 

Please see the following attached image.

 

Thanks,
Prashanth Shiva
EmSyS, Larsen & Toubro Limited,
Mysore | Ph: +91-821-2405582
http://www.Lntemsys.com



This mail is classified as :
( ) L&T EmSyS Proprietary ( ) L&T EmSyS Confidential ( x  ) L&T EmSyS Internal Use ( ) L&T EmSyS General Business

This email may contain confidential or privileged information for the intended recipient(s). If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system. Thanks!!

 



Larsen & Toubro Limited

www.larsentoubro.com

This Email may contain confidential or privileged information for the intended recipient (s) If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system.



Larsen & Toubro Limited

www.larsentoubro.com

This Email may contain confidential or privileged information for the intended recipient (s) If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system.


Yocto weekly bug trend charts -- WW22

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

Hi all,
The open bug number of last week increased to 203, which is the highest number in our project. QA is doing validation for Yocto 1.1 M1 builds. Bug status of WW22 could be found on https://wiki.pokylinux.org/wiki/Yocto_Bug_Trend.

Best Regards,
Jiajun


Re: Weekly Test Report for Yocto 1.1 M1 RC2 - 20110528

Darren Hart <dvhart@...>
 

On 05/31/2011 08:41 AM, Xu, Jiajun wrote:
Hi all,

This is the weekly test report for Yocto 1.1 M1 RC2 build. There
is no new bugs found in this testing. 3 BLOCK issues found in RC1 are
fixed. The only one block issue is beagleboard build failed on
autobuilder.
I didn't see any bugs opened against Beagleboard mentioned below (nor
via a bugzilla query). Are there bugs opened against these build failures?

Thanks,
--
Darren

There are still 9 old open bugs. Grub installation fail on
3 intel BSPs. Graphics testing on sugarbay is blocked.

For bug fixing, the keyboard not work issue and toolchain not
built out issue are fixed. Meanwhile, the cvs compile issue is marked as
INVALID because it also fails on native. We also remove sudoku-savant
compile test in qemu because such error may be caused by limited memory
in qemu.

If there is no new build for M1, QA will continue fullpass
testing against RC2.



*Test Summary*

*---------------------------------------*







*Test Result Summary*





*Component*



*Target*



*Status*



*Comments*





*BSP*



SugarBay



GOOD



Graphics testing is blocked; soft keyboard will be triggered with
terminal icon;





 



CrownBay



GOOD



Grub installation failed;





 



JasperForest



GOOD



Everything runs well





 



Blacksand



GOOD



Grub installation failed; S3 does not work;





 



eMenlow



GOOD



System installation failed; S3 does not work;





 



Beagleboard



BLOCK



Build failed





 



Routerstationpro



GOOD



Everything runs well





 



Mpc8315e-rdb



GOOD



Everything runs well





*QEMU*



qemux86



GOOD



Everything runs well





 



qemux86-64



GOOD



Everything runs well





 



qemuarm



GOOD



Everything runs well





 



qemuppc



GOOD



unfs does not work with qemuppc





 



qemumips



GOOD



Everything runs well





*ADT*



 



Buggy



unfs does not work with qemuppc







* *

 



Critical bugs, more than 50% test cases are blocked





 



Only Normal, Minor or Enhancement bugs, less than 10% test cases failed





 



Normal, Major and Critical bugs, more than 10% test cases failed







*Detailed Test Result for each component*





*Target*



*Total TCs***



*Not Run*



*Passed***



*Failed***



*Not testable (Blocked)***





*Sugarbay Sato-SDK*



55



0



53



1 (bug 1101)



1 (bug 1112)





*Crownbay Sato-SDK*



54



0



49



1 (bug 1099)



4





*Jasperforest LSB-SDK*



31



0



31



0



0





*n450 Sato-SDK*



54



0



48



2 (bug 613, 1099)



4





*eMenlow Sato-SDK*



54



0



48



2 (bug 1099, 503)



4





*Routerstationpro Sato-SDK*



29



0



29



0



0





*Mpc8315e-rdb Sato-SDK*



30



0



26



4 (bug 766)



0





*Qemux86-64 Sato*



27



0



27



0



0





*Qemux86-64 Sato-SDK*



30



0



30



0



0





*Qemux86 Sato*



27



0



27



0



0





*Qemux86 Sato-SDK*



30



0



30



0



0





*Qemumips Sato*



26



0



26



0



0





*Qemumips Sato-SDK*



32



0



32



0



0





*Qemuppc Sato*



20



0



19



0



1 (bug 414)





*Qemuppc Sato-SDK*



26



0



25



0



1 (bug 414)





*Qemuarm Sato*



26



0



26



0



0





*Qemuarm Sato-SDK*



32



0



32



0



0





*ADT*



6



0



5



1 (bug 414)



0





*Total*



589



0



563



11



15







* *






* You can check the detailed test result in attachment for each target.

** The failed/blocked case number is listed with failed cases’ bug number.



*Commit Information*

*---------------------------------------*

Tree/Branch: Poky/1.1_M1

Poky Commit: 4ff7af11ef69849ef9c16f585eae58ac920b222b

Meta Branch: 1.1_M1

Meta Commit: fc719f0cd6530ce15148b4aa274f1644b461b298



*Issue Summary*

*---------------------------------------*

*Component*



*Bug Number*



*Target Milestone*

*System & Core OS*



*Installation & Boot*



Bug 1099: [blacksand/emenlow/crownbay] grub install failed with sato-sdk
live image



1.1 M2

*Power Mangement*



Bug 613: [Blacksand]system cannot enter S3 standby mode



1.1

Bug 503: [emenlow] system cannot enter S3 standby mode



1.1

*Others*



Bug 1101: keyboard pop up when clicking terminal icon



1.0 M2

Bug 1107: Open or add person in contacts may segfault on sugarbay/blacksand



1.1 M2

Bug 1097: The mouse can not click accurate to the icons in qemumips X



1.1 M2

*Graphics*



Bug 1112: [sugarbay] mesa-demos should be added into sato image for
graphics testing



Not specified

Bug 883: [Sugarbay] GFX 3D game test fail to run with sugarbay BSP image
due to libsdl.so



1.1

*Multimedia*



Works well in sugarbay/n450/eMenlow/crownbay



 

*ADT*



Bug 414: [PPC] kernel panic when booting poky-image-sdk-qemuppc through UNFS



1.1 M3



Verified Fixed Bugs:

1. Bug 1100 <http://bugzilla.pokylinux.org/show_bug.cgi?id=1100>:
[emenlow/crownbay-noemgd] X window could not start up with sato-sdk image

2. Bug 1108 <http://bugzilla.pokylinux.org/show_bug.cgi?id=1108>:
keyboard could not work in qemux86/x86-64

3. Bug 1093 <http://bugzilla.pokylinux.org/show_bug.cgi?id=1093>:
meta-toolchain-gmae: eglibc fails to build with 4.6



Best Regards,

Jiajun



_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel


Yocto Technical Team meeting minutes from May 31st

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

Attendees: Saul, Darren, Paul, Jeff P, Richard, Jessica, Song, Dennis, Tom, Julie, Jefro, Mark, Bruce

Agenda:
1) Review Yocto 1.1 Release Criteria
See details at: https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.1_Release_Criteria
Julie/Song: Ask Jiajun which distros he is testing against.
Julie/Song: Add tests for N+1 of Fedora and Ubuntu to our M2, M3, M4 release criteria.

2) Discuss M1 1.1 Release Status
RC2 was available on Sunday, May 29th. Team will have a Go/No-Go meeting on June 7th during the Technical Team meeting.

3) Discuss M2 1.1 Scope
Song is leading a meeting to discuss M2 1.1 scope with maintainers.

4) Opens

Paul: Quick Start should reference 5.0.1. Paul will ask Beth to make sure this happens.
Richard: We need a plan for bugs:
1. [PPC] kernel panic when booting poky-image-sdk-qemuppc through UNFS
http://bugzilla.pokylinux.org/show_bug.cgi?id=414
2. [mpc8315e-rdb] USB does not work on mpc8315e-rdb
http://bugzilla.pokylinux.org/show_bug.cgi?id=766
Bruce/Mark will kick off the discussions.


Weekly Test Report for Yocto 1.1 M1 RC2 - 20110528

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

Hi all,

       This is the weekly test report for Yocto 1.1 M1 RC2 build. There is no new bugs found in this testing. 3 BLOCK issues found in RC1 are fixed. The only one block issue is beagleboard build failed on autobuilder. There are still 9 old open bugs. Grub installation fail on 3 intel BSPs. Graphics testing on sugarbay is blocked.

       For bug fixing, the keyboard not work issue and toolchain not built out issue are fixed. Meanwhile, the cvs compile issue is marked as INVALID because it also fails on native. We also remove sudoku-savant compile test in qemu because such error may be caused by limited memory in qemu.

       If there is no new build for M1, QA will continue fullpass testing against RC2.

 

Test Summary

---------------------------------------

Test Result Summary

 

Component

Target

Status

Comments

 

BSP

SugarBay

GOOD

Graphics testing is blocked; soft keyboard will be triggered with terminal icon;

 

 

CrownBay

GOOD

Grub installation failed;

 

 

JasperForest

GOOD

Everything runs well

 

 

Blacksand

GOOD

Grub installation failed; S3 does not work;

 

 

eMenlow

GOOD

System installation failed; S3 does not work;

 

 

Beagleboard

BLOCK

Build failed

 

 

Routerstationpro

GOOD

Everything runs well

 

 

Mpc8315e-rdb

GOOD

Everything runs well

 

QEMU

qemux86

GOOD

Everything runs well

 

 

qemux86-64

GOOD

Everything runs well

 

 

qemuarm

GOOD

Everything runs well

 

 

qemuppc

GOOD

unfs does not work with qemuppc

 

 

qemumips

GOOD

Everything runs well

 

ADT

 

Buggy

unfs does not work with qemuppc

 

 

 

Critical bugs, more than 50% test cases are blocked

 

 

Only Normal, Minor or Enhancement bugs, less than 10% test cases failed

 

 

Normal, Major and Critical bugs, more than 10% test cases failed

 

Detailed Test Result for each component

 

Target

Total TCs

Not Run

Passed

Failed

Not testable (Blocked)

 

Sugarbay Sato-SDK

55

0

53

1 (bug 1101)

1 (bug 1112)

 

Crownbay Sato-SDK

54

0

49

1 (bug 1099)

4

 

Jasperforest LSB-SDK

31

0

31

0

0

 

n450 Sato-SDK

54

0

48

2 (bug 613, 1099)

4

 

eMenlow Sato-SDK

54

0

48

2 (bug 1099, 503)

4

 

Routerstationpro Sato-SDK

29

0

29

0

0

 

Mpc8315e-rdb Sato-SDK

30

0

26

4 (bug 766)

0

 

Qemux86-64 Sato

27

0

27

0

0

 

Qemux86-64 Sato-SDK

30

0

30

0

0

 

Qemux86 Sato

27

0

27

0

0

 

Qemux86 Sato-SDK

30

0

30

0

0

 

Qemumips Sato

26

0

26

0

0

 

Qemumips Sato-SDK

32

0

32

0

0

 

Qemuppc Sato

20

0

19

0

1 (bug 414)

 

Qemuppc Sato-SDK

26

0

25

0

1 (bug 414)

 

Qemuarm Sato

26

0

26

0

0

 

Qemuarm Sato-SDK

32

0

32

0

0

 

ADT

6

0

5

1 (bug 414)

0

 

Total

589

0

563

11

15

 

 

* You can check the detailed test result in attachment for each target.

** The failed/blocked case number is listed with failed cases’ bug number.

 

Commit Information

---------------------------------------

Tree/Branch: Poky/1.1_M1

Poky Commit: 4ff7af11ef69849ef9c16f585eae58ac920b222b

Meta Branch: 1.1_M1

Meta Commit: fc719f0cd6530ce15148b4aa274f1644b461b298

 

Issue Summary

---------------------------------------

Component

Bug Number

Target Milestone

System & Core OS

Installation & Boot

Bug 1099: [blacksand/emenlow/crownbay] grub install failed with sato-sdk live image

1.1 M2

Power Mangement

Bug 613: [Blacksand]system cannot enter S3 standby mode

1.1

Bug 503: [emenlow] system cannot enter S3 standby mode

1.1

Others

Bug 1101: keyboard pop up when clicking terminal icon

1.0 M2

Bug 1107: Open or add person in contacts may segfault on sugarbay/blacksand

1.1 M2

Bug 1097: The mouse can not click accurate to the icons in qemumips X

1.1 M2

Graphics

Bug 1112: [sugarbay] mesa-demos should be added into sato image for graphics testing

Not specified

Bug 883: [Sugarbay] GFX 3D game test fail to run with sugarbay BSP image due to libsdl.so

1.1

Multimedia

Works well in sugarbay/n450/eMenlow/crownbay

 

ADT

Bug 414: [PPC] kernel panic when booting poky-image-sdk-qemuppc through UNFS

1.1 M3

 

Verified Fixed Bugs:

1.     Bug 1100: [emenlow/crownbay-noemgd] X window could not start up with sato-sdk image

2.     Bug 1108: keyboard could not work in qemux86/x86-64

3.     Bug 1093: meta-toolchain-gmae: eglibc fails to build with 4.6

 

Best Regards,

Jiajun


Re: FW: Problem to generate u-boot image

Darren Hart <dvhart@...>
 

On 05/31/2011 01:44 AM, Paul Eggleton wrote:
On Friday 27 May 2011 09:17:45 Nikhil Kamath wrote:
$ bitbake u-boot_git
When specifying a target for bitbake you can't include the version (the
underscore _ and everything after it). Poky will take care of selecting the
version for you; in this case there is only one. So you should run the
following instead:

$ bitbake u-boot

FYI for future reference if you do have multiple version choices and want to
force one of them to be selected that is not the default, you need to add this
somewhere (initially local.conf, but it may become part of your custom distro
if you later create one):

PREFERRED_VERSION_packagename = "1.0"

(Assuming packagename is the name of the package and 1.0 is the version you
want to select.)

Cheers,
Paul
Paul is correct in all the above. However, u-boot is very
machine-specific, and there is no qemuarm u-boot configuration. In order
to build u-boot, you must define:

UBOOT_MACHINE
UBOOT_ENTRYPOINT
UBOOT_LOADADDRESS

In bernard and older releases, the first is usally defined in the
u-boot_git.bb as a machine override:

UBOOT_MACHINE_your-machine = "uboot-machine-config"

Where uboot-machine-config is a named machine config that upstream
u-boot ships with its sources. The second and third variable are usually
defined in the machine configuration file.

For example, for the beagleboard, these values are set as:

UBOOT_MACHINE = "omap3_beagle_config"
UBOOT_ENTRYPOINT = "0x80008000"
UBOOT_LOADADDRESS = "0x80008000"

If you aren't sure what those values should be, consider starting a
thread on the u-boot mailing list on how to configure u-boot for your
specific machine.

Thanks,

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


Yocto Technical Team meeting Agenda for Tuesday, May 31st, 8am Pacific

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

Yocto Technical Team,
Here is an agenda for the Yocto Technical Team meeting on Tuesday, May 31st.
Thanks.
- Julie

Dial in: 916-356-2663, Bridge: 94, Passcode: 8963523

Agenda:
1) Review Yocto 1.1 Release Criteria - https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.1_Release_Criteria
2) Discuss M1 1.1 Release Status - RC2 available (?); Go/No-Go for June 6th?
3) Discuss M2 1.1 Scope
4) Opens

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


Re: FW: Problem to generate u-boot image

Paul Eggleton
 

On Friday 27 May 2011 09:17:45 Nikhil Kamath wrote:
$ bitbake u-boot_git
When specifying a target for bitbake you can't include the version (the
underscore _ and everything after it). Poky will take care of selecting the
version for you; in this case there is only one. So you should run the
following instead:

$ bitbake u-boot

FYI for future reference if you do have multiple version choices and want to
force one of them to be selected that is not the default, you need to add this
somewhere (initially local.conf, but it may become part of your custom distro
if you later create one):

PREFERRED_VERSION_packagename = "1.0"

(Assuming packagename is the name of the package and 1.0 is the version you
want to select.)

Cheers,
Paul

--

Paul Eggleton
Intel Open Source Technology Centre


Re: [PATCH 0/3][KERNEL] base patches needed for romley

Darren Hart <darren.hart@...>
 

On 05/27/2011 08:20 PM, Zanussi, Tom wrote:
On Fri, 2011-05-27 at 20:07 -0700, Hart, Darren wrote:
On 05/27/2011 01:45 PM, tom.zanussi@... wrote:
From: Tom Zanussi <tom.zanussi@...>

These upstreamed post-2.6.37 patches are needed by the romley BSP
for 2.6.37.

Note that I've removed the e-mail addresses from these posted patches,
but the git branch retains them.
I understand the reason, but this should no longer be necessary. The new
send-pull-request script only matches on "^Signed-off-by" and
"^[Cc][Cc]:", and you can do a dry run by answering "no" when prompted
and you can see where it would try and send the patches. If you notice
that a commit adding patches to recipe pulls in emails included in the
patches, PLEASE let me know. This should no longer be the case.
I didn't try that, just decided I didn't want to risk it, but did try it
now and get:

Send this email? ([y]es|[n]o|[q]uit|[a]ll): n
(mbox) Adding cc: Seth Heasley from line 'From: Seth Heasley'
(body) Adding cc: Seth Heasley from line 'Signed-off-by: Seth Heasley'
(body) Adding cc: Jeff Garzik from line 'Signed-off-by: Jeff Garzik'

Ah... that's really unfortunate. I fixed our script from harvesting
those, but git send-email still picks them out :-(

Thanks for testing and confirming the behavior.

--
Darren

Use of uninitialized value $cc in string eq at /usr/lib/git-core/git-send-email line 842.
Use of uninitialized value $cc in string eq at /usr/lib/git-core/git-send-email line 842.
Use of uninitialized value $cc in string eq at /usr/lib/git-core/git-send-email line 842.
Use of uninitialized value $cc in string eq at /usr/lib/git-core/git-send-email line 842.
Use of uninitialized value $cc in string eq at /usr/lib/git-core/git-send-email line 842.
Use of uninitialized value $cc in string eq at /usr/lib/git-core/git-send-email line 842.
Use of uninitialized value $cc in string eq at /usr/lib/git-core/git-send-email line 842.
Use of uninitialized value $cc in string eq at /usr/lib/git-core/git-send-email line 842.
Use of uninitialized value $cc in string eq at /usr/lib/git-core/git-send-email line 842.
Use of uninitialized value $cc in string eq at /usr/lib/git-core/git-send-email line 842.
Use of uninitialized value $cc in string eq at /usr/lib/git-core/git-send-email line 842.
Use of uninitialized value $cc in string eq at /usr/lib/git-core/git-send-email line 842.
W: unable to extract a valid address from: Seth Heasley
W: unable to extract a valid address from: Seth Heasley
W: unable to extract a valid address from: Jeff Garzik
W: unable to extract a valid address from: Seth Heasley
W: unable to extract a valid address from: Seth Heasley
W: unable to extract a valid address from: Jeff Garzik

It looks like it is trying to cc the e-mails in the patch, or am I
reading that wrong?

The poky/master commit I'm using is:

1169f1b066d0028bd2ef7915440450bd42ef165e

Tom

--
Darren


Please pull into linux-yocto-2.6.37.

Thanks,

Tom

Pull URL: git://git.yoctoproject.org/linux-yocto-2.6.37-contrib
Branch: tzanussi/romley-new-options-and-refactor-base
Browse: http://git.yoctoproject.org/cgit.cgi/linux-yocto-2.6.37-contrib/log/?h=tzanussi/romley-new-options-and-refactor-base

Greg Rose (1):
Remove extra struct page member from the buffer info structure

Seth Heasley (2):
x86/PCI: irq and pci_ids patch for Intel Patsburg
ahci: AHCI mode SATA patch for Intel Patsburg SATA RAID controller

arch/x86/pci/irq.c | 3 ++-
drivers/ata/ahci.c | 1 +
drivers/net/igbvf/igbvf.h | 1 -
include/linux/pci_ids.h | 3 ++-
4 files changed, 5 insertions(+), 3 deletions(-)

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

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


Re: Yocto Bug Triage call for action

Saul Wold <saul.wold@...>
 

On 05/26/2011 03:50 PM, Zhang, Jessica wrote:
Hi All,

The Yocto bug triage team did bug scrub and the following 2 bugs are
identified as critical major which means they need to be fixed ASAP for
the upcoming 1.1 M1 release.

1100 – [emenlow/crownbay-noemgd] X window could not start up with
sato-sdk image (Tom, Dexuan, Darren)

1108 – keyboard could not work in qemux86/x86-64 (Saul, Ke)

So people that are working on these bugs , please make sure leave enough
information for your current investigation/debugging by EOD your time so
the next person in a different time zone can easily pickup the context
and continue working on the fix.
I want to thank Tom, Darren, Ke, Dexuan and Richard for their quick action in tracking down and fixing these 2 issues. It shows the effort that we put into getting the Milestones tested and stabilized across time and space!

Thanks
Sau!

Thanks,

Jessica



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


Re: [PATCH 0/3][KERNEL] base patches needed for romley

Tom Zanussi <tom.zanussi@...>
 

On Fri, 2011-05-27 at 20:07 -0700, Hart, Darren wrote:
On 05/27/2011 01:45 PM, tom.zanussi@... wrote:
From: Tom Zanussi <tom.zanussi@...>

These upstreamed post-2.6.37 patches are needed by the romley BSP
for 2.6.37.

Note that I've removed the e-mail addresses from these posted patches,
but the git branch retains them.
I understand the reason, but this should no longer be necessary. The new
send-pull-request script only matches on "^Signed-off-by" and
"^[Cc][Cc]:", and you can do a dry run by answering "no" when prompted
and you can see where it would try and send the patches. If you notice
that a commit adding patches to recipe pulls in emails included in the
patches, PLEASE let me know. This should no longer be the case.
I didn't try that, just decided I didn't want to risk it, but did try it
now and get:

Send this email? ([y]es|[n]o|[q]uit|[a]ll): n
(mbox) Adding cc: Seth Heasley from line 'From: Seth Heasley'
(body) Adding cc: Seth Heasley from line 'Signed-off-by: Seth Heasley'
(body) Adding cc: Jeff Garzik from line 'Signed-off-by: Jeff Garzik'
Use of uninitialized value $cc in string eq at /usr/lib/git-core/git-send-email line 842.
Use of uninitialized value $cc in string eq at /usr/lib/git-core/git-send-email line 842.
Use of uninitialized value $cc in string eq at /usr/lib/git-core/git-send-email line 842.
Use of uninitialized value $cc in string eq at /usr/lib/git-core/git-send-email line 842.
Use of uninitialized value $cc in string eq at /usr/lib/git-core/git-send-email line 842.
Use of uninitialized value $cc in string eq at /usr/lib/git-core/git-send-email line 842.
Use of uninitialized value $cc in string eq at /usr/lib/git-core/git-send-email line 842.
Use of uninitialized value $cc in string eq at /usr/lib/git-core/git-send-email line 842.
Use of uninitialized value $cc in string eq at /usr/lib/git-core/git-send-email line 842.
Use of uninitialized value $cc in string eq at /usr/lib/git-core/git-send-email line 842.
Use of uninitialized value $cc in string eq at /usr/lib/git-core/git-send-email line 842.
Use of uninitialized value $cc in string eq at /usr/lib/git-core/git-send-email line 842.
W: unable to extract a valid address from: Seth Heasley
W: unable to extract a valid address from: Seth Heasley
W: unable to extract a valid address from: Jeff Garzik
W: unable to extract a valid address from: Seth Heasley
W: unable to extract a valid address from: Seth Heasley
W: unable to extract a valid address from: Jeff Garzik

It looks like it is trying to cc the e-mails in the patch, or am I
reading that wrong?

The poky/master commit I'm using is:

1169f1b066d0028bd2ef7915440450bd42ef165e

Tom

--
Darren


Please pull into linux-yocto-2.6.37.

Thanks,

Tom

Pull URL: git://git.yoctoproject.org/linux-yocto-2.6.37-contrib
Branch: tzanussi/romley-new-options-and-refactor-base
Browse: http://git.yoctoproject.org/cgit.cgi/linux-yocto-2.6.37-contrib/log/?h=tzanussi/romley-new-options-and-refactor-base

Greg Rose (1):
Remove extra struct page member from the buffer info structure

Seth Heasley (2):
x86/PCI: irq and pci_ids patch for Intel Patsburg
ahci: AHCI mode SATA patch for Intel Patsburg SATA RAID controller

arch/x86/pci/irq.c | 3 ++-
drivers/ata/ahci.c | 1 +
drivers/net/igbvf/igbvf.h | 1 -
include/linux/pci_ids.h | 3 ++-
4 files changed, 5 insertions(+), 3 deletions(-)

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


Re: [PATCH 0/3][KERNEL] base patches needed for romley

Darren Hart <darren.hart@...>
 

On 05/27/2011 01:45 PM, tom.zanussi@... wrote:
From: Tom Zanussi <tom.zanussi@...>

These upstreamed post-2.6.37 patches are needed by the romley BSP
for 2.6.37.

Note that I've removed the e-mail addresses from these posted patches,
but the git branch retains them.
I understand the reason, but this should no longer be necessary. The new
send-pull-request script only matches on "^Signed-off-by" and
"^[Cc][Cc]:", and you can do a dry run by answering "no" when prompted
and you can see where it would try and send the patches. If you notice
that a commit adding patches to recipe pulls in emails included in the
patches, PLEASE let me know. This should no longer be the case.

--
Darren


Please pull into linux-yocto-2.6.37.

Thanks,

Tom

Pull URL: git://git.yoctoproject.org/linux-yocto-2.6.37-contrib
Branch: tzanussi/romley-new-options-and-refactor-base
Browse: http://git.yoctoproject.org/cgit.cgi/linux-yocto-2.6.37-contrib/log/?h=tzanussi/romley-new-options-and-refactor-base

Greg Rose (1):
Remove extra struct page member from the buffer info structure

Seth Heasley (2):
x86/PCI: irq and pci_ids patch for Intel Patsburg
ahci: AHCI mode SATA patch for Intel Patsburg SATA RAID controller

arch/x86/pci/irq.c | 3 ++-
drivers/ata/ahci.c | 1 +
drivers/net/igbvf/igbvf.h | 1 -
include/linux/pci_ids.h | 3 ++-
4 files changed, 5 insertions(+), 3 deletions(-)

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

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


Re: [PATCH 3/3] ahci: AHCI mode SATA patch for Intel Patsburg SATA RAID controller

Tom Zanussi <tom.zanussi@...>
 

On Fri, 2011-05-27 at 17:16 -0700, Bruce Ashfield wrote:
On 11-05-27 5:19 PM, Tom Zanussi wrote:
On Fri, 2011-05-27 at 14:08 -0700, Bruce Ashfield wrote:
On 11-05-27 04:46 PM, tom.zanussi@... wrote:
From: Seth Heasley

commit 64a3903d0885879ba8706a8bcf71c5e3e7664db2 upstream

This patch adds an updated SATA RAID DeviceID for the Intel Patsburg PCH.
Looks like we already had this one in the 2.6.37 tree
via gregkh and -stable

> git tag --contains 5618c45b
v2.6.37.5
v2.6.37.6

And hence the base yocto/standard/common-pc-64/romley
bsp branch.

So I won't do anything with this in particular. It is
interesting though how it applied in your tree. Do you
have all the -stable updates ?

I checked and it doesn't look like I've been hoarding
them, but you never know.
Hmm, yeah, it did apply (checked the build dir for the other changes),
but not sure why I didn't get rejects. My kernel is a little over a
week old, but it does have the .5 stable:
It actually has .6 and certain people (*cough*) didn't push
the tags. I'll fix that tonight.

git has a way of managing to apply changes and do the right
thing. I've double checked, and I do see the change in the
branches waiting for us, so we'll go with that until proven
otherwise.
Yeah, either way it's the same single line change, so whatever's
easiest.

Tom

Cheers,

Bruce


$ git tag --contains 5618c45b
v2.6.37.5

Tom

Bruce


Signed-off-by: Seth Heasley
Signed-off-by: Jeff Garzik
Integrated-by: Tom Zanussi
---
drivers/ata/ahci.c | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/drivers/ata/ahci.c b/drivers/ata/ahci.c
index 3288263..dfc0a26 100644
--- a/drivers/ata/ahci.c
+++ b/drivers/ata/ahci.c
@@ -260,6 +260,7 @@ static const struct pci_device_id ahci_pci_tbl[] = {
{ PCI_VDEVICE(INTEL, 0x1d02), board_ahci }, /* PBG AHCI */
{ PCI_VDEVICE(INTEL, 0x1d04), board_ahci }, /* PBG RAID */
{ PCI_VDEVICE(INTEL, 0x1d06), board_ahci }, /* PBG RAID */
+ { PCI_VDEVICE(INTEL, 0x2826), board_ahci }, /* PBG RAID */

/* JMicron 360/1/3/5/6, match class to avoid IDE function */
{ PCI_VENDOR_ID_JMICRON, PCI_ANY_ID, PCI_ANY_ID, PCI_ANY_ID,


Re: [PATCH 3/3] ahci: AHCI mode SATA patch for Intel Patsburg SATA RAID controller

Bruce Ashfield <bruce.ashfield@...>
 

On 11-05-27 5:19 PM, Tom Zanussi wrote:
On Fri, 2011-05-27 at 14:08 -0700, Bruce Ashfield wrote:
On 11-05-27 04:46 PM, tom.zanussi@... wrote:
From: Seth Heasley

commit 64a3903d0885879ba8706a8bcf71c5e3e7664db2 upstream

This patch adds an updated SATA RAID DeviceID for the Intel Patsburg PCH.
Looks like we already had this one in the 2.6.37 tree
via gregkh and -stable

> git tag --contains 5618c45b
v2.6.37.5
v2.6.37.6

And hence the base yocto/standard/common-pc-64/romley
bsp branch.

So I won't do anything with this in particular. It is
interesting though how it applied in your tree. Do you
have all the -stable updates ?

I checked and it doesn't look like I've been hoarding
them, but you never know.
Hmm, yeah, it did apply (checked the build dir for the other changes),
but not sure why I didn't get rejects. My kernel is a little over a
week old, but it does have the .5 stable:
It actually has .6 and certain people (*cough*) didn't push
the tags. I'll fix that tonight.

git has a way of managing to apply changes and do the right
thing. I've double checked, and I do see the change in the
branches waiting for us, so we'll go with that until proven
otherwise.

Cheers,

Bruce


$ git tag --contains 5618c45b
v2.6.37.5

Tom

Bruce


Signed-off-by: Seth Heasley
Signed-off-by: Jeff Garzik
Integrated-by: Tom Zanussi
---
drivers/ata/ahci.c | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/drivers/ata/ahci.c b/drivers/ata/ahci.c
index 3288263..dfc0a26 100644
--- a/drivers/ata/ahci.c
+++ b/drivers/ata/ahci.c
@@ -260,6 +260,7 @@ static const struct pci_device_id ahci_pci_tbl[] = {
{ PCI_VDEVICE(INTEL, 0x1d02), board_ahci }, /* PBG AHCI */
{ PCI_VDEVICE(INTEL, 0x1d04), board_ahci }, /* PBG RAID */
{ PCI_VDEVICE(INTEL, 0x1d06), board_ahci }, /* PBG RAID */
+ { PCI_VDEVICE(INTEL, 0x2826), board_ahci }, /* PBG RAID */

/* JMicron 360/1/3/5/6, match class to avoid IDE function */
{ PCI_VENDOR_ID_JMICRON, PCI_ANY_ID, PCI_ANY_ID, PCI_ANY_ID,


Re: [PATCH 1/1] meta-intel: fix BBFILE_COLLECTIONS overrides

Tom Zanussi <tom.zanussi@...>
 

On Fri, 2011-05-27 at 15:18 -0700, Jeremy Puhlman wrote:
The crownbay has two BBFILE_COLLECTIONS in the same file, one for
crownbay and one for crownbay-noemgd. The conditional append allows
them to be selected based on the machine selected.
The BBFILE_COLLECTIONS var basically give you a hook so you can find:

BBFILE_PATTERN_<value set in BBFILE_COLLECTIONS>
BBFILE_PRIORITY_<value set in BBFILE_COLLECTIONS>


While it certainly is true you could have different sets, for different
machines, you set those subsequent values identically. At the moment
there appears to be no need unless your using the value in some other
manner else where. FWIW it probably doesn't matter either way, but it
doesn't appear to be needed by the way you are configuring it.
Yeah, you're right - it probably isn't necessary, though not broken
either.

Another thing to put on my list of cleanups for meta-intel that I never
seem to get to...

Thanks for your comments,

Tom

Jeremy Puhlman
Montavista Sofware, LLC.


Re: [PATCH 1/1] meta-intel: fix BBFILE_COLLECTIONS overrides

Jeremy Puhlman <jpuhlman@...>
 

The crownbay has two BBFILE_COLLECTIONS in the same file, one for
crownbay and one for crownbay-noemgd. The conditional append allows
them to be selected based on the machine selected.
The BBFILE_COLLECTIONS var basically give you a hook so you can find:

BBFILE_PATTERN_<value set in BBFILE_COLLECTIONS>
BBFILE_PRIORITY_<value set in BBFILE_COLLECTIONS>


While it certainly is true you could have different sets, for different
machines, you set those subsequent values identically. At the moment
there appears to be no need unless your using the value in some other
manner else where. FWIW it probably doesn't matter either way, but it
doesn't appear to be needed by the way you are configuring it.

Jeremy Puhlman
Montavista Sofware, LLC.


Re: [PATCH 1/1] meta-intel: fix BBFILE_COLLECTIONS overrides

Tom Zanussi <tom.zanussi@...>
 

On Fri, 2011-05-27 at 14:55 -0700, Darren Hart wrote:

On 05/26/2011 08:40 AM, tom.zanussi@... wrote:
From: Tom Zanussi <tom.zanussi@...>

Several BBFILE_COLLECTIONS assignments in the layer.confs for these
meta-intel layers added unwanted machine overrides, resulting in
truncated values for this variable - remove them.
Why the difference between crownbay and the other BSPs? Crownbay uses
_append.
The crownbay has two BBFILE_COLLECTIONS in the same file, one for
crownbay and one for crownbay-noemgd. The conditional append allows
them to be selected based on the machine selected.

Tom

--
Darren


Signed-off-by: Tom Zanussi <tom.zanussi@...>
---
meta-crownbay/conf/layer.conf | 4 ++--
meta-fishriver/conf/layer.conf | 2 +-
meta-jasperforest/conf/layer.conf | 2 +-
meta-sugarbay/conf/layer.conf | 2 +-
4 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/meta-crownbay/conf/layer.conf b/meta-crownbay/conf/layer.conf
index cee4ba2..d15579d 100644
--- a/meta-crownbay/conf/layer.conf
+++ b/meta-crownbay/conf/layer.conf
@@ -5,10 +5,10 @@ BBPATH := "${BBPATH}:${LAYERDIR}"
BBFILES := "${BBFILES} ${LAYERDIR}/recipes-*/*/*.bb \
${LAYERDIR}/recipes-*/*/*.bbappend"

-BBFILE_COLLECTIONS_crownbay += "crownbay"
+BBFILE_COLLECTIONS_append_crownbay += "crownbay"
BBFILE_PATTERN_crownbay := "^${LAYERDIR}/"
BBFILE_PRIORITY_crownbay = "6"

-BBFILE_COLLECTIONS_crownbay-noemgd += "crownbay-noemgd"
+BBFILE_COLLECTIONS_append_crownbay-noemgd += "crownbay-noemgd"
BBFILE_PATTERN_crownbay-noemgd := "^${LAYERDIR}/"
BBFILE_PRIORITY_crownbay-noemgd = "6"
diff --git a/meta-fishriver/conf/layer.conf b/meta-fishriver/conf/layer.conf
index 595bbe3..9162b5e 100644
--- a/meta-fishriver/conf/layer.conf
+++ b/meta-fishriver/conf/layer.conf
@@ -5,6 +5,6 @@ BBPATH := "${BBPATH}:${LAYERDIR}"
BBFILES := "${BBFILES} ${LAYERDIR}/recipes-*/*/*.bb \
${LAYERDIR}/recipes-*/*/*.bbappend"

-BBFILE_COLLECTIONS_fishriver += "fishriver"
+BBFILE_COLLECTIONS += "fishriver"
BBFILE_PATTERN_fishriver := "^${LAYERDIR}/"
BBFILE_PRIORITY_fishriver = "6"
diff --git a/meta-jasperforest/conf/layer.conf b/meta-jasperforest/conf/layer.conf
index 564bb1d..8125659 100644
--- a/meta-jasperforest/conf/layer.conf
+++ b/meta-jasperforest/conf/layer.conf
@@ -7,6 +7,6 @@ BBFILES := "${BBFILES} ${LAYERDIR}/recipes-*/*/*.bb \
${LAYERDIR}/../common/recipes-*/*/*.bb \
${LAYERDIR}/../common/recipes-*/*/*.bbappend"

-BBFILE_COLLECTIONS_jasperforest += "jasperforest"
+BBFILE_COLLECTIONS += "jasperforest"
BBFILE_PATTERN_jasperforest := "^${LAYERDIR}/"
BBFILE_PRIORITY_jasperforest = "6"
diff --git a/meta-sugarbay/conf/layer.conf b/meta-sugarbay/conf/layer.conf
index e23d123..d5f78e1 100644
--- a/meta-sugarbay/conf/layer.conf
+++ b/meta-sugarbay/conf/layer.conf
@@ -7,6 +7,6 @@ BBFILES := "${BBFILES} ${LAYERDIR}/recipes-*/*/*.bb \
${LAYERDIR}/../common/recipes-*/*/*.bb \
${LAYERDIR}/../common/recipes-*/*/*.bbappend"

-BBFILE_COLLECTIONS_sugarbay += "sugarbay"
+BBFILE_COLLECTIONS += "sugarbay"
BBFILE_PATTERN_sugarbay := "^${LAYERDIR}/"
BBFILE_PRIORITY_sugarbay = "6"