[yocto] Design Document of "Yocto 1656 Recipe creation/import script"
Hi All, This is the design document of "Yocto 1656 Recipe creation/import script". Please help to review it. Any suggestion is appreciate. Regards, Kai Design documnet for Recipe creation/import script * Purpose The feature is from Yocto 1.2 Bug 1656. A script or similar system that would allow you to give is an upstream URL, tarball, patch set, package (SRPM, or debian style) and generate a recipe based on those instructions. Name it with bitbake-createbb, and integrate into the build system to use the build system infrastructure that similiar with bitbake-runtask. * Usage: bitbake-createbb [PATCH_SRC_URI] * Steps 1 download the source package frowm the SRC_RUI 2 get package name and version from package or tarball name. 3 get summary and description from SRPM spec file or debian control file, or from configure files. 4 get license and license checksum. 5 get dependent packages |-- just parse spec file or debian control file |-- or get them by parse configure files 6 remove downloaded files ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH 1/1] distro: Add poky-tiny distro definition
On Thu, 2012-01-05 at 15:37 -0800, Darren Hart wrote: > Poky-tiny is intended for building very small OS images. The distro > definition sets the providers for the kernel and the runtime services. > It also drops NLS support and reduces the eglibc component list and > other DISTRO_FEATURE elements. > > Signed-off-by: Darren Hart > --- > meta-yocto/conf/distro/poky-tiny.conf | 110 > + > 1 files changed, 110 insertions(+), 0 deletions(-) > create mode 100644 meta-yocto/conf/distro/poky-tiny.conf I'd already restored the file but I've merged the delta with an appropriate commit message to resolve this, thanks. Richard ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH V3 0/3] New distribution definition for poky-tiny
On Thu, 2011-12-29 at 03:12 +0100, Leon Woestenberg wrote: > Ah, I missed this line: > o Read-only or RAMFS root filesystem > > > However, our recipes in many ways depend on write behaviour on first > boot. > > When under classic OE, I always had to verify each recipe for correct > operation for ro fs's, and did so manually. > > Would be nice to cover this use case better. We are getting much better at running postinstalls at rootfs creation time meaning that at boot time, there is little remaining work. The useradd code is one example of where its been hard work to get it working but hopefully we are there with that. Cheers, Richard ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Scottrif no IRC
I am still not able to connect to otcchat.org through IRC. Email communication only until this is resolved. Scott Rifenbark Intel Corporation Yocto Project Documentation 503.712.2702 503.341.0418 (cell) ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Design Document of "Yocto 1656 Recipe creation/import script"
On Friday, January 06, 2012 10:51:57 AM Kang Kai wrote: > Hi All, > > This is the design document of "Yocto 1656 Recipe creation/import > script". Please help to review it. > Any suggestion is appreciate. > > Regards, > Kai * s/documnet/document * s/SRC_RUI/SRC_URI * reading first time, I thought 'Steps' mean things user has to perform A bit off-topic: Where is the location for these kind of documents? Andreas ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Design Document of "Yocto 1656 Recipe creation/import script"
Is there any work started regarding this? Will this be part of bitbake? Python will be it's "implementation" language? Best Regards, Pedro Algarvio. On 06/01/12 09:51, Kang Kai wrote: > Hi All, > > This is the design document of "Yocto 1656 Recipe creation/import > script". Please help to review it. > Any suggestion is appreciate. > > Regards, > Kai > > > ___ > 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] Design Document of "Yocto 1656 Recipe creation/import script"
Hi Kai, On 06/01/12 01:51, Kang Kai wrote: This is the design document of "Yocto 1656 Recipe creation/import script". Please help to review it. Any suggestion is appreciate. You should check out autospectacle[1] that I linked to in the bug report. It does a lot of guessing using clever tricks like searching Freshmeat, doap files, READMES etc to get a description[2] and analysing configure.ac[3], qmake[4], etc. to determine dependencies. The autospectacle perl script is reasonably well commented and quite readable. I'm not suggesting we adopt all of the features in it but many of them are useful techniques for this effort. Regards, Joshua 1. https://meego.gitorious.org/meego-developer-tools/autospectacle/ 2. https://meego.gitorious.org/meego-developer-tools/autospectacle/blobs/master/autospectacle.pl#line1001 3. https://meego.gitorious.org/meego-developer-tools/autospectacle/blobs/master/autospectacle.pl#line633 4. https://meego.gitorious.org/meego-developer-tools/autospectacle/blobs/master/autospectacle.pl#line840 -- Joshua Lock Yocto Project "Johannes factotum" Intel Open Source Technology Centre ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] FW: Yocto Project Technical Team Meeting
BEGIN:VCALENDAR METHOD:REQUEST PRODID:Microsoft Exchange Server 2010 VERSION:2.0 BEGIN:VTIMEZONE TZID:Pacific Standard Time BEGIN:STANDARD DTSTART:16010101T02 TZOFFSETFROM:-0700 TZOFFSETTO:-0800 RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11 END:STANDARD BEGIN:DAYLIGHT DTSTART:16010101T02 TZOFFSETFROM:-0800 TZOFFSETTO:-0700 RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3 END:DAYLIGHT END:VTIMEZONE BEGIN:VEVENT ORGANIZER;CN="Liu, Song":MAILTO:song@intel.com ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=yocto@yoct oproject.org:MAILTO:yocto@yoctoproject.org DESCRIPTION;LANGUAGE=en-US:When: Occurs every Tuesday effective 1/10/2012 u ntil 6/19/2012 from 8:00 AM to 9:00 AM (UTC-08:00) Pacific Time (US & Cana da).\nWhere: Bridge Info Enclosed\n\nNote: The GMT offset above does not r eflect daylight saving time adjustments.\n\n*~*~*~*~*~*~*~*~*~*\n\n\n\n--- --Original Appointment-\nFrom: Liu\, Song\nSent: Friday\, January 06\, 2012 2:28 PM\nSubject: Yocto Project Technical Team Meeting\nWhen: Occurs every Tuesday effective 1/10/2012 until 6/19/2012 from 8:00 AM to 9:00 AM (UTC-08:00) Pacific Time (US & Canada).\nWhere: Bridge Info Enclosed\n\n\ n\nConference details\nConference name:Yocto Technical Team\nConfe rence date/start time: Tue Jun 28\, 2011 at 10:00 AM Central Daylight Time\nParticipants: 30\nDuration: 60 minutes\nParticipant passcode : 49611427\nDial-in number: 1.972.995.\nUS Toll Free number: 1.877.561.6828\nBlackBerry users\, click this link to join your confer ence as a chairperson: 1.972.995.x67184230#\nBlackBerry users\, cl ick this link to join your conference as a participant: 1.972.995. x49611427#\nDepending on where you are dialing from\, either your BlackBerry will pause and enter the passcode automatically or you will be prompted to click again to dial the passcode.\n\n\nLocal and Global Access Numbers\n\n\n\n\nCountry\nDial-in number\n\nAustralia:\n1800 636 843\n\nC zech Republic:\n242 430 350\n\nChina (Beijing):\nFrom office dial 8-995777 7 or 8784277\nBeijing Out of Office dial 5878 4277\n\nChina (Shanghai):\nF rom office dial 8-995 or 3073322\nShanghai Out of Office dial 2307 332 2\n\nChina (Shenzen):\nFrom office dial 8-995 or 6007877\nShenzen Out of Office dial 2600 7877\n\nChina (Other Cities):\nFrom IP phone dial 8-99 5\nOther cities - Non IP phone dial 021-23073322\n\nDenmark:\n8060 140 0\n\nFinland:\n09 41333477\n\nFrance:\n0497 275888\n\nGermany:\n08161 8032 32\n\nHolland:\n030 2417490\n\nIndia:\nBSNL subscribers use 1800 425 9996 (Toll Free)\nAirtel subscribers use 0008 009 861 212 (Toll Free)\nFrom TI Campus use 8995\nOthers use 2509 9555 (Landline within Bangalore) or\n 80 2509 9555 (Outside Bangalore)\n\nIsrael:\n09 790 6715\n\nItaly:\n039 69 061234 (039 is local city code not country code)\n\nJapan:\nFrom TI Campus use 8 995 \nOutside TI use 03 4331 3777\n\nMalaysia:\nFrom IP phone d ial 2643799\nFrom Kuala Lumpur dial 4264 3799\nOutside Kuala Lumpur dial ( 03)4264 3799\n\nNorway:\n2 295 8744\n\nPhilippines:\nFrom Baguio City use 4471177\nFrom Metro Manila area use 8702477\n\nSingapore:\nFrom IP phone d ial 3894777\nOutside TI use 6389 4777\n\nSouth Korea:\nFrom IP phone dial 5606998\nFrom Seoul dial 5606998\nOutside Seoul dial (02)5606998\n\nSweden :\n08 58755577\n\nTaiwan:\nFrom IP phone dial 1363\nFrom Taipei dial 2241 1363\nOutside Taipei dial (02)2241 1363\n\nTurkey:\nLandline Only dial 081 1 288 0001\nthen enter 877 633 1123\n\nUK:\n01604 663003\n\nUS:\n972 995 7 777 or 1877 561 6828\n\n\nRecurring conferences\nFirst scheduled conferenc e: Tue Jun 28\, 2011\nRecurrence frequency: Weekly - Every 1 week(s) on Tuesday\nRecurrence ends:End on Fri Jun 22\, 2012\, 10:40 AM C DT\n\n\n\n RRULE:FREQ=WEEKLY;COUNT=24;INTERVAL=1;BYDAY=TU;WKST=SU SUMMARY;LANGUAGE=en-US:FW: Yocto Project Technical Team Meeting DTSTART;TZID=Pacific Standard Time:20120110T08 DTEND;TZID=Pacific Standard Time:20120110T09 UID:04008200E00074C5B7101A82E00870E854717D01000 010004E99009388CC1C40B69E5290C8BFB244 CLASS:PUBLIC PRIORITY:5 DTSTAMP:20120106T222754Z TRANSP:OPAQUE STATUS:CONFIRMED SEQUENCE:0 LOCATION;LANGUAGE=en-US:Bridge Info Enclosed X-MICROSOFT-CDO-APPT-SEQUENCE:0 X-MICROSOFT-CDO-OWNERAPPTID:-664397860 X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY X-MICROSOFT-CDO-ALLDAYEVENT:FALSE X-MICROSOFT-CDO-IMPORTANCE:1 X-MICROSOFT-CDO-INSTTYPE:1 X-MICROSOFT-DISALLOW-COUNTER:FALSE BEGIN:VALARM ACTION:DISPLAY DESCRIPTION:REMINDER TRIGGER;RELATED=START:-PT5M END:VALARM END:VEVENT END:VCALENDAR ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Agenda: Yocto Project Technical Team Meeting - Tuesday, January 10, 2012 8:00 AM-9:00 AM (UTC-08:00) Pacific Time (US & Canada)
Agenda: * Opens collection - 5 min (Song) * Yocto 1.1.1 point release update - 10 min (Josh) * Yocto 1.2 M2 status - 10 min (Song/Bruce/Team) https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.2_Status * Opens - 10 min * Action item Review - 5 min - Mark will review unsorted features from Wind River team and try to have them scheduled (WIP, Reviewed, but not scheduled yet.) - Song and Saul to follow on Scott Garman's M2 schedule conflict. (WIP, need to talk with Dave) - Paul to work with Jeremy and others to move 1598 forward. (WIP) - Paul to split feature 1566. * Team Sharing -Original Appointment- From: Liu, Song Sent: Friday, January 06, 2012 2:28 PM Subject: Yocto Project Technical Team Meeting When: Tuesday, January 10, 2012 8:00 AM-9:00 AM (UTC-08:00) Pacific Time (US & Canada). Where: Bridge Info Enclosed Conference details Conference name:Yocto Technical Team Conference date/start time: Tue Jun 28, 2011 at 10:00 AM Central Daylight Time Participants: 30 Duration: 60 minutes Participant passcode: 49611427 Dial-in number: 1.972.995. US Toll Free number:1.877.561.6828 BlackBerry users, click this link to join your conference as a chairperson: 1.972.995.x67184230# BlackBerry users, click this link to join your conference as a participant: 1.972.995.x49611427# Depending on where you are dialing from, either your BlackBerry will pause and enter the passcode automatically or you will be prompted to click again to dial the passcode. Local and Global Access Numbers Country Dial-in number Australia: 1800 636 843 Czech Republic: 242 430 350 China (Beijing): >From office dial 8-995 or 8784277 Beijing Out of Office dial 5878 4277 China (Shanghai): >From office dial 8-995 or 3073322 Shanghai Out of Office dial 2307 3322 China (Shenzen): >From office dial 8-995 or 6007877 Shenzen Out of Office dial 2600 7877 China (Other Cities): >From IP phone dial 8-995 Other cities - Non IP phone dial 021-23073322 Denmark: 8060 1400 Finland: 09 41333477 France: 0497 275888 Germany: 08161 803232 Holland: 030 2417490 India: BSNL subscribers use 1800 425 9996 (Toll Free) Airtel subscribers use 0008 009 861 212 (Toll Free) >From TI Campus use 8995 Others use 2509 9555 (Landline within Bangalore) or 80 2509 9555 (Outside Bangalore) Israel: 09 790 6715 Italy: 039 69061234 (039 is local city code not country code) Japan: >From TI Campus use 8 995 Outside TI use 03 4331 3777 Malaysia: >From IP phone dial 2643799 >From Kuala Lumpur dial 4264 3799 Outside Kuala Lumpur dial (03)4264 3799 Norway: 2 295 8744 Philippines: >From Baguio City use 4471177 >From Metro Manila area use 8702477 Singapore: >From IP phone dial 3894777 Outside TI use 6389 4777 South Korea: >From IP phone dial 5606998 >From Seoul dial 5606998 Outside Seoul dial (02)5606998 Sweden: 08 58755577 Taiwan: >From IP phone dial 1363 >From Taipei dial 2241 1363 Outside Taipei dial (02)2241 1363 Turkey: Landline Only dial 0811 288 0001 then enter 877 633 1123 UK: 01604 663003 US: 972 995 or 1877 561 6828 Recurring conferences First scheduled conference: Tue Jun 28, 2011 Recurrence frequency: Weekly - Every 1 week(s) on Tuesday Recurrence ends:End on Fri Jun 22, 2012, 10:40 AM CDT ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH 0/1] Add meta-cedartrail to meta-intel/master
From: Kishore Bodke Hi, This patch is to update the meta-cedartrail BSP from edison branch to master branch. Please pull into meta-intel/master. Thanks Kishore. The following changes since commit 7c3db7010479970f3f92501349827c517de3c36a: meta-intel: change EMGD xserver libva dependency to libva-x11 (2011-12-22 09:22:37 -0600) are available in the git repository at: git://git.pokylinux.org/meta-intel-contrib kishore/cedartrail http://git.pokylinux.org/cgit.cgi/meta-intel-contrib/log/?h=kishore/cedartrail Kishore Bodke (1): meta-cedartrail: Create meta-cedartrail BSP Add meta-cedartrail to meta-intel MAINTAINERS|3 + meta-cedartrail/COPYING.MIT| 17 +++ meta-cedartrail/README | 111 meta-cedartrail/README.sources | 17 +++ meta-cedartrail/conf/layer.conf| 10 ++ meta-cedartrail/conf/machine/cedartrail.conf | 15 +++ .../formfactor/formfactor/cedartrail/machconfig|3 + .../recipes-bsp/formfactor/formfactor_0.0.bbappend |3 + .../recipes-core/tasks/task-core-tools.bbappend|2 + .../xserver-xf86-config/cedartrail/xorg.conf | 26 + .../xorg-xserver/xserver-xf86-config_0.1.bbappend |3 + .../linux/linux-yocto-rt_3.0.bbappend |8 ++ .../recipes-kernel/linux/linux-yocto_3.0.bbappend |8 ++ 13 files changed, 226 insertions(+), 0 deletions(-) create mode 100755 meta-cedartrail/COPYING.MIT create mode 100755 meta-cedartrail/README create mode 100755 meta-cedartrail/README.sources create mode 100644 meta-cedartrail/binary/.gitignore create mode 100644 meta-cedartrail/conf/layer.conf create mode 100644 meta-cedartrail/conf/machine/cedartrail.conf create mode 100644 meta-cedartrail/recipes-bsp/formfactor/formfactor/cedartrail/machconfig create mode 100644 meta-cedartrail/recipes-bsp/formfactor/formfactor_0.0.bbappend create mode 100644 meta-cedartrail/recipes-core/tasks/task-core-tools.bbappend create mode 100644 meta-cedartrail/recipes-graphics/xorg-xserver/xserver-xf86-config/cedartrail/xorg.conf create mode 100644 meta-cedartrail/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend create mode 100644 meta-cedartrail/recipes-kernel/linux/linux-yocto-rt_3.0.bbappend create mode 100644 meta-cedartrail/recipes-kernel/linux/linux-yocto_3.0.bbappend -- 1.7.5.4 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH 1/1] meta-cedartrail: Create meta-cedartrail BSP
From: Kishore Bodke Add meta-cedartrail to meta-intel Signed-off-by: Kishore Bodke --- MAINTAINERS|3 + meta-cedartrail/COPYING.MIT| 17 +++ meta-cedartrail/README | 111 meta-cedartrail/README.sources | 17 +++ meta-cedartrail/conf/layer.conf| 10 ++ meta-cedartrail/conf/machine/cedartrail.conf | 15 +++ .../formfactor/formfactor/cedartrail/machconfig|3 + .../recipes-bsp/formfactor/formfactor_0.0.bbappend |3 + .../recipes-core/tasks/task-core-tools.bbappend|2 + .../xserver-xf86-config/cedartrail/xorg.conf | 26 + .../xorg-xserver/xserver-xf86-config_0.1.bbappend |3 + .../linux/linux-yocto-rt_3.0.bbappend |8 ++ .../recipes-kernel/linux/linux-yocto_3.0.bbappend |8 ++ 13 files changed, 226 insertions(+), 0 deletions(-) create mode 100755 meta-cedartrail/COPYING.MIT create mode 100755 meta-cedartrail/README create mode 100755 meta-cedartrail/README.sources create mode 100644 meta-cedartrail/binary/.gitignore create mode 100644 meta-cedartrail/conf/layer.conf create mode 100644 meta-cedartrail/conf/machine/cedartrail.conf create mode 100644 meta-cedartrail/recipes-bsp/formfactor/formfactor/cedartrail/machconfig create mode 100644 meta-cedartrail/recipes-bsp/formfactor/formfactor_0.0.bbappend create mode 100644 meta-cedartrail/recipes-core/tasks/task-core-tools.bbappend create mode 100644 meta-cedartrail/recipes-graphics/xorg-xserver/xserver-xf86-config/cedartrail/xorg.conf create mode 100644 meta-cedartrail/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend create mode 100644 meta-cedartrail/recipes-kernel/linux/linux-yocto-rt_3.0.bbappend create mode 100644 meta-cedartrail/recipes-kernel/linux/linux-yocto_3.0.bbappend diff --git a/MAINTAINERS b/MAINTAINERS index 49b536e..c915a09 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -32,6 +32,9 @@ Please keep this list in alphabetical order. Maintainers List (try to look for most precise areas first) --- +CEDARTRAIL +M: Kishore Bodke +F: meta-cedartrail/ COMMON M: Tom Zanussi diff --git a/meta-cedartrail/COPYING.MIT b/meta-cedartrail/COPYING.MIT new file mode 100755 index 000..fb950dc --- /dev/null +++ b/meta-cedartrail/COPYING.MIT @@ -0,0 +1,17 @@ +Permission is hereby granted, free of charge, to any person obtaining a copy +of this software and associated documentation files (the "Software"), to deal +in the Software without restriction, including without limitation the rights +to use, copy, modify, merge, publish, distribute, sublicense, and/or sell +copies of the Software, and to permit persons to whom the Software is +furnished to do so, subject to the following conditions: + +The above copyright notice and this permission notice shall be included in +all copies or substantial portions of the Software. + +THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR +IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, +FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE +AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER +LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, +OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN +THE SOFTWARE. diff --git a/meta-cedartrail/README b/meta-cedartrail/README new file mode 100755 index 000..295e9ff --- /dev/null +++ b/meta-cedartrail/README @@ -0,0 +1,111 @@ +This README file contains information on building the meta-cedartrail +BSP layer, and booting the images contained in the /binary directory. +Please see the corresponding sections below for details. + +Dependencies + + +This layer depends on: + + URI: git://git.openembedded.org/bitbake + branch: master + + URI: git://git.openembedded.org/openembedded-core + layers: meta + branch: master + + URI: git://git.yoctoproject.org/meta-intel + layers: intel + branch: master + + +Patches +=== + +Please submit any patches against this BSP to the Yocto mailing list +(yocto@yoctoproject.org) and cc: the maintainer: + +Maintainer: Kishore Bodke + +Please see the meta-intel/MAINTAINERS file for more details. + +Table of Contents += + + I. Building the meta-cedartrail BSP layer +II. Booting the images in /binary + + +I. Building the meta-cedartrail BSP layer += + +In order to build an image with BSP support for a given release, you +need to download the corresponding BSP tarball from the 'Board Support +Package (BSP) Downloads' page of the Yocto Project website. + +Having done that, and assuming you extracted the BSP tarball contents +at the top-level of your yocto build tree, you can build a cedartrail +image by adding t
[yocto] Final day for ELC presentations
Hi all - as most of you know, today is the final day to submit presentations for the Embedded Linux Conference ( https://events.linuxfoundation.org/events/embedded-linux-conference). If you plan to present on a Yocto Project topic, please let me know. thanks -- Jeff Osier-Mixon http://jefro.net/blog Yocto Project Community Manager @Intel http://yoctoproject.org ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Does my build disk's filesystem make a difference?
I am creating a Yocto Project build system. For various reasons, it is a dual-boot system, win7 & linux (probably mint 12, haven't decided). I have a primary boot disk with both operating systems and a large secondary disk to use for build trees etc. Does the filesystem on the big secondary disk matter? Ideally I would like to be able to get to the large data disk from both operating systems. That would necessitate NTFS, as win7 does not speak ext4 reliably, but I don't want to slow my builds down. -- Jeff Osier-Mixon http://jefro.net/blog Yocto Project Community Manager @Intel http://yoctoproject.org ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Does my build disk's filesystem make a difference?
On 06/01/12 15:53, Jeff Osier-Mixon wrote: I am creating a Yocto Project build system. For various reasons, it is a dual-boot system, win7 & linux (probably mint 12, haven't decided). I have a primary boot disk with both operating systems and a large secondary disk to use for build trees etc. Does the filesystem on the big secondary disk matter? Ideally I would like to be able to get to the large data disk from both operating systems. That would necessitate NTFS, as win7 does not speak ext4 reliably, but I don't want to slow my builds down. Erk! I'm not familiar with NTFS but the thought of this scares me, I expect you'd be opening yourself up to a world of hurt as: a) NTFS isn't a first class citizen of Linux. b) according to wikipedia NTFS has a 255 character filename limit - I don't know for certain this is a problem but I wouldn't be surprised if it is. Will you be storing anything on the disk that isn't build related? If you anticipate doing a lot of builds you really want to a) use a filesystem that is Linux native and b) tweak the filesystem to reduce the number of writes made. If you just want/need to be able to look at the build system pieces under WinOS then you could try: http://www.ext2fsd.com/ Cheers, Joshua -- Joshua Lock Yocto Project "Johannes factotum" Intel Open Source Technology Centre ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Does my build disk's filesystem make a difference?
On 01/06/2012 04:01 PM, Joshua Lock wrote: > On 06/01/12 15:53, Jeff Osier-Mixon wrote: >> I am creating a Yocto Project build system. For various reasons, it is a >> dual-boot system, win7 & linux (probably mint 12, haven't decided). I >> have a primary boot disk with both operating systems and a large >> secondary disk to use for build trees etc. >> >> Does the filesystem on the big secondary disk matter? Ideally I would Yes, it matters a great deal. Many of the features we use to ensure data integrity and accounting slow down performance. I use a separate ext4 RAID 0 array for builds (and only for builds and other data that can be easily recreated). I mount it without a journal and with noatime. This significantly reduces the overhead of the filesystem and increases performance considerably - at the cost of higher risk of data loss in the event of an unclean shutdown. >> like to be able to get to the large data disk from both operating >> systems. That would necessitate NTFS, as win7 does not speak ext4 >> reliably, but I don't want to slow my builds down. No way. See below for details. > > Erk! I'm not familiar with NTFS but the thought of this scares me, I > expect you'd be opening yourself up to a world of hurt as: > > a) NTFS isn't a first class citizen of Linux. > b) according to wikipedia NTFS has a 255 character filename limit - I > don't know for certain this is a problem but I wouldn't be surprised if > it is. In kernel NTFS only has experimental write support, and only to overwrite existing files without changing their file size. NTFS-3G provides a userspace filesystem implementation with more features, but I'd bet my house on the performance being abysmal for builds. -- Darren > > Will you be storing anything on the disk that isn't build related? If > you anticipate doing a lot of builds you really want to a) use a > filesystem that is Linux native and b) tweak the filesystem to reduce > the number of writes made. > > If you just want/need to be able to look at the build system pieces > under WinOS then you could try: > http://www.ext2fsd.com/ > > Cheers, > Joshua -- Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH 1/4] lttng-ust: Integrate into yocto linux
Hi Zumeng,
Thanks for putting these together.
Please provide a commit message. See:
https://wiki.yoctoproject.org/wiki/Contribution_Guidelines#Patch_Headers_and_Commit_Messages
> +LICENSE = "LGPLv2.1+ & BSD"
> +LIC_FILES_CHKSUM = "file://COPYING;md5=e647752e045a8c45b6f583771bd561ef"
COPYING only covers the LGPL, please add another file to cover the BSD license.
> +
> +inherit autotools
> +
> +DEPENDS = "liburcu util-linux"
> +
> +SRC_URI = "http://lttng.org/files/lttng-ust/lttng-ust-${PV}.tar.gz";
> +
> +SRC_URI[md5sum] = "0f09bb954c99cb99ab6997cd492953c1"
> +SRC_URI[sha256sum] =
> "e9ec3c55c2251b3f3b512bfa1015b0f67e35d55793850ccea5134f7b24ee3ba1"
> +
> +S = "${WORKDIR}/lttng-ust-${PV}"
> +
> +# Due to liburcu not building on MIPS currently this recipe needs to
> +# be limited also.
> +# So here let us first suppport x86/arm/powerpc platforms now.
> +COMPATIBLE_HOST = '(x86_64.*|i.86.*|arm.*|powerpc.*)-linux'
I don't think this is what you meant. You are restricting the type of build
system,
not the type of target you can build for.
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH 2/4] lttng-tools: Integrated from git repo.
This commit message doesn't tell me anything about what this patch is
intended to do.
> +++
> b/meta/recipes-kernel/lttng-2.0/lttng-tools-fix-compiling-error-for-powerpc-arm-and-mips.patch
> @@ -0,0 +1,23 @@
> +Upstream-Status: Pending
> +
> +lttng-tools: fix compiling error for powerpc, arm
> +
Add some commentary here about what the compilation error is.
> +Signed-off-by: Zumeng Chen
> +---
> + librunas/runas.c |1 +
> + 1 files changed, 1 insertions(+), 0 deletions(-)
> +
> +diff --git a/librunas/runas.c b/librunas/runas.c
> +--- a/librunas/runas.c
> b/librunas/runas.c
> +@@ -29,6 +29,7 @@
> + #include
> + #include
> + #include
> ++#include
> +
> + #include
> +
> +--
> +1.7.5.4
> +
> diff --git a/meta/recipes-kernel/lttng-2.0/lttng-tools_2.0-pre16.bb
> b/meta/recipes-kernel/lttng-2.0/lttng-tools_2.0-pre16.bb
> new file mode 100644
> index 000..0b7a240
> --- /dev/null
> +++ b/meta/recipes-kernel/lttng-2.0/lttng-tools_2.0-pre16.bb
> @@ -0,0 +1,24 @@
> +SECTION = "devel"
> +SUMMARY = "Linux Trace Toolkit Control"
> +DESCRIPTION = "The Linux trace toolkit is a suite of tools designed to \
> +extract program execution details from the Linux operating system and \
> +interpret them."
> +LICENSE = "GPLv2.1"
> +LIC_FILES_CHKSUM = "file://COPYING;md5=ab682a4729389c3f11913d758affe98e"
> +
> +DEPENDS = "liburcu popt lttng-ust"
> +
> +SRC_URI = "http://lttng.org/files/lttng-tools/lttng-tools-${PV}.tar.bz2 \
> +file://fix-compiling-error-for-powerpc-arm-and-mips.patch"
Whitespace error. Indent with spaces after the initial block indent
(which doesn't exist here).
> +
> +SRC_URI[md5sum] = "58ed0a15db80a00172d5b0413a55451c"
> +SRC_URI[sha256sum] =
> "188d262bda80043dd939c9aa7aec1795ca77aeec0cb3c0f23c28bfe754049491"
> +
> +S = "${WORKDIR}/lttng-tools-${PV}"
> +
> +
> +inherit autotools
> +
> +export KERNELDIR="${STAGING_KERNEL_DIR}"
> +
> +COMPATIBLE_HOST = '(x86_64.*|i.86.*|arm.*|powerpc.*)-linux'
This requires a comment as in the previous patch. Again, I don't think
this is what you are looking for. You want to limit which target
architectures you build this for. Right?
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH 3/4] lttng-modules: from lttng-modules 2.0 git repo.
On 01/05/2012 10:11 PM, Zumeng Chen wrote:
> LTTng-modules 2.0 is currently in pre-release phase (-pre11)
If the commit message is identical, one could reasonably expect the
patch to be identical ;-) Please provide a complete commit message.
>
> Signed-off-by: Zumeng Chen
> ---
> ...modules-replace-KERNELDIR-with-KERNEL_SRC.patch | 41
>
> .../lttng-2.0/lttng-modules_v2.0.pre11.bb | 23 +++
> 2 files changed, 64 insertions(+), 0 deletions(-)
> create mode 100644
> meta/recipes-kernel/lttng-2.0/lttng-modules-replace-KERNELDIR-with-KERNEL_SRC.patch
> create mode 100644 meta/recipes-kernel/lttng-2.0/lttng-modules_v2.0.pre11.bb
>
> diff --git
> a/meta/recipes-kernel/lttng-2.0/lttng-modules-replace-KERNELDIR-with-KERNEL_SRC.patch
>
> b/meta/recipes-kernel/lttng-2.0/lttng-modules-replace-KERNELDIR-with-KERNEL_SRC.patch
> new file mode 100644
> index 000..b7b2fbb
> --- /dev/null
> +++
> b/meta/recipes-kernel/lttng-2.0/lttng-modules-replace-KERNELDIR-with-KERNEL_SRC.patch
> @@ -0,0 +1,41 @@
> +Upstream-Status: Inappropriate [embedded specific]
> +
> +lttng-modules: replace KERNELDIR with KERNEL_SRC
> +
> +Since lttng-modules uses the default way of module.bbclass to
> +build and install lttng-modules, so we do this replacement for
> +it as-is.
Since and so are redundant: s/so///
> +
> +Signed-off-by: Zumeng Chen
> +---
> + Makefile |7 +++
> + 1 files changed, 3 insertions(+), 4 deletions(-)
> +
> +diff --git a/Makefile b/Makefile
> +index 5ac13d7..25caad5 100644
> +--- a/Makefile
> b/Makefile
> +@@ -38,17 +38,16 @@ obj-m += lib/
> + endif
> +
> + else
> +-KERNELDIR ?= /lib/modules/$(shell uname -r)/build
> + PWD := $(shell pwd)
> + CFLAGS = $(EXTCFLAGS)
> +
> + default:
> +-$(MAKE) -C $(KERNELDIR) M=$(PWD) modules
> ++$(MAKE) -C $(KERNEL_SRC) M=$(PWD) modules
> +
> + modules_install:
> +-$(MAKE) -C $(KERNELDIR) M=$(PWD) modules_install
> ++$(MAKE) -C $(KERNEL_SRC) M=$(PWD) modules_install
> +
> + clean:
> +-$(MAKE) -C $(KERNELDIR) M=$(PWD) clean
> ++$(MAKE) -C $(KERNEL_SRC) M=$(PWD) clean
> +
> + endif
> +--
> +1.7.5.4
> +
> diff --git a/meta/recipes-kernel/lttng-2.0/lttng-modules_v2.0.pre11.bb
> b/meta/recipes-kernel/lttng-2.0/lttng-modules_v2.0.pre11.bb
> new file mode 100644
> index 000..34af847
> --- /dev/null
> +++ b/meta/recipes-kernel/lttng-2.0/lttng-modules_v2.0.pre11.bb
> @@ -0,0 +1,23 @@
> +SECTION = "devel"
> +SUMMARY = "Linux Trace Toolkit KERNEL MODULE"
> +DESCRIPTION = "The lttng-modules 2.0 package contains the kernel tracer
> modules"
> +LICENSE = "LGPLv2.1 & GPLv2"
> +LIC_FILES_CHKSUM = "file://LICENSE;md5=1eb086682a7c65a45acd9bcdf6877b3e \
> +"file://gpl-2.0.txt;md5=751419260aa954499f7abaabaa882bbe \
> +"file://lgpl-2.1.txt;md5=243b725d71bb5df4a1e5920b344b86ad"
Whitespace errors. Please use spaces here.
> +
> +DEPENDS = virtual/kernel
> +
> +inherit module
> +
> +SRCREV = "4d3e89e379fc66480d729abe8daa5c86eb585400"
> +PV = "v2.0.pre11+git${SRCPV}"
> +PR = "r0"
> +
> +SRC_URI += "git://git.lttng.org/lttng-modules.git;protocol=git \
> + file://lttng-modules-replace-KERNELDIR-with-KERNEL_SRC.patch"
Spaces please.
> +
> +export INSTALL_MOD_DIR="kernel/lttng-modules"
> +
> +S = "${WORKDIR}/git"
> +COMPATIBLE_HOST = '(x86_64.*|i.86.*|arm.*|powerpc.*)-linux'
I think you want a solution for TARGET.
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH 0/1] meta-yocto: add local.conf.sample.extended LICENSE_FLAGS_WHITELIST section
From: Tom Zanussi This patch adds a section to local.conf.sample.extended to accompany the corresponding LICENSE_FLAGS mechanism. The following changes since commit 468998cddbe1a803096c9b357e1b5daa3b7e8c2e: Dongxiao Xu (1): command.py: add parseConfigurationFiles API are available in the git repository at: git://git.yoctoproject.org/poky-contrib.git tzanussi/license-flags-whitelist-sample.v1 http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=tzanussi/license-flags-whitelist-sample.v1 Tom Zanussi (1): local.conf.sample.extended: add LICENSE_FLAGS_WHITELIST section meta-yocto/conf/local.conf.sample.extended | 13 + 1 files changed, 13 insertions(+), 0 deletions(-) ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH 1/1] local.conf.sample.extended: add LICENSE_FLAGS_WHITELIST section
From: Tom Zanussi Add a new section for LICENSE_FLAGS_WHITELIST, containing a list of the current packages with LICENSE_FLAGS. Signed-off-by: Tom Zanussi --- meta-yocto/conf/local.conf.sample.extended | 13 + 1 files changed, 13 insertions(+), 0 deletions(-) diff --git a/meta-yocto/conf/local.conf.sample.extended b/meta-yocto/conf/local.conf.sample.extended index 7c26572..f44d7fa 100644 --- a/meta-yocto/conf/local.conf.sample.extended +++ b/meta-yocto/conf/local.conf.sample.extended @@ -123,3 +123,16 @@ # The following is a list of classes to import to use in the generation of images # currently an example class is image_types_uboot # IMAGE_CLASSES = " image_types_uboot" + +# This is a list of packages that require a commercial license to ship +# product. If shipped as part of an image these packages may have +# implications so they are disabled by default. To enable them, +# un-comment the below as appropriate. +#LICENSE_FLAGS_WHITELIST = "commercial_gst-fluendo-mp3 \ +# commercial_gst-openmax \ +# commercial_gst-plugins-ugly \ +# commercial_lame \ +# commercial_libmad \ +# commercial_libomxil \ +# commercial_mpeg2dec \ +# commercial_qmmp" -- 1.7.0.4 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH 1/1] local.conf.sample.extended: add LICENSE_FLAGS_WHITELIST section
On 01/06/2012 09:23 PM, tom.zanu...@intel.com wrote: From: Tom Zanussi Add a new section for LICENSE_FLAGS_WHITELIST, containing a list of the current packages with LICENSE_FLAGS. Signed-off-by: Tom Zanussi Thanks! Acked-by: Saul Wold --- meta-yocto/conf/local.conf.sample.extended | 13 + 1 files changed, 13 insertions(+), 0 deletions(-) diff --git a/meta-yocto/conf/local.conf.sample.extended b/meta-yocto/conf/local.conf.sample.extended index 7c26572..f44d7fa 100644 --- a/meta-yocto/conf/local.conf.sample.extended +++ b/meta-yocto/conf/local.conf.sample.extended @@ -123,3 +123,16 @@ # The following is a list of classes to import to use in the generation of images # currently an example class is image_types_uboot # IMAGE_CLASSES = " image_types_uboot" + +# This is a list of packages that require a commercial license to ship +# product. If shipped as part of an image these packages may have +# implications so they are disabled by default. To enable them, +# un-comment the below as appropriate. +#LICENSE_FLAGS_WHITELIST = "commercial_gst-fluendo-mp3 \ +# commercial_gst-openmax \ +# commercial_gst-plugins-ugly \ +# commercial_lame \ +# commercial_libmad \ +# commercial_libomxil \ +# commercial_mpeg2dec \ +# commercial_qmmp" ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
