Re: [yocto] FW: Yocto Project 1.4 Beta Testing
Hi all, I tried this and felt it easy to use for a new hand like me. Experience survey of using Yocto 1.4 Q: Which architecture did you choose to build? A:x86 Q: How easily were you able to build an image and boot an image? A: It is very easy Q: Is there any surprise to you in the process of doing this Beta testing? If so, would you please describe it and tell us how you expected it to work? A:Yes, I built yocto with Sato reference User Interface support and it is amazing for me that QEMU Emulator can give full-system emulation. Q: Was it easy to find the support you needed to build and boot an image? A:Yes , the documents on the yoctoproject.org is very rich and easy to follow. Q: Which Bugzilla reports did you submit? A: 4247 Q: Did you try anything else with Yocto 1.4? A:Not yet Q: What would you like to have in Yocto Project for future releases? A:Is it possible to have percent indicator(or something like this) for command line UI? Sometimes it takes too long and I even wonder if it's still doing something. Thanks, Chao -Original Message- From: Weiwei Wang [mailto:weiwei.w...@windriver.com] Sent: April 09, 2013 13:30 To: Peng, Chao; Wei, Yunguo (Bryan); Li, Fupan Subject: Fwd: FW: Yocto Project 1.4 Beta Testing Yunguo，Pengchao, Fupan I know you guys all have committed assignment, but I still suggest you guys can try it, because our WRlinux is highly based on Yocto, it can help you guys familiar with Yocto/wrlinux fast. Anyway, it is not a must-do job, it depends on your willing Regards Weiwei Original Message Subject:FW: Yocto Project 1.4 Beta Testing Date: Tue, 9 Apr 2013 06:53:03 +0800 From: Ling, Michael michael.l...@windriver.com To: Wang, Weiwei weiwei.w...@windriver.com, Liu, Bo (Tony) bo@windriver.com, Gooch, Stephen stephen.go...@windriver.com CC: Zhan, Rongkai (Mark) rongkai.z...@windriver.com Weiwei Can someone of CDC Linux team participate in this? YP is important for the WRL future….. Thanks! -Michael *From:*Liu, Song [mailto:song@intel.com] *Sent:* Monday, April 08, 2013 11:26 AM *To:* DiGiglio, John; Allison, Ramsey T; Samson, Don; Burris, Jason M; Tuszynski, Ron S; Moffet, Nathan; Kamble, Nitin A; Ung, Cheng Chuan; Blum, Kirk; Yeleswarapu, Rao; Seow, Chen Yong; Stewart, David C; Williamson, Glenn P; Arzoumanian, Kahren; Barry, Peter; Borders, Jay H; Lynch, Michael A; Osier-mixon, Jeffrey; Saxena, Rahul; Verma, Ishu; Zanussi, Tom; Millsap, Michael G; Narasimhan, Babu; Hatle, Mark; Nicholson, Andrew; Mandal, Laxmikanta; Rutherford, Nicole K; Moses, Fred; Crews, Michael R; Chiang, Terence; Ricci, Davide; Ta, Lieu; Erway, Tracey M; Eng, Robert; Bodke, Kishore K; Murugesu, Sivakumar; Gillen, Mylinh H; Ling, Michael; Yusuf, Imran; Chan, Chee Yau; Cipriano, John; Venkataramani, Sathish P; Haunschild, Nicholas N; Shureih, Sabrina; Finucane, Kevin; Coquerel, Laurent M; Simsek, Gokhan; Ong, Boon Leong; Haw, Foo Chien; Catts-Tucker, Fred; Jajodia, Tanya K *Subject:* Yocto Project 1.4 Beta Testing Hi all, It’s that time again, Yocto Project releases every 6 months and now we are ready for 1.4 Beta testing. Attached is the Beta users guide with testing instructions, please explore it yourself or forward this to anyone who could be interested. Remember, we have Yocto T-shirts for you if you send me the survey feedback. Thanks! Song ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Build problems with ML507 and meta-xilinx
Hi Andrew, On Apr 12, 2013, at 12:34 PM, Andrew James andrew.james77...@gmail.com wrote: I wonder if someone can help me. I'm attempting to do a yocto build for the ML507 xilinx development board and am running into build error when building eglibc I'm using VMWARE Player running an Ubuntu 12.10 64-bit virtual machine. I can succesfully build core-image-minimal using the default settings, but when trying to build for the ML507 (MACHINE = virtex-5-ml507-powerpc-440 I get a build error when compiling eglibc, '440fp not supported' I have used git to get the 'danny' version of the yocto directories. Any help would be appreciated, I can provide futher details if neccessary I was able to get Yocto to build soft fpu (gcc-4.5) and hard fpu (gcc-4.7) support, a couple of months back. Here are some instructions Step 01: Modfy your bblayers.conf file to include the following repositories BBLAYERS ?= \ /tool/yocto/poky/meta \ /tool/yocto/poky/meta-yocto \ /tool/yocto/meta-openembedded/toolchain-layer \ /tool/yocto/meta-xilinx \ Step 02: Modify your local.conf file XILINX_LOC ?= /tool/xilinx/14.3/ISE_DS MACHINE ?= virtex-5-ml507-powerpc-440 XILINX_BSP_PATH ?= /project/xilinx-ml507-base-trd-ppc440-fpu If you use the EDK BSB to create a default project with APU FPU support, it should be sufficient. Step 03: Checkout specific commits ids for each of the repositories poky: commit id: 2a9c574fd8b0800199b6569b6abf02634801013d meta-openembedded: commit id: ef5e1d752003e70d30ce8462c3cd09ce3794d783 meta-xilinx: commit id: c8ad57010f189d6b072ca193a88fd1ff551c5644 http://git.yoctoproject.org/cgit/cgit.cgi/meta-xilinx/log/ Let me know if you run into any more issues. I will need to get around to updating support for the ML507 against the current poky master danny branches in a couple of weeks. Best regards, Elvis Dowson___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Problem with mouse and keyboard detection in yocto (core-image-sato on emenlow)
On 12 April 2013 06:58, Andreas Enbacka aenba...@gmail.com wrote: I tried to execute zcat /proc/config.gz | grep EVDEV, and it produced the following output: # CONFIG_INPUT_EVDEV is not set CONFIG_USB_VIDEO_CLASS_INPUT_EVDEV=y Does the above shed some light what could be the problem with the image? Erm, yes. My atom-pc kernel has CONFIG_INPUT_EVDEV set. There was a bug where kernel configuration was dropping fragments, so you may want to try fetching the dylan branch (as we're about to release) and trying again. Ross ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Problem with mouse and keyboard detection in yocto (core-image-sato on emenlow)
Hi, Thanks for the suggestion, I will fetch the dylan branch and retry. //Andreas -Original Message- From: Burton, Ross [mailto:ross.bur...@intel.com] Sent: 12. huhtikuuta 2013 13:27 To: Andreas Enbacka Cc: Bruce Ashfield; yocto@yoctoproject.org Subject: Re: [yocto] Problem with mouse and keyboard detection in yocto (core-image-sato on emenlow) On 12 April 2013 06:58, Andreas Enbacka aenba...@gmail.com wrote: I tried to execute zcat /proc/config.gz | grep EVDEV, and it produced the following output: # CONFIG_INPUT_EVDEV is not set CONFIG_USB_VIDEO_CLASS_INPUT_EVDEV=y Does the above shed some light what could be the problem with the image? Erm, yes. My atom-pc kernel has CONFIG_INPUT_EVDEV set. There was a bug where kernel configuration was dropping fragments, so you may want to try fetching the dylan branch (as we're about to release) and trying again. Ross ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] How to archive source for a single package
I need to archive source for virtual/kernel when building. This is needed for other builds that uses the bitbake build result. I saw that there is archive-patched-source class, which seems to do what I want plus a lot more. The problem with it is that it seems to be intended for other use case than mine, which means that it does a lot more work than I need. Is there a way to either tame archive-patched-source to only be applicable for virtual/kernel, or is there other ways of accomplishing what I want? Regards Mats ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] An embarrassment of TTYs
My core-image-base build seems to have blessed me with 256 pseudoterminal devices and 325 TTY devices. I really don't deserve this generosity. Is this normal, or am I just a lucky guy? More to the point, where do I donate the excess back, so I can live with a more modest number of these devices? I'd like to be able to do ls /dev/* without having my recent activity disappear off the top of my terminal window scrollback. -- Ciao, Paul D. DeRocco Paulmailto:pdero...@ix.netcom.com ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] An embarrassment of TTYs
Hi Paul, Look for CONFIG_LEGACY_PTY* in your config and tune those values. You can ssh without any legacy PTYs. Sincerely, John Mehaffey Senior System Architect (Automotive) Mentor Graphics Corporation From: yocto-boun...@yoctoproject.org [yocto-boun...@yoctoproject.org] on behalf of Paul D. DeRocco [pdero...@ix.netcom.com] Sent: Friday, April 12, 2013 10:57 AM To: yocto@yoctoproject.org Subject: [yocto] An embarrassment of TTYs My core-image-base build seems to have blessed me with 256 pseudoterminal devices and 325 TTY devices. I really don't deserve this generosity. Is this normal, or am I just a lucky guy? More to the point, where do I donate the excess back, so I can live with a more modest number of these devices? I'd like to be able to do ls /dev/* without having my recent activity disappear off the top of my terminal window scrollback. -- Ciao, Paul D. DeRocco Paulmailto:pdero...@ix.netcom.com ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] An embarrassment of TTYs
From: Mehaffey, John Look for CONFIG_LEGACY_PTY* in your config and tune those values. You can ssh without any legacy PTYs. So legacy PTYs are the 256 BSD devices, so if I disable them I'll still have the UNIX 98 /dev/ptmx mechanism? I don't need SSH, but will nead one pseudo-terminal for something else in the near future. -- Ciao, Paul D. DeRocco Paulmailto:pdero...@ix.netcom.com ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] How to archive source for a single package
Hi Mats, On Fri, Apr 12, 2013 at 03:58:01PM +0200, Mats Liljegren wrote: I need to archive source for virtual/kernel when building. This is needed for other builds that uses the bitbake build result. I saw that there is archive-patched-source class, which seems to do what I want plus a lot more. The problem with it is that it seems to be intended for other use case than mine, which means that it does a lot more work than I need. The archive-*-source classes are primarily intended to assist in providing materials for license compliance for the entire target image. That being said, it shouldn't be too difficult to apply them to a single package. Is there a way to either tame archive-patched-source to only be applicable for virtual/kernel, or is there other ways of accomplishing what I want? I assume you have a line in your local.conf that looks something like: INHERIT += archive-patched-source This means that the class will be inherited at the global level and therefor applied to all packages. It's perfectly reasonable to inherit the class in any specific package, by adding this line to its recipe: inherit archive-patched-source I hope this gives you what you're looking for. Take a look at the Yocto Project dev manual[1] for further information on the source archiver. -Kevin [1] http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#maintaining-open-source-license-compliance-during-your-products-lifecycle Regards Mats ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [yocto-docs][PATCH 1/1] ref-manual/ref-classes: update source archiver entry
The src_distribute*.bbclass files have been removed in favor of archive*.bbclass. Update classes reference to reflect that change. Signed-off-by: Kevin Strasser kevin.stras...@linux.intel.com --- documentation/ref-manual/ref-classes.xml | 40 +++--- 1 file changed, 15 insertions(+), 25 deletions(-) diff --git a/documentation/ref-manual/ref-classes.xml b/documentation/ref-manual/ref-classes.xml index 69ca78c..51418b9 100644 --- a/documentation/ref-manual/ref-classes.xml +++ b/documentation/ref-manual/ref-classes.xml @@ -193,36 +193,26 @@ /para /section -section id='ref-classes-src-distribute' -titleDistribution of Sources - filenamesrc_distribute_local.bbclass/filename/title +section id='ref-classes-archiver' +titleArchiving Sources - filenamearchive*.bbclass/filename/title para -Many software licenses require that source files be provided along with the binaries. -To simplify this process, two classes were created: -filenamesrc_distribute.bbclass/filename and -filenamesrc_distribute_local.bbclass/filename. -/para - -para -The results of these classes are filenametmp/deploy/source//filename -subdirectories with sources sorted by -filenamelink linkend='var-LICENSE'LICENSE/link/filename field. -If recipes list few licenses (or have entries like Bitstream Vera), -the source archive is placed in each license directory. +Many software licenses require that source code and/or other materials be +released with the binaries. To help with that task the following classes +are provided: +itemizedlist + listitemfilenamearchive-original-sources.bbclass/filename/listitem + listitemfilenamearchive-patched-sources.bbclass/filename/listitem + listitemfilenamearchive-configured-sources.bbclass/filename/listitem +listitemfilenamearchiver.bbclass/filename/listitem +/itemizedlist /para para -This class operates using three modes: -itemizedlist -listitemparaemphasiscopy:/emphasis Copies the files to the -distribution directory./para/listitem -listitemparaemphasissymlink:/emphasis Creates symbolic -links for the files to the distribution directory. -/para/listitem -listitemparaemphasismove+symlink:/emphasis Moves the files -into the distribution directory and then creates symbolic -links back to where they originated./para/listitem -/itemizedlist +For more details on the source archiver, see the +ulink url='YOCTO_DOCS_DEV_URL;#maintaining-open-source-license-compliance-during-your-products-lifecycle' +Maintaining Open Source License Compliance During Your Product's Lifecycle/ulink +section in the Yocto Project Development Manual. /para /section -- 1.7.9.5 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
