yocto@lists.yoctoproject.org

Yocto weekly bug trend charts -- WW10

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

#1122

Hi all,
This is latest Yocto bug trend chart for WW10. QA tested RC1 last week and there are 34 new bugs submitted. Now there are 138 open bugs in bugzilla.

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

Reminder for new release candidates.

Elizabeth Flanagan <elizabeth.flanagan@...>

#1121

All,

I've changed the location of the qemu directory from / to /machines. Just in case anyone was wondering where it went
with the still building RC2.

The new release candidate is almost finished. This one has taken considerably longer as there are more targets. I'll
send out an email later tonight with info on it.

-b

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

Fullpass Test Report for Yocto M4 RC1 20110226 Build

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

#1120

Hi all,

This is the fullpass test report for RC1 build 20110226. The critical bug blocks out testing is most BSP targets build failed on autobuilder. Together with sanity test result against the same build, there are 17 new bugs reported with RC1 build. And there are 31 bugs met in this testing, which cause 73 cases failed. For QEMU targets, most functionality work well, except for partial zypper function. Most failed test cases on beagleboard are excepted and will not be fixed in v1.0. For poky feature, sstate and non-GPLv3 build do not work correctly. SDK testing is partly blocked with i586 toolchain tarball build failed. For compliance with LTP/POSIX/LSB, these testing results are still in analysis and will be published later.

NOTE: Yi Zhao, Liangliang Wang and Liang Li helped to do a sanity test against the latest BSP builds(20110301), including beagleboard, mpc8315e-rdb and routerstationpro. They did not find any show-stoper or critical bugs with this build. Only one new issue is found with RTC set on routerstationpro. You could find the detailed test report in attachment.

Test Summary

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

Test Result Summary
Component		Target	Status	Comments
BSP		SugarBay	BLOCK	BSP build failed
		CrownBay	BLOCK	BSP build failed
		JasperForest	BLOCK	BSP build failed
		Blacksand	BUGGY	BSP build failed, atom-pc build pass for core; With atom-pc image, partial zypper function not work well; connman-applet and audio/video not work;
		Beagleboard	BUGGY	USB, RTC, X window, NAND do not work; sato-sdk image not copied to sharing folder; Most failed cases will be fixed in v1.1. So will skip them in next RC2 testing;
		Routerstationpro	BLOCK	sato-sdk image not copied to sharing folder
		Mpc8315e-rdb	BLOCK	sato-sdk image not copied to sharing folder
QEMU		qemux86	GOOD	Partial zypper function not work well
		qemux86-64	GOOD	Partial zypper function not work well
		qemuarm	GOOD	Partial zypper function not work well
		qemuppc	BUGGY	gcc segfault and zypper function not work well
		qemumips	BUGGY	x11vnc and partial zypper function not work well
Poky			BUGGY	sstate and non-gplv3 build do not work correctly
Documentation			GOOD
SDK			BLOCK	unfs not work for qemuppc; i586 toolchain not build out
Complience Test			In analysis	LTP and POSIX testing is finished and being analysis now; LSB testing is partly finished, you could check the attachment for LSP test result.
	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)
Blacksand Sato	52	0	33	14 (bug 607, 803, 804, 613, 798, 799)	5 (bug 779, 613)
BeagleBoard Sato	21	0	8	10 (bug 764, 765, 767, 772)	3 (bug 764)
Qemux86-64 Sato	21	0	20	1 (bug 721)	0
Qemux86-64 SDK	26	0	22	4 (bug 721)	0
Qemux86 Sato	21	0	18	3 (bug 803, 804)	0
Qemux86 SDK	26	0	23	3 (bug 803, 804)	0
Qemumips Sato	21	0	15	6 (bug 721, 782, 787)	0
Qemumips SDK	26	0	20	6 (bug 721, 782, 787)	0
Qemuppc Sato	18	0	12	6 (bug 722, 787)	0
Qemuppc SDK	23	0	16	7 (bug 722, 780, 778)	0
Qemuarm Sato	21	0	16	5 (bug 491, 489, 490, 749, 787)	0
Qemuarm SDK	26	0	22	4 (bug 491, 489, 490, 787)	0
SDK	3	0	0	1 (bug 414)	2 (Toolchain tarballs not built out for i586)
Poky	8	0	5	3 (bug 598, 712, 788, 789)	0
Documentation	1	0	1	0	0
Total	314	0	231	73	10

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

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

Images

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

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

Issue Summary

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

Zypper/RPM:

1. New! [zypper] zypper install does not work on qemux86/atom-pc

http://bugzilla.pokylinux.org/show_bug.cgi?id=803

2. New! [zypper] package installed by rpm could not be recognized by zypper

http://bugzilla.pokylinux.org/show_bug.cgi?id=804

3. New! rpm remove package error

http://bugzilla.pokylinux.org/show_bug.cgi?id=787

4. [zypper] zypper segfault in qemux86-64 sdk image

http://bugzilla.pokylinux.org/show_bug.cgi?id=721

5. [qemuarm]zypper search package warning in sato image: no '/usr/bin/uuidgen'

http://bugzilla.pokylinux.org/show_bug.cgi?id=749

6. [zypper] package removal failure

http://bugzilla.pokylinux.org/show_bug.cgi?id=491

7. [zypper] uname -m and repo arch difference

http://bugzilla.pokylinux.org/show_bug.cgi?id=489

8. [zypper] installation failure on arm

http://bugzilla.pokylinux.org/show_bug.cgi?id=490

9. [zypper] search failure on qemuppc (nightly build 20110212-1)

http://bugzilla.pokylinux.org/show_bug.cgi?id=722

Poky:

1. New! [sstate] random error message shown when sstate is used

http://bugzilla.pokylinux.org/show_bug.cgi?id=788

2. New! [sstate] only few setscene tasks run even with same build environment

http://bugzilla.pokylinux.org/show_bug.cgi?id=789

3. Fail to build non-GPLv3 image

http://bugzilla.pokylinux.org/show_bug.cgi?id=712

4. [poky] kernel interactive build does not work via ssh

http://bugzilla.pokylinux.org/show_bug.cgi?id=598

SDK:

1. [PPC] kernel panic when booting poky-image-sdk-qemuppc through UNFS

http://bugzilla.pokylinux.org/show_bug.cgi?id=414

BSP:

1. New! [blacksand] no sound even all options in amixer enabled

http://bugzilla.pokylinux.org/show_bug.cgi?id=798

2. New! [blacksand] configured audiosink is not working for video player

http://bugzilla.pokylinux.org/show_bug.cgi?id=799

3. New! [RouterStationPro] Missing file when setting RTC on routerstationpro

http://bugzilla.pokylinux.org/show_bug.cgi?id=801

4. [Connman] xuser must be granted privilege to start connman-applet

http://bugzilla.pokylinux.org/show_bug.cgi?id=779

5. [Blacksand] Some error information prompted when run dmesg command

http://bugzilla.pokylinux.org/show_bug.cgi?id=607

6. [Blacksand]system cannot enter S3 standby mode

http://bugzilla.pokylinux.org/show_bug.cgi?id=613

7. [beagleboard] X server can not startup on beagleboard

http://bugzilla.pokylinux.org/show_bug.cgi?id=764

8. [beagleboard] USB does not work on beagleboard

http://bugzilla.pokylinux.org/show_bug.cgi?id=765

9. [beagleboard] Can not set RTC correctly

http://bugzilla.pokylinux.org/show_bug.cgi?id=767

10. [beagleboard] Can not recognize NAND flash on board

http://bugzilla.pokylinux.org/show_bug.cgi?id=772

Complience:

1. New! The process of installing LSB test suit and running LSB test on qemu-ppc is very slow

http://bugzilla.pokylinux.org/show_bug.cgi?id=793

2. New! LSB: A test case (lib/Config.t) failed during running perl test of LSB

http://bugzilla.pokylinux.org/show_bug.cgi?id=794

3. New! LSB: Some cases (libstdc++.so.6) failed on library check of LSB test

http://bugzilla.pokylinux.org/show_bug.cgi?id=795

4. New! LSB: Some cases related to locale failed on libstdcpp and cpp-t2c test of LSB

http://bugzilla.pokylinux.org/show_bug.cgi?id=796

Others:

1. [X11VNC Server ] No response when I click 'X11VNC Server' icon

http://bugzilla.pokylinux.org/show_bug.cgi?id=781

2. gcc segfault on qemuppc (nightly build 20110226-1)

http://bugzilla.pokylinux.org/show_bug.cgi?id=780

3. The vnc client does not pop-up on qemumips-sato-sdk

http://bugzilla.pokylinux.org/show_bug.cgi?id=782

Best Regards,

Jiajun

M4-RC1_20110226_detail_testreport_fullpass.ods

message/rfc822

Re: yocto supported freescale eval boards

Robert Berger <gmane@...>

#1119

Hi Darren, Bruce,

On 03/06/2011 02:52 AM, Bruce Ashfield wrote:


Besides the PPC the iMX31ADS seems to be supported as well.The imx31ads is supported by older non linux-yocto recipes, so it
may have some bit rot at the moment. Until it gets refreshed onto
a linux-yocto base, your mileage will vary with it.Thanks for the hint;)



We're currently using the following board.

http://search.digikey.com/scripts/DkSearch/dksus.dll?PName?Name=MPC8315E-RDBA-ND&Site=US&Lang=EN
Confirmed. This is the board we are currently using.


There are definitely plans to update/refresh the FSL/e500 board
options. Unofficially there's a whole set of boards that will
work fine, and there's a good pool of good quality BSPs that are
viable options.

I hesitate to say more, since nothing has been quite chosen yet
and I'd be speculating or worse misleading at this point. But
a newer e500 based board is something that will arrive once
everything falls into place.Do you happen to have some time estimation for this?


That being said, I can suggest/help with the addition of any of
a number of FSL powerpc based boards, it all depends on what
the requirements are for the board. Does it just have to
be readily available ? Less than 'x' dollars ? Any particular
peripheral support ?I'm doing a 5 days "Introduction to Embedded Linux" and a 5 days "Device
Drivers and Kernel Internals" training which are pretty much hardware
independent. Just want to avoid using LTIB and want to use yocto
instead, since a "mainline" kernel is definitely preferred over whatever
comes with LTIB. Most likely mainline will work with most of the powerpc
based boards as long as I don't need any fancy peripherals.

Thanks for the offer to help me adding a board. I'll have a chat with my
customer and will let you know.

Regards,

Robert


Cheers,

Bruce

...I read the system requirements label on a software package recently.
It said "requires Windows NT or better". So I installed Unix. -- from a FAQ

My public pgp key is available at:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x90320BF1

Re: yocto supported freescale eval boards

Bruce Ashfield <bruce.ashfield@...>

#1118

On 11-03-05 10:45 AM, Darren Hart wrote:
On 03/05/2011 07:22 AM, Robert Berger wrote:
Hi,

A customer asked for a training with a freescale eval board and I would
like to use yocto for it.

What I found from the documentation is, that the MPC8313E-RDB Reference
Platform is supported. I'm a bit confused by a list, which can be found
on the Freescale website:

http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=MPC8313E-RDB&tab=Buy_Parametric_Tab&pspll=1&fromSearch=false


It says:
MPC8313E-RDB,Hardware Only 8313E PROCESSOR BD (SOCK Hardware Not
Recommended for New Design)

MPC8313E-RDB-T, MPC8313E-RDB-U, MPC8313E-RDB-UT, MPC8313E-RDBB seem to
be still supported. What's the difference? What would you recommend?


Besides the PPC the iMX31ADS seems to be supported as well.The imx31ads is supported by older non linux-yocto recipes, so it
may have some bit rot at the moment. Until it gets refreshed onto
a linux-yocto base, your mileage will vary with it.


What would you recommend? Are there more Freescale eval boards going to
be supported by yocto in the near future?
We're currently using the following board.

http://search.digikey.com/scripts/DkSearch/dksus.dll?PName?Name=MPC8315E-RDBA-ND&Site=US&Lang=ENConfirmed. This is the board we are currently using.



I don't know which upcoming boards are likely to be adopted, perhaps
Bruce (CC'd) will have some ideas?There are definitely plans to update/refresh the FSL/e500 board
options. Unofficially there's a whole set of boards that will
work fine, and there's a good pool of good quality BSPs that are
viable options.

I hesitate to say more, since nothing has been quite chosen yet
and I'd be speculating or worse misleading at this point. But
a newer e500 based board is something that will arrive once
everything falls into place.

That being said, I can suggest/help with the addition of any of
a number of FSL powerpc based boards, it all depends on what
the requirements are for the board. Does it just have to
be readily available ? Less than 'x' dollars ? Any particular
peripheral support ?

Cheers,

Bruce

Re: yocto supported freescale eval boards

Darren Hart <dvhart@...>

#1117

On 03/05/2011 07:22 AM, Robert Berger wrote:
Hi,

A customer asked for a training with a freescale eval board and I would
like to use yocto for it.

What I found from the documentation is, that the MPC8313E-RDB Reference
Platform is supported. I'm a bit confused by a list, which can be found
on the Freescale website:

http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=MPC8313E-RDB&tab=Buy_Parametric_Tab&pspll=1&fromSearch=false

It says:
MPC8313E-RDB,Hardware Only 8313E PROCESSOR BD (SOCK 	Hardware 	Not
Recommended for New Design)

MPC8313E-RDB-T, MPC8313E-RDB-U, MPC8313E-RDB-UT, MPC8313E-RDBB seem to
be still supported. What's the difference? What would you recommend?


Besides the PPC the iMX31ADS seems to be supported as well.

What would you recommend? Are there more Freescale eval boards going to
be supported by yocto in the near future?
We're currently using the following board.

http://search.digikey.com/scripts/DkSearch/dksus.dll?PName?Name=MPC8315E-RDBA-ND&Site=US&Lang=EN

I don't know which upcoming boards are likely to be adopted, perhaps Bruce (CC'd) will have some ideas?

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

yocto supported freescale eval boards

Robert Berger <gmane@...>

#1116

Hi,

A customer asked for a training with a freescale eval board and I would
like to use yocto for it.

What I found from the documentation is, that the MPC8313E-RDB Reference
Platform is supported. I'm a bit confused by a list, which can be found
on the Freescale website:

http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=MPC8313E-RDB&tab=Buy_Parametric_Tab&pspll=1&fromSearch=false

It says:
MPC8313E-RDB,Hardware Only 8313E PROCESSOR BD (SOCK 	Hardware 	Not
Recommended for New Design)

MPC8313E-RDB-T, MPC8313E-RDB-U, MPC8313E-RDB-UT, MPC8313E-RDBB seem to
be still supported. What's the difference? What would you recommend?


Besides the PPC the iMX31ADS seems to be supported as well.

What would you recommend? Are there more Freescale eval boards going to
be supported by yocto in the near future?

Regards,

Robert...In all large corporations, there is a pervasive fear that
someone, omewhere is having fun with a computer on company time.
Networks help alleviate that fear.

My public pgp key is available at:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x90320BF1

[PATCH 1/1] linux-yocto: update machine configurations

Bruce Ashfield <bruce.ashfield@...>

#1115

Fixes [YOCTO #733, YOCTO #766, YOCTO: #801]

Updating the configuration for the routerstation pro and
mpc8315e-rdb to 2.6.37 variants of the RTC, USB and VFAT
filesystem types.

Signed-off-by: Bruce Ashfield <bruce.ashfield@...>
---
 .../conf/distro/include/poky-default-revisions.inc |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/meta/conf/distro/include/poky-default-revisions.inc b/meta/conf/distro/include/poky-default-revisions.inc
index 2f33630..5045c9e 100644
--- a/meta/conf/distro/include/poky-default-revisions.inc
+++ b/meta/conf/distro/include/poky-default-revisions.inc
@@ -108,8 +108,8 @@ SRCREV_machine_pn-linux-yocto_atom-pc ?= "2b412826bbeb4a16abe2ea74f2456ab880c6e3
 SRCREV_machine_pn-linux-yocto_routerstationpro ?= "17dedeb17887eb398743b04615302b61bd95ffdd"
 SRCREV_machine_pn-linux-yocto_mpc8315e-rdb ?= "6117f19403ccd5c288ce553def432925296a28b7"
 SRCREV_machine_pn-linux-yocto_beagleboard ?= "2b412826bbeb4a16abe2ea74f2456ab880c6e3c1"
-SRCREV_machine_pn-linux-yocto ?= "e2cabadc059ad8d91f7e4a023106620d93abd23a"
-SRCREV_meta_pn-linux-yocto ?= "e2737075b79e4fc682e41051cf1c0bc47a47d502"
+SRCREV_machine_pn-linux-yocto ?= "2b412826bbeb4a16abe2ea74f2456ab880c6e3c1"
+SRCREV_meta_pn-linux-yocto ?= "212cae404e57ff9dc58c808035770d51325c3512"
 SRCREV_pn-linux-libc-headers-yocto ??= "2b412826bbeb4a16abe2ea74f2456ab880c6e3c1"
 SRCREV_pn-matchbox-config-gtk ??= "3ed74dfb7c57be088a5ab36e446c0ccde9fa1028"
 SRCREV_pn-matchbox-desktop-sato ??= "76"
-- 
1.7.0.4

[PATCH 0/1] linux-yocto: update routerstationpro and mpc8315e-rdb configuration

Bruce Ashfield <bruce.ashfield@...>

#1114

Richard/Saul,

Fixes [YOCTO #733, YOCTO #766, YOCTO: #801]

Our board configs were missing some values, this addresses
VFAT, USB and RTC for these two boards. I've sent the patch
against master, since the right branch wasn't completely
clear at the time of writing this up. Please cherry pick it
into the appropriate branch.

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@...>
---


Bruce Ashfield (1):
  linux-yocto: update machine configurations

 .../conf/distro/include/poky-default-revisions.inc |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

[ANNOUNCEMENT] Release of Board Support Packages for Intel Atom Processor E660

Elizabeth Flanagan <elizabeth.flanagan@...>

#1113

All,

I am pleased to announce the release of board support packages for systems based on the Intel® Atom(tm) Processor E660
with Intel® Platform Controller Hub EG20T Development Kit at:

http://yoctoproject.org/download/board-support-package-bsp-downloads/atom-e660-hub-eg20t

This BSP, also known as "Crown Bay", ships as an open system and allows maximum flexibility for changing hardware
configuration and peripherals.

You can find information about this kit by downloading the PDF document from http://edc.intel.com/Link.aspx?id=3878.
For information on the Intel® Atom(tm) Processor E660 see http://edc.intel.com/Platforms/Atom-E6xx/.  For general
information about Board Support Packages, see the Board Support Package (BSP) Developer's Guide at:

http://www.yoctoproject.org/sites/default/files/bsp-guide_7.pdf

We are releasing two versions of the BSP tarballs. Each tarball contains the meta-crownbay Yocto BSP layer and bootable
images.

The BSP versions available for the Crown Bay are:

- Crown Bay - This tarball is prefixed with the string 'crownbay'. It contains proprietary graphics binaries and
requires you to agree to a click-through license before you can download it. It is available from:

https://eula-downloads.yoctoproject.org/crownbay/crownbay-laverne-4.0.1

- Crown Bay no EMGD - This tarball is prefixed with the string 'crownbay-noemgd'. It does not contain any proprietary
information. You can download the tarball directly. The BSP uses fully open source generic vesa support.  As such, the
drivers are not optimized to take full advantage of the hardware as compared to the other BSP tarball. It is available from:

http://www.yoctoproject.org/downloads/yocto-0.9/machines/crownbay-noemgd-laverne-4.0.1.tar.bz2

For source files for the Crown Bay BSP images see:

http://autobuilder.yoctoproject.org/downloads/yocto-0.9/sources.


Release Notes
-------------
The following known issues exist for this BSP.

- BUGID# 725 - During a boot operation you are prompted with the question:
Found drive at /dev/sda.  Do you want to install poky there ? [y/n] Unrelated text might follow this prompt during the
install.  You can still see the prompt text but you might have to locate it above the unrelated text.  The actions [y/n]
are still valid and you need to enter your choice.

- BUGID# 738 - The icons in the green panel at the top of the screen are missing.  Consequently, the functions that are
accessible exclusively through that panel, such as switching between open applications and the desktop, do not work.
You must close an application to get to the desktop.


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

Using the term "Yocto"

Rifenbark, Scott M <scott.m.rifenbark@...>

#1112

Hi,

I am sending out this email to stimulate some thought or discussion on the use of the term “Yocto” and “The Yocto Project.”

Both terms are used throughout documentation, presentations, blog posts, and in speaking. The term “The Yocto Project” is actually trademarked by the Linux Foundation. And it is a reference to the overall effort around Dave Stewart’s group. Because this term is trademarked its written use needs to be somewhat standardized. The term “The Yocto Project” should be used whenever referring to the effort as a whole. It could be used as either a noun or an adjective. Examples:

· The Yocto Project is an effort to blah, blah, blah…. (noun)

· The Yocto Project Community does blah, blah, blah… (adjective)

Official announcements, communications, documentation should always use the term “The Yocto Project” when communicating the whole effort.

What about “Yocto?” As in “Yocto” this and “Yocto” that….

In more casual situations such as speaking, blog posts, emails it is natural that the whole effort is going to be referred to as “Yocto.”

Care should be used when using “Yocto” as an adjective. What exactly does “Yocto image” mean? What is a “Yocto kernel?” What is “Yocto metadata?”

Just some food for thought here…. Comments and discussion welcome.

Scott Rifenbark

Intel Corporation

Yocto Project Documentation

503.712.2702

503.341.0418 (cell)

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

Saul Wold <saul.wold@...>

#1111

On 03/01/2011 02:30 PM, Adrian Alonso wrote:
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@...>
---


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
Merged these into meta-xilinx

Thanks
	Sau!

Re: Could you help to have a look at BUG 660

Saul Wold <saul.wold@...>

#1110

On 03/02/2011 05:43 PM, Xu, Dongxiao wrote:
Hi Richard and Saul,

Could you help to have a review of BUG 660?

http://bugzilla.pokylinux.org/show_bug.cgi?id=660

BUG 660 is about missing kernel firmware in poky-image-minimal.

As from most of the machine configuration files in current poky, including
igep0030.conf, "kernel-modules" and "linux-firmware-sd8686" are part of
"MACHINE_EXTRA_RRECOMMENDS", like:

MACHINE_EXTRA_RRECOMMENDS = " kernel-modules linux-firmware-sd8686"

However for poky-image-minimal, only "MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS" is
included. If the kernel module and firmware files are indeed necessary for
successful boot, we can add them into minimal image.

Any comment on that?

Thanks,
DongxiaoDongxiao,

It seems that the igep machines have been moved to meta-extras now, which is the place for machines that are being depreciated.  If the bug
is just against igep then we can close this, if there is a more general situation, then firmware files that are required to boot need to be moved to the MACHINE_ESSENTIAL_EXTRA_RRECOMMEDS as that would be the right place.

If you want to fix the meta-extra/igep you can add the MACHINE_ESSENTIAL_EXTRA_RRCOOMENTS instead of MACHINE_EXTRA_RRECOMMEDS?


Sau!

Could you help to have a look at BUG 660

Xu, Dongxiao <dongxiao.xu@...>

#1109

Hi Richard and Saul,

Could you help to have a review of BUG 660?

http://bugzilla.pokylinux.org/show_bug.cgi?id=660

BUG 660 is about missing kernel firmware in poky-image-minimal.

As from most of the machine configuration files in current poky, including
igep0030.conf, "kernel-modules" and "linux-firmware-sd8686" are part of
"MACHINE_EXTRA_RRECOMMENDS", like:

MACHINE_EXTRA_RRECOMMENDS = " kernel-modules linux-firmware-sd8686"

However for poky-image-minimal, only "MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS" is
included. If the kernel module and firmware files are indeed necessary for
successful boot, we can add them into minimal image.

Any comment on that?

Thanks,
Dongxiao

[PATCH 5/5] linux-xilinx: update kernel version

Adrian Alonso <aalonso@...>

#1108

* Sync kernel version to 2.6.37 from xilinx repo
* Add linux.inc to meta-xilinx layer (deprecated in main layer).
* Increase PR

Signed-off-by: Adrian Alonso <aalonso@...>
---
 recipes-kernel/linux/linux-xilinx_git.bb |    8 +-
 recipes-kernel/linux/linux.inc           |   95 ++++++++++++++++++++++++++++++
 2 files changed, 99 insertions(+), 4 deletions(-)
 create mode 100644 recipes-kernel/linux/linux.inc

diff --git a/recipes-kernel/linux/linux-xilinx_git.bb b/recipes-kernel/linux/linux-xilinx_git.bb
index 1d15437..8ef2d5a 100644
--- a/recipes-kernel/linux/linux-xilinx_git.bb
+++ b/recipes-kernel/linux/linux-xilinx_git.bb
@@ -1,4 +1,4 @@
-require recipes-kernel/linux/linux.inc
+require linux.inc
 
 DESCRIPTION = "Linux kernel for Xilinx platforms"
 
@@ -10,9 +10,9 @@ DEFAULT_PREFERENCE_virtex5 = "1"
 LICENSE = "GPL"
 LIC_FILES_CHKSUM = "file://COPYING;md5=d7810fab7487fb0aad327b76f1be7cd7"
 
-TAG="xilinx_v2.6.37-rc4"
-PV = "2.6.37.4"
-PR = "r5"
+TAG="xilinx_v2.6.37"
+PV = "2.6.37"
+PR = "r6"
 
 SRCREV = "${TAG}"
 SRC_URI = "git://git.xilinx.com/linux-2.6-xlnx.git;protocol=git \
diff --git a/recipes-kernel/linux/linux.inc b/recipes-kernel/linux/linux.inc
new file mode 100644
index 0000000..f0b47da
--- /dev/null
+++ b/recipes-kernel/linux/linux.inc
@@ -0,0 +1,95 @@
+DESCRIPTION = "Linux Kernel"
+SECTION = "kernel"
+LICENSE = "GPLv2"
+
+LIC_FILES_CHKSUM = "file://COPYING;md5=d7810fab7487fb0aad327b76f1be7cd7"
+
+inherit kernel
+require linux-dtb.inc
+
+DEPENDS_append_em-x270 = " mtd-utils "
+
+RPSRC = "http://www.rpsys.net/openzaurus/patches/archive"
+
+# Specify the commandline for your device
+
+#boot from mmc
+CMDLINE_at91sam9263ek = "mem=64M console=ttyS0,115200 root=/dev/mmcblk0p1 rootfstype=ext2 rootdelay=5"
+#boot from nfs
+#CMDLINE_at91sam9263ek = "mem=64M console=ttyS0,115200 root=301 root=/dev/nfs nfsroot=172.20.3.1:/data/at91 ip=172.20.0.5:::255.255.0.0"
+
+do_configure_prepend() {
+        echo "" > ${S}/.config
+
+        #
+        # logo support, if you supply logo_linux_clut224.ppm in SRC_URI, then it's going to be used
+        #
+        if [ -e ${WORKDIR}/logo_linux_clut224.ppm ]; then
+                install -m 0644 ${WORKDIR}/logo_linux_clut224.ppm drivers/video/logo/logo_linux_clut224.ppm
+                echo "CONFIG_LOGO=y"                    >> ${S}/.config
+                echo "CONFIG_LOGO_LINUX_CLUT224=y"      >> ${S}/.config
+        fi
+
+        #
+        # oabi / eabi support
+        #
+        if [ "${TARGET_OS}" = "linux-gnueabi" -o  "${TARGET_OS}" = "linux-uclibcgnueabi" ]; then
+                echo "CONFIG_AEABI=y"                   >> ${S}/.config
+                echo "# CONFIG_OABI_COMPAT is not set"             >> ${S}/.config
+        else
+                echo "# CONFIG_AEABI is not set"        >> ${S}/.config
+                echo "# CONFIG_OABI_COMPAT is not set"  >> ${S}/.config
+        fi
+
+        echo "CONFIG_CMDLINE=\"${CMDLINE}\"" >> ${S}/.config
+
+        sed -e '/CONFIG_AEABI/d' \
+            -e '/CONFIG_OABI_COMPAT=/d' \
+            -e '/CONFIG_CMDLINE=/d' \
+            -e '/CONFIG_LOGO=/d' \
+            -e '/CONFIG_LOGO_LINUX_CLUT224=/d' \
+            < '${WORKDIR}/defconfig' >>'${S}/.config'
+
+        #
+        # root-over-nfs-over-usb-eth support. Limited, but should cover some cases.
+        # Enable this by setting a proper CMDLINE_NFSROOT_USB.
+        #
+        if [ ! -z "${CMDLINE_NFSROOT_USB}" ]; then
+                oenote "Configuring the kernel for root-over-nfs-over-usb-eth with CMDLINE ${CMDLINE_NFSROOT_USB}"
+                sed -e '/CONFIG_INET/d' \
+                    -e '/CONFIG_IP_PNP=/d' \
+                    -e '/CONFIG_USB_GADGET=/d' \
+                    -e '/CONFIG_USB_GADGET_SELECTED=/d' \
+                    -e '/CONFIG_USB_ETH=/d' \
+                    -e '/CONFIG_NFS_FS=/d' \
+                    -e '/CONFIG_ROOT_NFS=/d' \
+                    -e '/CONFIG_CMDLINE=/d' \
+                    -i ${S}/.config
+                echo "CONFIG_INET=y"                     >> ${S}/.config
+                echo "CONFIG_IP_PNP=y"                   >> ${S}/.config
+                echo "CONFIG_USB_GADGET=y"               >> ${S}/.config
+                echo "CONFIG_USB_GADGET_SELECTED=y"      >> ${S}/.config
+                echo "CONFIG_USB_ETH=y"                  >> ${S}/.config
+                echo "CONFIG_NFS_FS=y"                   >> ${S}/.config
+                echo "CONFIG_ROOT_NFS=y"                 >> ${S}/.config
+                echo "CONFIG_CMDLINE=\"${CMDLINE_NFSROOT_USB}\"" >> ${S}/.config
+        fi
+        yes '' | oe_runmake oldconfig
+}
+
+
+
+do_install_prepend() {
+        if [ -f arch/${ARCH}/boot/Image ] && [ ! -f arch/${ARCH}/boot/uImage ]; then
+             ln -f arch/${ARCH}/boot/Image arch/${ARCH}/boot/uImage
+        fi
+
+        if test -e arch/${ARCH}/boot/images/uImage ; then
+             ln -f arch/${ARCH}/boot/images/uImage arch/${ARCH}/boot/uImage
+        fi
+
+        if test -e arch/${ARCH}/kernel/vmlinux.lds ; then
+             ln -f arch/${ARCH}/kernel/vmlinux.lds arch/${ARCH}/boot/vmlinux
+        fi
+}
+
-- 
1.7.4

[PATCH 4/5] openssl: Fix files search path

Adrian Alonso <aalonso@...>

#1107

* Fix FILESPATH, recipe not finding layer patch
  rename PN to files

Signed-off-by: Adrian Alonso <aalonso@...>
---
 ...enssl-linux-gnueabi-powerpc-configuration.patch |    0
 .../openssl/openssl_0.9.8p.bbappend                |    5 ++---
 2 files changed, 2 insertions(+), 3 deletions(-)
 rename recipes-connectivity/openssl/{openssl-0.9.8p => files}/openssl-linux-gnueabi-powerpc-configuration.patch (100%)

diff --git a/recipes-connectivity/openssl/openssl-0.9.8p/openssl-linux-gnueabi-powerpc-configuration.patch b/recipes-connectivity/openssl/files/openssl-linux-gnueabi-powerpc-configuration.patch
similarity index 100%
rename from recipes-connectivity/openssl/openssl-0.9.8p/openssl-linux-gnueabi-powerpc-configuration.patch
rename to recipes-connectivity/openssl/files/openssl-linux-gnueabi-powerpc-configuration.patch
diff --git a/recipes-connectivity/openssl/openssl_0.9.8p.bbappend b/recipes-connectivity/openssl/openssl_0.9.8p.bbappend
index 381f31c..91f7a85 100644
--- a/recipes-connectivity/openssl/openssl_0.9.8p.bbappend
+++ b/recipes-connectivity/openssl/openssl_0.9.8p.bbappend
@@ -1,5 +1,4 @@
 THISDIR := "${@os.path.dirname(bb.data.getVar('FILE', d, True))}"
-FILESPATH =. "${@base_set_filespath(["${THISDIR}/${PN}"], d)}:"
+FILESPATH =. "${@base_set_filespath(["${THISDIR}/files"], d)}:"
 
-SRC_URI_append += "file://openssl-linux-gnueabi-powerpc-configuration.patch \
-                  "
+SRC_URI_append += "file://openssl-linux-gnueabi-powerpc-configuration.patch"
-- 
1.7.4

[PATCH 3/5] u-boot-xilinx: fix missing license definition

Adrian Alonso <aalonso@...>

#1106

* Fix missing LICENSE definition
* Update u-boot-xilinx preferred version (sync with xilinx repo).
* Increase PR

Signed-off-by: Adrian Alonso <aalonso@...>
---
 recipes-bsp/uboot/u-boot-xilinx_git.bb |    6 ++++--
 1 files changed, 4 insertions(+), 2 deletions(-)

diff --git a/recipes-bsp/uboot/u-boot-xilinx_git.bb b/recipes-bsp/uboot/u-boot-xilinx_git.bb
index 49f5ad4..2483c4b 100644
--- a/recipes-bsp/uboot/u-boot-xilinx_git.bb
+++ b/recipes-bsp/uboot/u-boot-xilinx_git.bb
@@ -1,12 +1,14 @@
 require recipes-bsp/uboot/u-boot.inc
-PR = "r7"
+PR = "r8"
 THISDIR := "${@os.path.dirname(bb.data.getVar('FILE', d, True))}"
 FILESPATH =. "${@base_set_filespath(["${THISDIR}/files"], d)}:"
+LICENSE = "GPLv2+"
 LIC_FILES_CHKSUM = "file://COPYING;md5=4c6cde5df68eff615d36789dc18edd3b"
 
 EXTRA_OEMAKE = "CROSS_COMPILE=${TARGET_PREFIX} OPTFLAGS='-O2'"
 BRANCH="master"
-TAG="e094f2479ea339d7f48b6826f06f0be4984d9a98"
+#TAG="e094f2479ea339d7f48b6826f06f0be4984d9a98"
+TAG="d49297009f402a20dd59b21212975dd3d79ee6fd"
 SRC_URI = "git://git.xilinx.com/u-boot-xlnx.git;branch=${BRANCH};protocol=git \
            file://uboot-remove-inline-qualifier-from-show_boot_progres.patch \
            file://ml405-add-uartlite-config-options.patch \
-- 
1.7.4

[PATCH 2/5] virtex5: add u-boot image to rootfs

Adrian Alonso <aalonso@...>

#1105

* 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@...>
---
 conf/machine/virtex5.conf |    2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)

diff --git a/conf/machine/virtex5.conf b/conf/machine/virtex5.conf
index 232ab6a..b9ea61e 100644
--- a/conf/machine/virtex5.conf
+++ b/conf/machine/virtex5.conf
@@ -13,6 +13,8 @@ require conf/machine/include/tune-ppc440.inc
 #ASSUME_PROVIDED += "virtual/kernel"
 PREFERRED_PROVIDER_virtual/kernel = "linux-xilinx"
 PREFERRED_VERSION_u-boot_virtex5 = "u-boot-xilinx"
+# Add u-boot image
+EXTRA_IMAGEDEPENDS += "u-boot-xilinx"
 
 KERNEL_IMAGETYPE = "uImage"
 
-- 
1.7.4

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

Adrian Alonso <aalonso@...>

#1104

* 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@...>
---
 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@...>

#1103

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@...>
---


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