Date   

Re: yocto tools on a nokia n800

Bruce Ashfield <bruce.ashfield@...>
 

On 10-10-30 12:20 PM, Tom Zanussi wrote:
On Fri, 2010-10-29 at 04:50 -0700, tiagoprn wrote:
Hello everyone!

I have a question. I have just read about the yocto/poky projects and
here I am with a hope. :)

I have a nokia n800 (an internet tablet abandoned by Nokia just about
2 years ago).

With poky/yocto project tools, is it possible to install a linux
toolchain with X and the touchscreen/wireless components working, for
an example, in a SD Card and boot my device into it?

I'm anxious for that.
Hi,

It looks like yocto already has support for the n800 - there's this
entry in local.conf:

# Other supported machines
.
.






#MACHINE ?= "nokia800"


and see this section in README.hardware:

'Nokia 770/N800/N810 Internet Tablets (nokia770 and nokia800)'

which says:

"The nokia800 images and kernel will run on both the N800 and N810"

Sounds like what you're looking for...
The rest of the config has been moved to meta-extras, and
we'd need to do a bit of kernel work, but it has worked in the past, and could work again in the future.

In other words 'I agree'.

Cheers,

Bruce


Tom




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


Some photos of the four architecture demo

David Stewart
 

Check out http://www.yoctoproject.org/blogs/davest/2010/10/7/four-architectures-grooving-together, my latest post to the Yocto Project blog. Some photos there of the UPnP demo.

 

I also plan to post one up showing a little of the sausage-making… just a little…

 

Let me know what you think.

 

Dave


Re: yocto tools on a nokia n800

Tom Zanussi <tom.zanussi@...>
 

On Fri, 2010-10-29 at 04:50 -0700, tiagoprn wrote:
Hello everyone!

I have a question. I have just read about the yocto/poky projects and
here I am with a hope. :)

I have a nokia n800 (an internet tablet abandoned by Nokia just about
2 years ago).

With poky/yocto project tools, is it possible to install a linux
toolchain with X and the touchscreen/wireless components working, for
an example, in a SD Card and boot my device into it?

I'm anxious for that.
Hi,

It looks like yocto already has support for the n800 - there's this
entry in local.conf:

# Other supported machines
.
.






#MACHINE ?= "nokia800"


and see this section in README.hardware:

'Nokia 770/N800/N810 Internet Tablets (nokia770 and nokia800)'

which says:

"The nokia800 images and kernel will run on both the N800 and N810"

Sounds like what you're looking for...

Tom


World build state

Saul Wold <sgw@...>
 

Folks,

I just completed a world build and the situation is not that bad currently, the summary of the failures are listed below.


libsndfile1_1.0.17
- Failed in compilation of flac.c
loudmouth_1.4.0
- Failed in compilation of asyncns.c
- asyncns.c:159:14: error: static declaration of 'strndup' follows non-static declaration
plugin-evolution2_0.36
- Failed in do_configure
CMake Error at cmake/modules/FindEPackage.cmake:166 (MESSAGE):
Evolution Data Server not found.
Call Stack (most recent call first):
CMakeLists.txt:9 (FIND_PACKAGE)
clutter-gtk-0.10_git
- Failed during linking
ohm_git
- Failed during compilation of ohm-plugin-dpms.c
- missing X11/extensions/dpmsstr.h
git_1.7.2.1
- Failed during do_configure
- Need a configure update for checking of "fopen'ed directory"
openswan_2.4.7
- Failed during compilation of optionsfrom.c
- optionsfrom.c:34:14: error: conflicting types for 'getline'
clutter-gtk-1.0_git
- Failed during linking
gnome-terminal_2.26.3
- Failed during linking
matchbox-themes-extra_svn
- Failed during install with an overwrite error
- will not overwrite just-created `/intel/poky/demo/build/tmp/work/core2-poky-linux/matchbox-themes-extra-0.3+svnr1524-r0/image/usr/share/themes/mbcrystal/matchbox/theme.desktop' with `theme.desktop'
libapplewm_1.0.0
- Failed during compilation of applewm.c
- missing X11/extensions/applewmstr.h
telepathy-idle_0.1.2
- Failed during compilation of idle-connection.c


Bugs will be files soon on these items.

Sau!

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


Bugzilla Changes

Saul Wold <sgw@...>
 

We need to review the existing Bugzilla and update the Products and Categories to reflect the projects correctly. Please review this email and make comments, suggestions for moving forward with a better Bugzilla categorization.

Currently we have "Core OS" with the following Components:
General
Graphics Driver
Kernel
Tool Chain

Along with "Poky" which contains:
General
SDK Tools

There are also product categories for "Runtime Distribution", "Sato" and "SDK Plugins". Along with other infrastructure items.

I would propose that we clearly define the some new products and move bugs as appropriate:

Poky Build System - for Poky class and configuration issues
User Space - for user space, patching and runtime failures
Tool Chain - break it down to compiler, tools, libraries, and general
Kernel - Break it down to Arch / Config components
SDK - For all SDK related issues, have components for plugin, tools, ...
Sato - as it exists today
Runtime Distribution- Delete this, we are not a distro (no bugs now)

Additionally, there is other discussion about Poky Test components for the standards tests such as LSB, LTP, Posix.

We will need to add Product Categories for other Yocto Projects that do not have bugzilla yet.

Finally we need to update the Bugzilla Interface to be Yocto Project, changing naming as appropriate.

Please take a few minutes to review this and give some feedback.


Thanks

Sau!

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


World Package List

Saul G. Wold <sgw@...>
 

Folks,

Please find attached a list of packages that are in the world build but not currently contained in any tasks or images. This is an early warning that we are putting some of these up for consideration for relocation.

As we work through this determination process, we will document it to use as in the future for package relocation. There maybe recipes in this list that will move into some specific tasks or be moved to an external layer.

Please review this spreadsheet and provide any input for these packages.

Thanks
Sau!

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


Re: yocto tools on a nokia n800

Bruce Ashfield <bruce.ashfield@...>
 

On 10-10-29 07:50 AM, tiagoprn wrote:
Hello everyone!

I have a question. I have just read about the yocto/poky projects and here I am with a hope. :)

I have a nokia n800 (an internet tablet abandoned by Nokia just about 2 years ago).

With poky/yocto project tools, is it possible to install a linux toolchain with X and the touchscreen/wireless components working, for an example, in a SD Card and boot my device into it?
I can comment on some of this from the kernel point of view,
I'll leave others to comment on platform/project/userspace
issues.

It is definitely possible to enable (basic or more capabilities)
in the N800 (in particular since most of the required support
is mainline) in the yocto kernel (or other). We could extend
the common set of features and sanity to the n800 and then
enable peripherals or boot methods .. it all depends on the
capabilities and interest.

maintable/doable in the kernel and userspace has the required
capabilities (from my point of view), so this is something
that could come back (others can comment more on the previous
support), with a little bit of assistance.

Cheers,

Bruce


I'm anxious for that.

Thanks for your support.

Regard,


yocto tools on a nokia n800

tiagoprn <tiagoprn@...>
 

Hello everyone!
 
 I have a question. I have just read about the yocto/poky projects and here I am with a hope. :)
 
 I have a nokia n800 (an internet tablet abandoned by Nokia just about 2 years ago).
 
 With poky/yocto project tools, is it possible to install a linux toolchain with X and the touchscreen/wireless components working, for an example, in a SD Card and boot my device into it?
 
 I'm anxious for that.
 
 Thanks for your support.
 
 Regard,
 

--
***
TIAGOPRN
Desenvolvedor Web, Linux e Windows
(Django, Python, Delphi, Lazarus, MySQL, SQLite)
E-mail: tiagoprn@...
Blog: http://tgplima.net84.net
LinkedIn (profile público): http://br.linkedin.com/in/tiagoparanhoslima
twitter: https://twitter.com/tiagoprn


Re: Some data collection and analysis on poky performance

Tian, Kevin <kevin.tian@...>
 

From: Qing He
Sent: Wednesday, October 27, 2010 5:23 PM

As we know, many of us have experienced slow builds of recent poky,
and it also takes larger disk space. This affects user exprience thus
is one of our directions in 1.0.
thanks Qing, that's a great start.


To find the problems leading to performance issues, I tried some
profiling on poky builds, below is a very brief summary of the data.
I profiled poky-image-minimal of both the current master branch and
green release, with similar parameters (4 CPUs) on NHM. Note that
both rpm and ipk packages are built for current master branch, while
oonly ipk packages are built for green release


I. some stats
1. recipes (including -native)
green release:
recipes built: 76
tasks run: 998
master:
recipes built: 133
tasks run: 1600
could you get a compare list which recipes have been newly added? I thought that
minimal image was seldom changed...


2. time
green release:
real: 28m7s
user: 57m45s
sys: 9m41s
user+sys: 67m26s
master:
real: 66m39s
user: 152m17s
sys: 27m37s
user+sys: 179m54s

3. space (haven't analyze though)
green release: 7.8G
master: 26.6G
I recall that RP mentioned debug symbol is enabled in current master, but I'm not sure
whether green has done the same. You may double-confirm that part first.



II. profiling
I tried a brief profile by collecting the time used for every task, so
we can scrutinize the result from a microscopic point of view. I'm still
looking into the full result, but there's something of immediate
attention.

In master, hardly any task consume less than 1.3s, this is quite
surprising, since many tasks like do_patch virtually do nothing, while
in the green release, these tasks may simply consume 0.1~0.2s. A deeper
investigation shows that this large overhead goes to bitbake-runtask,
the bitbake config and cache mechanism is executed for every task,
considerably increased the time. The overhead introduced solely by
this is around 1600*1.3=2080s, approximately 35 minutes (user+sys).
It's said this change comes from pseudo integration. Now it's time for us to
revisit this implementation then. RP can have more insights here.


Also, we should count the additional rpm packaging system,
do_package_write_rpm costs around 1400s, (excluding 1.3s per task,
btw, this is about 50% slower than do_package_write_ipk, in average),
that's around 23 minutes.

Roughly considering that the build time is proportional to recipes
count, we can try to estimate master build time from green release:
67 * (76 / 133) + 35 + 23 = 175
very close to the real time consuming (although somewhat too closed...),
so possibly the above two are the most significant time consumers
in the slowness of current poky
above are all good findings!

Thanks
Kevin


Some data collection and analysis on poky performance

Qing He <qing.he@...>
 

As we know, many of us have experienced slow builds of recent poky,
and it also takes larger disk space. This affects user exprience thus
is one of our directions in 1.0.

To find the problems leading to performance issues, I tried some
profiling on poky builds, below is a very brief summary of the data.
I profiled poky-image-minimal of both the current master branch and
green release, with similar parameters (4 CPUs) on NHM. Note that
both rpm and ipk packages are built for current master branch, while
oonly ipk packages are built for green release


I. some stats
1. recipes (including -native)
green release:
recipes built: 76
tasks run: 998
master:
recipes built: 133
tasks run: 1600

2. time
green release:
real: 28m7s
user: 57m45s
sys: 9m41s
user+sys: 67m26s
master:
real: 66m39s
user: 152m17s
sys: 27m37s
user+sys: 179m54s

3. space (haven't analyze though)
green release: 7.8G
master: 26.6G


II. profiling
I tried a brief profile by collecting the time used for every task, so
we can scrutinize the result from a microscopic point of view. I'm still
looking into the full result, but there's something of immediate
attention.

In master, hardly any task consume less than 1.3s, this is quite
surprising, since many tasks like do_patch virtually do nothing, while
in the green release, these tasks may simply consume 0.1~0.2s. A deeper
investigation shows that this large overhead goes to bitbake-runtask,
the bitbake config and cache mechanism is executed for every task,
considerably increased the time. The overhead introduced solely by
this is around 1600*1.3=2080s, approximately 35 minutes (user+sys).

Also, we should count the additional rpm packaging system,
do_package_write_rpm costs around 1400s, (excluding 1.3s per task,
btw, this is about 50% slower than do_package_write_ipk, in average),
that's around 23 minutes.

Roughly considering that the build time is proportional to recipes
count, we can try to estimate master build time from green release:
67 * (76 / 133) + 35 + 23 = 175
very close to the real time consuming (although somewhat too closed...),
so possibly the above two are the most significant time consumers
in the slowness of current poky

Thanks,
Qing


[PATCH] package.bbclass: make sure 'sysroots' created before lockfile

Tian, Kevin <kevin.tian@...>
 

meta/classes/package.bbclass | 1 +
1 file changed, 1 insertion(+)

commit 2cd6d6d7957cf46114c8b25ed13e6f8030cd9c06
Author: Kevin Tian <kevin.tian@intel.com>
Date: Tue Oct 26 15:54:43 2010 +0800

package.bbclass: make sure 'sysroots' created before lockfile

package sstate requires a lock under sysroots/, which however may not be
created when sstate_setscene functions are executed and then causes failures.
here we make sure 'sysroots' created before do_package_setscene is executed.

Signed-off-by: Kevin Tian <kevin.tian@intel.com>
Pull URL: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=tk/master

Thanks
Kevin


Thanks, and buckle up!

David Stewart
 

All –

 

First of all, I want to thank you guys so much for all of the hard work you put in to bring us to this point, the first public launch of the Yocto Project. There is something really powerful when a team of talented people gathers together to do something special and then pulls it off. I know when we first put our eyes on October 17, 2010 and decided to launch our baby then, there were a few of us who quaked in our boots a bit at the thought of pulling off something like this.

 

But we did it! And it’s awesome to behold. It’s not perfect, but we have a lot to be proud about.

 

In my mind’s eye, I can think forward to a time when your code will have an impact on many people’s lives – whether it’s saving lives with medical devices, operating airplanes or cars safely, generating and routing energy efficiently or routing packets in your favorite website’s data center. Think about how many lives you can touch! Pretty amazing stuff.

 

So thank you, from my heart. I feel privileged to have worked with you.

 

Secondly, I know that tomorrow when the site goes live and announcements go out, I hope people will like our baby, and will tell us so. But you know, there are some people who could be quite critical, and criticize everything from our use of Python to package selection to the fonts on our web sites.  If you have not been through one of these launches before, this is simply a normal part of life in an open source project. When you get your stuff out there for people to see and interact with, you open yourself up to criticism too.

 

So don’t take anything as a personal insult. I try to look at all of it as feedback from a valuable person, and in my heart I do thank them for it.

 

Dave


Sanity test report with milestone build 20101024

xianchao zhang <xianchao.zhang@...>
 

Hi jiajun,

This is the Sanity Test Report for M4 build 20101024. Changhui and I  are responsible for qemumips/arm/ppc testing.

For zypper test cases with qemuarm, since create repo fails in my host, the related cases were not tested.

Test Summary

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

Target

Total TCs

Not Run

Passed

Failed

Not testable (Blocked)

Completed Rate [%]

Pass rate of total [%]

Qemumips Sato

19

0

16

3

0

100

84.21

Qemumips SDK

26

2

21

3

0

92.31

80.77

Qemuppc Sato

17

5

11

1

5

70.59

64.71

Qemuppc SDK

24

7

16

1

5

70.83

66.67

Qemuarm Sato

19

3

16

0

3

84.21

84.21

Qemuarm SDK

26

5

21

0

3

80.77

80.77

Total

131

22

101

8

16

83.21

77.10


Images

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

http://autobuilder.pokylinux.org/milestone/20101024/

Best Regards, xianchao


Re: Did not find big problems for today's Rc4 (x86/arm) toolchain sdk related images

Lu, Lianhao <lianhao.lu@...>
 

I did the SDK part test of RC4a images on qemuppc, qemumips, and BlackSand. No new bugs found compared to the test of RC3.

 

Best Regards,

-Lianhao

 

From: yocto-bounces@... [mailto:yocto-bounces@...] On Behalf Of Tian, Kevin
Sent: Tuesday, October 26, 2010 8:39 AM
To: yocto@...
Subject: [yocto] Did not find big problems for today's Rc4 (x86/arm) toolchain sdk related images

 

FYI. SDK/toolchain part behaves well from RC4.

 

Thanks

Kevin

 

From: Wu, Tong
Sent: Monday, October 25, 2010 8:39 PM
To: Ke, Liping; Tian, Kevin; Yu, Ke; Lu, Lianhao
Subject: On behalf of Liping {Did not find big problems for today's Rc4 (x86/arm) toolchain sdk related images]

 

Hi, all

I did not bring my laptop, and can’t connect webmail, so use this mail box to report the result.

 

X86 sdk image, sdk toolchain, ide-support has been built successfully from clean-up folder at last.

 

X86/arm qemu run successfully.

 

Crosstool chain could compile the c/c++ project successfully in the host.

 

Qemu arm/x86 could compile c/c++ project successfully.

 

Thanks& Regards,

criping


Did not find big problems for today's Rc4 (x86/arm) toolchain sdk related images

Tian, Kevin <kevin.tian@...>
 

FYI. SDK/toolchain part behaves well from RC4.

 

Thanks

Kevin

 

From: Wu, Tong
Sent: Monday, October 25, 2010 8:39 PM
To: Ke, Liping; Tian, Kevin; Yu, Ke; Lu, Lianhao
Subject: On behalf of Liping {Did not find big problems for today's Rc4 (x86/arm) toolchain sdk related images]

 

Hi, all

I did not bring my laptop, and can’t connect webmail, so use this mail box to report the result.

 

X86 sdk image, sdk toolchain, ide-support has been built successfully from clean-up folder at last.

 

X86/arm qemu run successfully.

 

Crosstool chain could compile the c/c++ project successfully in the host.

 

Qemu arm/x86 could compile c/c++ project successfully.

 

Thanks& Regards,

criping


Test Report for Yocto M4 20101024 Build

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

Hi all,

       This is the Partial Test Report for M4 build 20101024(RC4a). Thanks for Dexuan’s help on testing. We finished most testing for IA targets. There is no regression issue found. 2 new normal issues are found. For non-IA targets, Changhui is still downloading images and will give full testing tomorrow. Then I gave a quick try for sato/sdk qemuarm/ppc/mips with RC4a builds. There is no new issue found on my side till now, no issue with booting/networking/basic system usage. So from QA’s view, RC4a has the same quality with RC3(with no regression and critical bugs).

 

Test Summary

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

Target

Total TCs

Not Run

Passed

Failed

Not testable (Blocked)

Completed Rate [%]

Pass rate of total [%]

Netbook SDK

76

19

54

3 (bug 491, bug 502)

0

75

71.05

eMenlow SDK

69

32

34

3 (bug 503, bug 491, bug 160, bug 310)

2 (bug 503)

53.62

49.28

Qemux86-64 Sato

19

0

19

0

0

100

100

Qemux86-64 SDK

26

2

24

0

0

92.31

92.31

Qemux86 Sato

19

0

19

0

0

100

100

Qemux86 SDK

26

2

24

0

0

92.31

92.31

* To check detail test result, you can login testlink with username/password(guest/guest) first. Then click hyperlinks in above table.

** For Netbook/E-menlow, testing is focused on sdk image.

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

 

Images

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

http://yoctobuild01.jf.intel.com/milestone/20101024/

http://autobuilder.pokylinux.org/milestone/20101024/

 

Issue Summary

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

New Bugs:

1.       Xorg and matchbox-window will SegFault when there are too many windows

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

2.       "rpm -e libnss-mdns" gets error

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

 

Best Regards,

Jiajun


Poky weekly bug trend charts -- WW43

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

Hi all,
This is the Poky weekly bug trend charts for last week (WW43). The open bug number increased to 128. 22 bugs are marked as fixed in last week.
The 1st chart indicates the total open bug number. The 2nd chart indicates the new bug submission and bug fixing count every week.

Best Regards,
Jiajun


Re: RC3 vs RC4a

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

From: Stewart, David C
Sent: Saturday, October 23, 2010 6:48 AM

We have an RC3 which we feel confident in based on our no-nogo launch
decision.

However, there are a handful of issues which are not critical but would
be desirable to address them - for example, having to do with errors
being "fatal" which are not, etc.

So I have asked Saul to create an RC4a with these patched in. Would
like Sanity and BAT tests run on RC4a to see if we should ship it, or
with stick with RC3.

RP - will complete the patch tonight.
Saul - will complete the RC4a build by 5PM Sunday (Pacific) Kevin and
Jiajun and whole team - test this build as much as you have time for.
OK, we'll try latest RC4a and report any new issues if seen.
QA will try as more as possible and send out result today.

Thanks
Kevin


Late Monday, we will decide whether to go with the RC3 build or RC4a build.

Dave
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.pokylinux.org/listinfo/yocto
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.pokylinux.org/listinfo/yocto
Best Regards,
Jiajun


Re: RC3 vs RC4a

Tian, Kevin <kevin.tian@...>
 

From: Stewart, David C
Sent: Saturday, October 23, 2010 6:48 AM

We have an RC3 which we feel confident in based on our no-nogo launch decision.

However, there are a handful of issues which are not critical but would be desirable to
address them - for example, having to do with errors being "fatal" which are not, etc.

So I have asked Saul to create an RC4a with these patched in. Would like Sanity and BAT
tests run on RC4a to see if we should ship it, or with stick with RC3.

RP - will complete the patch tonight.
Saul - will complete the RC4a build by 5PM Sunday (Pacific)
Kevin and Jiajun and whole team - test this build as much as you have time for.
OK, we'll try latest RC4a and report any new issues if seen.

Thanks
Kevin


Late Monday, we will decide whether to go with the RC3 build or RC4a build.

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


Re: RC3 vs RC4a

Saul G. Wold <sgw@...>
 

On 10/22/2010 03:48 PM, Stewart, David C wrote:
We have an RC3 which we feel confident in based on our no-nogo launch decision.

However, there are a handful of issues which are not critical but would be desirable to address them - for example, having to do with errors being "fatal" which are not, etc.

So I have asked Saul to create an RC4a with these patched in. Would like Sanity and BAT tests run on RC4a to see if we should ship it, or with stick with RC3.

RP - will complete the patch tonight.
Saul - will complete the RC4a build by 5PM Sunday (Pacific)
The build has been running overnight and should be complete, the images are in the standard location on the internal and external autobuilder dated 20101024.

http://autobuilder.pokylinux.org/milestone/20101024/


Kevin and Jiajun and whole team - test this build as much as you have time for.
Please pass this request to the Windriver team also as I am not sure if they are on the list


Late Monday, we will decide whether to go with the RC3 build or RC4a build.
Once we (Jessica and I) get through Heathrow and I get a phone card (I hope), I will call Richard. If it's approved, Scott G. can move the bits to the yoctoproject.org machine.

Sau!



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