[yocto] Where is the poky version information stored?

2012-08-27 Thread Elvis Dowson
Hi, Is the poky version information stored in a particular file? I'd like to create a log tag in my git repo, and prefix it with the poky version. Best regards, Elvis Dowson ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoprojec

Re: [yocto] Documentation improvement

2012-08-27 Thread Rifenbark, Scott M
Jim, I am addressing issues in my email box (bottom up) and was not sure if I ever closed this one with you. I have made changes to the "Creating Configuration Fragments" section in the YP Development Manual "latest" version (http://www.yoctoproject.org/docs/latest/dev-manual/dev-manual.html#c

Re: [yocto] Where is the poky version information stored?

2012-08-27 Thread Khem Raj
On Mon, Aug 27, 2012 at 8:36 AM, Elvis Dowson wrote: > Hi, >Is the poky version information stored in a particular file? I'd like > to create a log tag in my git repo, and prefix it with the poky version. > I guess DISTRO_VERSION is what you can use, which is defined in conf/distro/poky.

Re: [yocto] 1.3 M3 Full Pass test results

2012-08-27 Thread Liu, Song
Hi Laurentiu, Do you have any comment on the performance question Richard asked? I know your team is using a machine with different configuration from the one used by the Shanghai team. The performance figure from the Shanghai team has been hovering around 110 mins. That's the case for 1.2 rel

Re: [yocto] 1.3 M3 Full Pass test results

2012-08-27 Thread Serban, Laurentiu
Hello guys, I am sorry I did not notice the last line in the e-mail. When we ran the performance testing we pre-downloaded all the sources, because last week had a lot of connectivity issues. I mentioned in the e-mail that the build time refers to an image built after all the sources were downl

Re: [yocto] Request for photos

2012-08-27 Thread Stewart, David C
All - still would like to include as many pictures as I can of real products using the Yocto Project. Have not heard any... do you have a photo you can send me urgently? (Otherwise I will just make stuff up, and you don't want me to do that...) :-) Dave >-Original Message- >From: yoct

[yocto] Agenda: Yocto Project Technical Team Meeting - Tuesday, August 28, 2012 8:00 AM-9:00 AM (UTC-08:00) Pacific Time (US & Canada).

2012-08-27 Thread Liu, Song
Agenda:   * Opens collection - 5 min (Song) * Yocto 1.3 M3 release readiness (All) https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.3_Status#Milestone_3 https://wiki.yoctoproject.org/wiki/Yocto_1.3_Milestone_Test_Report (M3 report is at the bottom of the page) * Yocto 1.3 status - 10 min

[yocto] Xorg keyboard not working

2012-08-27 Thread Chris Tapp
I've got a system that has a working console and four virtual terminals. I can start X and run an application using /usr/bin/xinit /usr/sbin/xinitrc -- /usr/bin/Xorg The application runs fine and is expected to run with no user interaction. Keyboard input is sometimes needed to either kill the

[yocto] Poky 1.3_M3 branch does not work with linux-yocto 3.0 kernel ?

2012-08-27 Thread Saxena, Rahul
Hi, I am building a BSP (meta-cedartrail) using 1.3 M3 branch of Poky. When I try to boot a image such as core-image-sato, I get kernel panic and errors such as: VFS: Cannot open root device "ram0" or unkown-block(0,0) Please append a correct "root=" boot option; here are the available pa

Re: [yocto] 1.3 M3 Full Pass test results

2012-08-27 Thread Xu, Jiajun
We used to get 115m and 127m for 1.3 M1 and M2 on our test machine. > Hello guys, > > I am sorry I did not notice the last line in the e-mail. > > When we ran the performance testing we pre-downloaded all the sources, > because last week had a lot of connectivity issues. I mentioned in the > e-m

Re: [yocto] Poky 1.3_M3 branch does not work with linux-yocto 3.0 kernel ?

2012-08-27 Thread Bruce Ashfield
On 12-08-27 8:14 PM, Saxena, Rahul wrote: Hi, I am building a BSP (meta-cedartrail) using 1.3 M3 branch of Poky. When I try to boot a image such as core-image-sato, I get kernel panic and errors such as: VFS: Cannot open root device “ram0” or unkown-block(0,0) Please append a correct “root=”