Re: [yocto] add a process memory check utility (ps_mem)
Hi Khem,
Here is a patch.
- add RDEPENDS python
- updated FILES to your comment
- made change to the master tip of git://git.openembedded.org/meta-openembedded
- testing: bitbake psmem
- testing: bitbake fsl-image-full (using freescale yocto)
Thank you.
Insop
>From 2a4e527465b0ec80e41d2b0df0e2c0b2ef30c608 Mon Sep 17 00:00:00 2001
From: Insop Song
Date: Wed, 10 Dec 2014 17:16:27 -0800
Subject: [yocto][PATCH] Add ps_mem to to accurately report the in core
memory usage
for a program
- https://github.com/pixelb/ps_mem
---
meta-oe/recipes-extended/ps_mem/psmem.bb | 26 ++
1 file changed, 26 insertions(+)
create mode 100644 meta-oe/recipes-extended/ps_mem/psmem.bb
diff --git a/meta-oe/recipes-extended/ps_mem/psmem.bb
b/meta-oe/recipes-extended/ps_mem/psmem.bb
new file mode 100644
index 000..b6b22a7
--- /dev/null
+++ b/meta-oe/recipes-extended/ps_mem/psmem.bb
@@ -0,0 +1,26 @@
+#
+# ps_mem
+#
+
+SUMMARY = "A utility to accurately report the in core memory usage
for a program"
+HOMEPAGE = "https://github.com/pixelb/ps_mem";
+LICENSE = "LGPLv2"
+LIC_FILES_CHKSUM = "file://LICENSE;md5=c05fdef0c0d05f619748e9bb0fb41b21"
+
+RDEPENDS_${PN} = " python "
+
+SRC_URI = "git://github.com/pixelb/ps_mem.git;branch=master;protocol=git"
+SRCREV = "702b461d16062f14a9f4191bc731adcf48b51489"
+
+S = "${WORKDIR}/git"
+
+do_compile () {
+ echo "No compile needed"
+}
+
+do_install () {
+ install -d ${D}${bindir}
+ install -m 0755 ${S}/ps_mem.py ${D}${bindir}/ps_mem
+}
+
+FILES_${PN}-dbg += "/var/www/pages/.debug"
--
1.7.9.5
On Wed, Dec 10, 2014 at 2:39 PM, Khem Raj wrote:
>
>> On Dec 10, 2014, at 1:33 PM, Insop Song wrote:
>>
>> Hi Khem,
>>
>> I've been using this memory check utility (ps_mem) and wrote a bb file
>> to include it in our yocto image.
>>
>> I thought it'd nice to include this in yocto upstream as well.
>>
>> - It's called ps_mem, "A utility to accurately report the in core
>> memory usage for a program"
>> - https://github.com/pixelb
>>
>> Could you consider to include ps_mem in upstream? and let me know what
>> and where to put if is okay? I can follow up.
>
> sure, please post it for meta-openembedded/meta-oe
>
>>
>>
>> Thank you,
>>
>> Insop
>>
>>
>> - this is my bb file as an example
>>
>> diff --git a/recipes-gs/ps_mem/psmem.bb b/recipes-gs/ps_mem/psmem.bb
>> new file mode 100644
>> index 000..d408298
>> --- /dev/null
>> +++ b/recipes-gs/ps_mem/psmem.bb
>> @@ -0,0 +1,26 @@
>> +#
>> +# ps_mem
>> +#
>> +SUMMARY = "A utility to accurately report the in core memory usage
>> for a program"
>> +HOMEPAGE = "https://github.com/pixelb/ps_mem";
>> +LICENSE = "LGPLv2"
>> +LIC_FILES_CHKSUM = "file://LICENSE;md5=c05fdef0c0d05f619748e9bb0fb41b21"
>> +
>> +PR = “r0"
>
> remove this
>
>> +
>> +SRC_URI = "git://github.com/pixelb/ps_mem.git;branch=master;protocol=git"
>> +SRCREV = "702b461d16062f14a9f4191bc731adcf48b51489"
>> +
>> +S = "${WORKDIR}/git"
>> +
>> +do_compile () {
>> + echo "No compile needed"
>> +}
>> +
>> +do_install () {
>> + install -d ${D}${bindir}
>> + install -m 0755 ${S}/ps_mem.py ${D}${bindir}/ps_mem
>
> you need a dependency on python atlas
>
>> +}
>> +
>> +FILES_${PN} += "/*”
>
> why is this needed may be you want www to go under /var
>
>> +FILES_${PN}-dbg += "/www/pages/.debug”
>
> this could go into /var/www
>
>> --
>> 1.7.9.5
>
From 2a4e527465b0ec80e41d2b0df0e2c0b2ef30c608 Mon Sep 17 00:00:00 2001
From: Insop Song
Date: Wed, 10 Dec 2014 17:16:27 -0800
Subject: [PATCH] Add ps_mem to to accurately report the in core memory usage
for a program
- https://github.com/pixelb/ps_mem
---
meta-oe/recipes-extended/ps_mem/psmem.bb | 26 ++
1 file changed, 26 insertions(+)
create mode 100644 meta-oe/recipes-extended/ps_mem/psmem.bb
diff --git a/meta-oe/recipes-extended/ps_mem/psmem.bb b/meta-oe/recipes-extended/ps_mem/psmem.bb
new file mode 100644
index 000..b6b22a7
--- /dev/null
+++ b/meta-oe/recipes-extended/ps_mem/psmem.bb
@@ -0,0 +1,26 @@
+#
+# ps_mem
+#
+
+SUMMARY = "A utility to accurately report the in core memory usage for a program"
+HOMEPAGE = "https://github.com/pixelb/ps_mem";
+LICENSE = "LGPLv2"
+LIC_FILES_CHKSUM = "file://LICENSE;md5=c05fdef0c0d05f619748e9bb0fb41b21"
+
+RDEPENDS_${PN} = " python "
+
+SRC_URI = "git://github.com/pixelb/ps_mem.git;branch=master;protocol=git"
+SRCREV = "702b461d16062f14a9f4191bc731adcf48b51489"
+
+S = "${WORKDIR}/git"
+
+do_compile () {
+ echo "No compile needed"
+}
+
+do_install () {
+ install -d ${D}${bindir}
+ install -m 0755 ${S}/ps_mem.py ${D}${bindir}/ps_mem
+}
+
+FILES_${PN}-dbg += "/var/www/pages/.debug"
--
1.7.9.5
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] add a process memory check utility (ps_mem)
Hi Khem,
I've been using this memory check utility (ps_mem) and wrote a bb file
to include it in our yocto image.
I thought it'd nice to include this in yocto upstream as well.
- It's called ps_mem, "A utility to accurately report the in core
memory usage for a program"
- https://github.com/pixelb
Could you consider to include ps_mem in upstream? and let me know what
and where to put if is okay? I can follow up.
Thank you,
Insop
- this is my bb file as an example
diff --git a/recipes-gs/ps_mem/psmem.bb b/recipes-gs/ps_mem/psmem.bb
new file mode 100644
index 000..d408298
--- /dev/null
+++ b/recipes-gs/ps_mem/psmem.bb
@@ -0,0 +1,26 @@
+#
+# ps_mem
+#
+SUMMARY = "A utility to accurately report the in core memory usage
for a program"
+HOMEPAGE = "https://github.com/pixelb/ps_mem";
+LICENSE = "LGPLv2"
+LIC_FILES_CHKSUM = "file://LICENSE;md5=c05fdef0c0d05f619748e9bb0fb41b21"
+
+PR = "r0"
+
+SRC_URI = "git://github.com/pixelb/ps_mem.git;branch=master;protocol=git"
+SRCREV = "702b461d16062f14a9f4191bc731adcf48b51489"
+
+S = "${WORKDIR}/git"
+
+do_compile () {
+ echo "No compile needed"
+}
+
+do_install () {
+ install -d ${D}${bindir}
+ install -m 0755 ${S}/ps_mem.py ${D}${bindir}/ps_mem
+}
+
+FILES_${PN} += "/*"
+FILES_${PN}-dbg += "/www/pages/.debug"
--
1.7.9.5
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] how to disable shell access
Thank you Ross, To answer my own question on "1. how to change the default password of root?" - remove "debug-tweaks" and do as it is described in "https://wiki.yoctoproject.org/wiki/FAQ:How_do_I_set_or_change_the_root_password"; Ref: https://wiki.yoctoproject.org/wiki/FAQ:How_do_I_set_or_change_the_root_password http://bec-systems.com/site/967/setting-the-root-password-in-an-openembedded-image https://lists.yoctoproject.org/pipermail/poky/2013-August/009098.html http://gumstix.8.x6.nabble.com/Duovero-EXTRA-IMAGE-FEATURES-tools-sdk-password-td4968867.html ISS On Tue, Jun 17, 2014 at 1:54 PM, Burton, Ross wrote: > On 17 June 2014 21:23, Insop Song wrote: >> 2. how to block shell access but to open for debugging access >> For this, I could think of that we could block ssh access and only open >> console. >> Or opening ssh for a hidden port only. > > The Raumfeld multi-room audio system has a neat solution for this: you > insert a USB stick with a special file to enable the SSH daemon. The > filename is a md5sum, presumably a hash of something along the lines > of "open sesame". This is their magic "root me" button, as root has > no password. > > Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] how to disable shell access
All, We usually want to block shell access for the product that we release, but want to have a way to log in for debugging and troubleshoot. I want to ask how other developers are doing this. So two main questions: 1. how to change the default password of root? 2. how to block shell access but to open for debugging access For this, I could think of that we could block ssh access and only open console. Or opening ssh for a hidden port only. I look forward to hearing from your experiences. Thank you, ISS -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Why use Yocto?
Just add my few cents of using Yocto. Since yocto is tailored towards embedded system, normally it includes light weight (strip-down version/flavor) software and servers, such as sysklogd instead of syslogd and busybox cron instead of crond. Which is not a bad thing at all, as this make sure your system is less bloated. However, just be aware that when you want to make some changes to these server configurations, you need more debugging time since some of this strip-down servers does not behave as other full blown servers. Also this means that google search wont' give you good answers either since most of the answers to the existing distribution (ubuntu, debian,,,) targeted. On the other hand, this mailing list is very active, and you will get answers from other developers quickly. ISS On Tue, Jun 10, 2014 at 10:16 AM, Alex J Lennon wrote: > > On 10/06/2014 17:50, Marlon Smith wrote: > > Wow, thanks everyone for the excellent replies. I am a developer and not > much of a legal guy, so pointing out the licensing issues with Ubuntu was > especially helpful. > > It sounds like we are going to choose Yocto for our product. > > > Further to the excellent points made by others, presumably Freescale are > providing commercial support on Yocto for i.MX6 now too. > > I know they have a developer day coming up in the UK shortly at which Yocto > is on the agenda. > > I also suspect they will have some "ready to run" binaries somewhere for > download, although I can't spot them in the walled garden. > > They usually do, and that might even be enough for you, depending on your > needs, and how custom the board variant is... > > Regards, > > Alex > > > -- > ___ > 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] how to specify if multiple bb files are existing
Hi Rudi, I looked more and found out that the reason why 2013.01.01.bb, which is the latest, was not picked was due to "DEFAULT_PREFERENCE = -1" in that file. I was using this file from here : http://git.freescale.com/git/cgit.cgi/ppc/sdk/poky.git/tree/meta/recipes-bsp/u-boot/u-boot-fw-utils_2013.01.01.bb?h=dylan Thank you. ISS On Wed, Jun 4, 2014 at 7:27 PM, Insop Song wrote: > Hi Rudi, > > Thank you very much for your help. > I've added PREFERRED_VERSION and started build. > > Regards, > > Insop > > On Wed, Jun 4, 2014 at 6:37 PM, Rudolf Streif > wrote: >> Hi Insop, >> >> Technically u-boot-fw-utils_2013.01.01 should be used because it's the newer >> version. However, you can explicitly specify >> >> PREFERRED_VERSION_u-boot-fw-utils = "2013.01.01" >> >> Cheers, >> Rudi >> -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] how to specify if multiple bb files are existing
Hi Rudi, Thank you very much for your help. I've added PREFERRED_VERSION and started build. Regards, Insop On Wed, Jun 4, 2014 at 6:37 PM, Rudolf Streif wrote: > Hi Insop, > > Technically u-boot-fw-utils_2013.01.01 should be used because it's the newer > version. However, you can explicitly specify > > PREFERRED_VERSION_u-boot-fw-utils = "2013.01.01" > > Cheers, > Rudi > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] how to specify if multiple bb files are existing
Hi All, I want include "u-boot-fw-utils" to my image. I want to include "u-boot-fw-utils_2013.01.01.bb", but "u-boot-fw-utils_2011.06.bb" is included if I added it in my image like following IMAGE_INSTALL += " \ ... u-boot-fw-utils \ " Question: - how to specify bb file when there are multiple of them like followings? $ du . -a | grep u-boot-fw 12 ./meta/recipes-bsp/u-boot/u-boot-fw-utils_2013.01.01.bb 12 ./meta/recipes-bsp/u-boot/u-boot-fw-utils_2011.06.bb Thank you, ISS -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [yocto and jenkins]
Thank you for the corection Paul, yes you are right.
I actually run the following from jenkins job
export BB_ENV_EXTRAWHITE="BUILD_NUMBER"
source SOURCE_THIS
bitbake our_image
On Wed, Jun 4, 2014 at 2:53 AM, Paul Eggleton
wrote:
> On Monday 02 June 2014 17:26:08 Insop Song wrote:
>> Thank you very much Paul.
>>
>> Setting "export BB_ENV_EXTRAWHITE=${BUILD_NUMBER}" fixed the issue.
>
> I think that should be "export BB_ENV_EXTRAWHITE=BUILD_NUMBER" (since it's the
> variable name you're allowing through, not just the value).
>
> Cheers,
> Paul
>
> --
>
> Paul Eggleton
> Intel Open Source Technology Centre
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [yocto and jenkins]
Thank you very much Paul.
Setting "export BB_ENV_EXTRAWHITE=${BUILD_NUMBER}" fixed the issue.
Regards,
Insop
On Mon, Jun 2, 2014 at 4:03 PM, Paul Barker wrote:
> On Mon, Jun 02, 2014 at 03:38:43PM -0700, Insop Song wrote:
>> All,
>>
>> I've been building yocto using jenkins.
>>
>> I want to include yocto's build environment variable "BUILD_NUMBER" to
>> yocto's kernel.
>>
>> 1, I've tried this in one of my conf file, add
>>
>> GS_SDK_VERSION = "GS-SDK-V1.5-${BUILD_NUMBER}"
>>
>> But ${BUILD_NUMBER} is not expended
>>
>>
>> 2, I've looked at Keon's example from
>> https://git.linaro.org/openembedded/jenkins-setup.git
>>
>> I've put the following in conf/local.conf
>>
>> JENKINS_BUILD_NUMBER = "`echo ${BUILD_NUMBER}`"
>>
>> Then add GS_SDK_VERSION = "GS-SDK-V1.5-${JENKINS_BUILD_NUMBER}"
>>
>> It still doesn't expand.
>>
>> So my question is
>>
>> - how to include environment variable to yocto's running?
>
> As a guess, bitbake is ignoring the value of the BUILD_NUMBER environment
> variable. You can add the variable to BB_ENV_EXTRAWHITE but you need to do so
> outside of bitbake as the value needs to be set when bitbake starts
> (BB_ENV_EXTRAWHITE is an environment variable).
>
> Googling BB_ENV_EXTRAWHITE should provide more information.
>
> --
> Paul Barker
>
> Email: p...@paulbarker.me.uk
> http://www.paulbarker.me.uk
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [yocto and jenkins]
All,
I've been building yocto using jenkins.
I want to include yocto's build environment variable "BUILD_NUMBER" to
yocto's kernel.
1, I've tried this in one of my conf file, add
GS_SDK_VERSION = "GS-SDK-V1.5-${BUILD_NUMBER}"
But ${BUILD_NUMBER} is not expended
2, I've looked at Keon's example from
https://git.linaro.org/openembedded/jenkins-setup.git
I've put the following in conf/local.conf
JENKINS_BUILD_NUMBER = "`echo ${BUILD_NUMBER}`"
Then add GS_SDK_VERSION = "GS-SDK-V1.5-${JENKINS_BUILD_NUMBER}"
It still doesn't expand.
So my question is
- how to include environment variable to yocto's running?
Thank you,
Insop
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] package install in using INITSCRIPT_PARAMS
Hi, I've use the following to set up SystemV init.d configuration and it works fine for full root file system generation. my example> INITSCRIPT_NAME = "startwifi" INITSCRIPT_PARAMS = "start 99 S ." However, if I don't include the above application as part of the image and later install it using RPM installation (busybox rpm), then "/etc/rcS" is not set up on rpm installation. I'd think that this should be set upon rpm installation as well. What do you think? Thank you, Insop My build env --- Build Configuration: BB_VERSION= "1.18.0" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "Ubuntu-12.04" TARGET_SYS= "powerpc-fsl_networking-linux" MACHINE = "b4860qds" DISTRO= "fsl-networking" DISTRO_VERSION= "1.4.1" TUNE_FEATURES = "m32 fpu-hard e6500 altivec" TARGET_FPU= "hard" meta meta-yocto meta-yocto-bsp= "(nobranch):5130199a19fd7410003001e99ca736699a350f10" meta-fsl-ppc = "(nobranch):77d0e8f5455830a813fa5a823e37da990eec3635" meta-fsl-ppc-toolchain = "(nobranch):8ec94cec04527cb971c125b1ddd2c5375034d723" meta-virtualization = "(nobranch):ad6df4f59cd7646f61db29e8fa51f878329d6f93" meta-fsl-networking = "(nobranch):04ff616e1b6e97b7d9497adfe7b858d0e969135b" meta-oe meta-networking = "(nobranch):7c8dd8f096b64a709175d37a08a4fb02ca263616" ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] package_deb creation issue in powerpc (kernel 64bit, userspace 32bit)
Can anyone use debian package? On Tue, Dec 10, 2013 at 9:29 PM, Insop Song wrote: > Hi Khem and Paul, > > I have an issue of creating deb packages. > > I am using Freescale version of yocto, which is based on dylan > - http://git.freescale.com/git/cgit.cgi/ppc/sdk/poky.git/ > > I've put the following in > - PACKAGE_CLASSES ?= "package_deb" > - IMAGE_FEATURES += "package-management" > > I've tested opkg, and it runs fine as you suggested in other thread > - https://lists.yoctoproject.org/pipermail/yocto/2013-October/016887.html > > Our target is: > - RFS and application: 32bit > - Kernel: 64 bit > - ARCH: powerpc > > > Here is the error message I got: > > " > insop@neon /opt/build-fsl-yocto-1.4 $ bitbake fsl-image-g100 > Parsing recipes: 100% > |###| > Time: 00:01:30 > Parsing of 1376 .bb files complete (0 cached, 1376 parsed). 3147 > targets, 132 skipped, 0 masked, 0 errors. > Build Configuration: > BB_VERSION= "1.18.0" > BUILD_SYS = "x86_64-linux" > NATIVELSBSTRING = "Ubuntu-12.04" > TARGET_SYS= "powerpc-fsl_networking-linux" > MACHINE = "b4860qds" > DISTRO= "fsl-networking" > DISTRO_VERSION= "1.4.1" > TUNE_FEATURES = "m32 fpu-hard e6500 altivec" > TARGET_FPU= "hard" > meta > meta-yocto > meta-yocto-bsp= "feature/CH-1449:97b5f9e64fb64aa1c883eedc03e6cb6765291179" > meta-fsl-ppc = "feature/CH-1449:d686f3162481ccb942a3d896a10a86d93d12e455" > meta-fsl-ppc-toolchain = "sdk-v1.4.x:8ec94cec04527cb971c125b1ddd2c5375034d723" > meta-virtualization = "sdk-v1.4.x:ad6df4f59cd7646f61db29e8fa51f878329d6f93" > meta-fsl-networking = "develop:08bb6c1a78838bbff79befa3f15e49ca642d479e" > meta-oe > meta-networking = "sdk-v1.4.x:7c8dd8f096b64a709175d37a08a4fb02ca263616" > NOTE: Resolving any missing task queue dependencies > NOTE: Preparing runqueue > NOTE: Executing SetScene Tasks > NOTE: Executing RunQueue Tasks > ERROR: Function failed: do_rootfs (see > /opt/build-fsl-yocto-1.4/tmp/work/b4860qds-fsl_networking-linux/fsl-image-g100/1.0-r20/temp/log.do_rootfs.8847 > for further information) > ERROR: Logfile of failure stored in: > /opt/build-fsl-yocto-1.4/tmp/work/b4860qds-fsl_networking-linux/fsl-image-g100/1.0-r20/temp/log.do_rootfs.8847 > Log data follows: > | DEBUG: Executing shell function do_rootfs > | dpkg-scanpackages.real: info: Wrote 6 entries to output Packages file. > | dpkg-scanpackages.real: info: Wrote 2037 entries to output Packages file. > | dpkg-scanpackages.real: info: Wrote 68 entries to output Packages file. > | dpkg-scanpackages.real: info: Wrote 6 entries to output Packages file. > | Ign file: ./ InRelease > | Ign file: ./ InRelease > | Ign file: ./ InRelease > | Ign file: ./ Release.gpg > | Ign file: ./ Release.gpg > | Ign file: ./ Release.gpg > | Get:1 file: ./ Release [16 B] > | Get:2 file: ./ Release [16 B] > | Get:3 file: ./ Release [11 B] > | Ign file: ./ Translation-en > | Ign file: ./ Translation-en > | Ign file: ./ Translation-en > | Reading package lists... > | W: Ignoring Provides line with DepCompareOp for package > pkgconfig__pkg-config__ > | W: You may want to run apt-get update to correct these problems > | Reading package lists... > | Building dependency tree... > | W: Ignoring Provides line with DepCompareOp for package > pkgconfig__pkg-config__ > | W: You may want to run apt-get update to correct these problems > | E: Unable to locate package lib64-hypervisor > | E: Unable to locate package lib64-hypervisor-partman > | ERROR: Function failed: do_rootfs (see > /opt/build-fsl-yocto-1.4/tmp/work/b4860qds-fsl_networking-linux/fsl-image-g100/1.0-r20/temp/log.do_rootfs.8847 > for further information) > ERROR: Task 7 > (/home/insop/Projects/fsl-yocto-1.4/meta-fsl-networking/images/fsl-image-g100.bb, > do_rootfs) failed with exit code '1' > NOTE: Tasks Summary: Attempted 3527 tasks of which 2782 didn't need to > be rerun and 1 failed. > No currently running tasks (3527 of 3528) > Summary: 1 task failed: > > /home/insop/Projects/fsl-yocto-1.4/meta-fsl-networking/images/fsl-image-g100.bb, > do_rootfs > Summary: There was 1 ERROR message shown, returning a non-zero exit code. > " > > Thank you, > > Insop ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] package_deb creation issue in powerpc (kernel 64bit, userspace 32bit)
Hi Khem and Paul, I have an issue of creating deb packages. I am using Freescale version of yocto, which is based on dylan - http://git.freescale.com/git/cgit.cgi/ppc/sdk/poky.git/ I've put the following in - PACKAGE_CLASSES ?= "package_deb" - IMAGE_FEATURES += "package-management" I've tested opkg, and it runs fine as you suggested in other thread - https://lists.yoctoproject.org/pipermail/yocto/2013-October/016887.html Our target is: - RFS and application: 32bit - Kernel: 64 bit - ARCH: powerpc Here is the error message I got: " insop@neon /opt/build-fsl-yocto-1.4 $ bitbake fsl-image-g100 Parsing recipes: 100% |###| Time: 00:01:30 Parsing of 1376 .bb files complete (0 cached, 1376 parsed). 3147 targets, 132 skipped, 0 masked, 0 errors. Build Configuration: BB_VERSION= "1.18.0" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "Ubuntu-12.04" TARGET_SYS= "powerpc-fsl_networking-linux" MACHINE = "b4860qds" DISTRO= "fsl-networking" DISTRO_VERSION= "1.4.1" TUNE_FEATURES = "m32 fpu-hard e6500 altivec" TARGET_FPU= "hard" meta meta-yocto meta-yocto-bsp= "feature/CH-1449:97b5f9e64fb64aa1c883eedc03e6cb6765291179" meta-fsl-ppc = "feature/CH-1449:d686f3162481ccb942a3d896a10a86d93d12e455" meta-fsl-ppc-toolchain = "sdk-v1.4.x:8ec94cec04527cb971c125b1ddd2c5375034d723" meta-virtualization = "sdk-v1.4.x:ad6df4f59cd7646f61db29e8fa51f878329d6f93" meta-fsl-networking = "develop:08bb6c1a78838bbff79befa3f15e49ca642d479e" meta-oe meta-networking = "sdk-v1.4.x:7c8dd8f096b64a709175d37a08a4fb02ca263616" NOTE: Resolving any missing task queue dependencies NOTE: Preparing runqueue NOTE: Executing SetScene Tasks NOTE: Executing RunQueue Tasks ERROR: Function failed: do_rootfs (see /opt/build-fsl-yocto-1.4/tmp/work/b4860qds-fsl_networking-linux/fsl-image-g100/1.0-r20/temp/log.do_rootfs.8847 for further information) ERROR: Logfile of failure stored in: /opt/build-fsl-yocto-1.4/tmp/work/b4860qds-fsl_networking-linux/fsl-image-g100/1.0-r20/temp/log.do_rootfs.8847 Log data follows: | DEBUG: Executing shell function do_rootfs | dpkg-scanpackages.real: info: Wrote 6 entries to output Packages file. | dpkg-scanpackages.real: info: Wrote 2037 entries to output Packages file. | dpkg-scanpackages.real: info: Wrote 68 entries to output Packages file. | dpkg-scanpackages.real: info: Wrote 6 entries to output Packages file. | Ign file: ./ InRelease | Ign file: ./ InRelease | Ign file: ./ InRelease | Ign file: ./ Release.gpg | Ign file: ./ Release.gpg | Ign file: ./ Release.gpg | Get:1 file: ./ Release [16 B] | Get:2 file: ./ Release [16 B] | Get:3 file: ./ Release [11 B] | Ign file: ./ Translation-en | Ign file: ./ Translation-en | Ign file: ./ Translation-en | Reading package lists... | W: Ignoring Provides line with DepCompareOp for package pkgconfig__pkg-config__ | W: You may want to run apt-get update to correct these problems | Reading package lists... | Building dependency tree... | W: Ignoring Provides line with DepCompareOp for package pkgconfig__pkg-config__ | W: You may want to run apt-get update to correct these problems | E: Unable to locate package lib64-hypervisor | E: Unable to locate package lib64-hypervisor-partman | ERROR: Function failed: do_rootfs (see /opt/build-fsl-yocto-1.4/tmp/work/b4860qds-fsl_networking-linux/fsl-image-g100/1.0-r20/temp/log.do_rootfs.8847 for further information) ERROR: Task 7 (/home/insop/Projects/fsl-yocto-1.4/meta-fsl-networking/images/fsl-image-g100.bb, do_rootfs) failed with exit code '1' NOTE: Tasks Summary: Attempted 3527 tasks of which 2782 didn't need to be rerun and 1 failed. No currently running tasks (3527 of 3528) Summary: 1 task failed: /home/insop/Projects/fsl-yocto-1.4/meta-fsl-networking/images/fsl-image-g100.bb, do_rootfs Summary: There was 1 ERROR message shown, returning a non-zero exit code. " Thank you, Insop ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] How NOT to include kernel image to the rootfs?
Thank you all for the help. I've added "RDEPENDS_kernel-base = """ at conf/local.conf Also I had to take out "oprofile" in my image, as oprofile needs kernel-vmlinux ... Then it worked. Thank you all. Regards, Insop On Mon, Jun 24, 2013 at 2:12 AM, Luo Zhenhua-B19537 wrote: > Insop, > > You can check the actual dependency in the output file of "bitbake -g > fsl-image-min-net2". > > > Best Regards, > > Zhenhua > >> -Original Message- >> From: yocto-boun...@yoctoproject.org [mailto:yocto- >> boun...@yoctoproject.org] On Behalf Of Anders Darander >> Sent: Monday, June 24, 2013 5:05 PM >> To: yocto@yoctoproject.org >> Subject: Re: [yocto] How NOT to include kernel image to the rootfs? >> >> * Insop Song [130624 10:56]: >> > I've tried >> > - by commenting "RDEPENDS_kernel-base ?= "kernel-image"" from >> > kernel.bbclass >> > - and/or adding "RDEPENDS_kernel-base = "" in my image definition >> >> You should add this line in either your local.conf, or in a .bbappend for >> the kernel recipe in question. >> >> > But neither worked. >> >> That should make it work. >> >> >> Cheers, >> Anders >> >> >> -- >> Anders Darander >> ChargeStorm AB / eStorm AB >> ___ >> 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] How NOT to include kernel image to the rootfs?
Hi, Thank you for the answer. I've tried - by commenting "RDEPENDS_kernel-base ?= "kernel-image"" from kernel.bbclass - and/or adding "RDEPENDS_kernel-base = "" in my image definition But neither worked. For confirmation, this bitbake -e outptut and it doesn't have the kernel-base insop@neon /opt/build-fsl-yocto-1.3.2 $ time bitbake -e fsl-image-min-net2 | grep kernel-base real 0m10.691s user 0m6.476s sys 0m0.844s insop@neon /opt/bui Also, though it was not concluded, I found this mail thread also said that it didn't work http://comments.gmane.org/gmane.linux.embedded.yocto.general/12694 Any other thought? Thank you, Insop On Sun, Jun 23, 2013 at 8:29 PM, Bruce Ashfield < bruce.ashfi...@windriver.com> wrote: > On 13-06-23 7:08 PM, Insop Song wrote: > >> Hi, >> >> - Question >> "How NOT to include kernel image to the rootfs?" >> >> - Background >> In our application, we use u-boot to load kernel and rootfs from nand >> flash separately. >> >> I don't want to include kernel image inside /boot as I don't need it >> over there. >> I could untar the rootfs, remove, and tar it up again, but I would like >> to find a way within the yocto framework. >> >> I was not able to find a way by looking up the recipies and googling on >> this topic. >> >> Could any one help me? >> > > Have you tried clearing RDEPENDS_kernel-base ? > > From kernel.bbclass: > > # Allow machines to override this dependency if kernel image files are > # not wanted in images as standard > RDEPENDS_kernel-base ?= "kernel-image" > > Cheers, > > Bruce > > > > > >> Thank you, >> >> Insop >> > > ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] How NOT to include kernel image to the rootfs?
Hi, - Question "How NOT to include kernel image to the rootfs?" - Background In our application, we use u-boot to load kernel and rootfs from nand flash separately. I don't want to include kernel image inside /boot as I don't need it over there. I could untar the rootfs, remove, and tar it up again, but I would like to find a way within the yocto framework. I was not able to find a way by looking up the recipies and googling on this topic. Could any one help me? Thank you, Insop ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] grub-efi-native_2.00.bb do_deploy fail
Hi, I am using latest HEAD of master, and have this error, any one has the similar issue? - error msg ERROR: Function failed: do_deploy (see /home/insop/mybuilds/fri2-1.4/tmp/work/i686-linux/grub-efi-i586-native/2.00-r1/temp/log.do_deploy.7321 for further information) ERROR: Logfile of failure stored in: /home/insop/mybuilds/fri2-1.4/tmp/work/i686-linux/grub-efi-i586-native/2.00-r1/temp/log.do_deploy.7321 - full log insop@chai ~/mybuilds/fri2-1.4 $ time bitbake core-image-realtime-sdk Loading cache: 100% |##| ETA: 00:00:00 Loaded 1145 entries from dependency cache. Build Configuration: BB_VERSION= "1.17.1" BUILD_SYS = "i686-linux" NATIVELSBSTRING = "Ubuntu-12.10" TARGET_SYS= "i586-poky-linux" MACHINE = "fri2" DISTRO= "poky" DISTRO_VERSION= "1.3+snapshot-20130325" TUNE_FEATURES = "m32 core2" TARGET_FPU= "" meta meta-yocto meta-yocto-bsp= "master:3c5f4d54d01887a117bf659fc9af6b2b892c2b08" meta-intel meta-fri2 = "master:8bfb88c22a9298c0193ccbb7fc0221300956b612" meta-realtime = "image-sdk:6825219a33a4b4d140a01cee5165d805951d1d75" NOTE: Resolving any missing task queue dependencies NOTE: Preparing runqueue NOTE: Executing SetScene Tasks NOTE: Executing RunQueue Tasks ERROR: Function failed: do_deploy (see /home/insop/mybuilds/fri2-1.4/tmp/work/i686-linux/grub-efi-i586-native/2.00-r1/temp/log.do_deploy.7321 for further information) ERROR: Logfile of failure stored in: /home/insop/mybuilds/fri2-1.4/tmp/work/i686-linux/grub-efi-i586-native/2.00-r1/temp/log.do_deploy.7321 Log data follows: | DEBUG: Executing python function sstate_task_prefunc | DEBUG: Python function sstate_task_prefunc finished | DEBUG: Executing shell function do_deploy | install: cannot stat `/home/insop/mybuilds/fri2-1.4/tmp/work/i686-linux/grub-efi-i586-native/2.00-r1/grub-2.00/bootia32.efi': No such file or directory | ERROR: Function failed: do_deploy (see /home/insop/mybuilds/fri2-1.4/tmp/work/i686-linux/grub-efi-i586-native/2.00-r1/temp/log.do_deploy.7321 for further information) ERROR: Task 243 (/home/insop/poky/meta/recipes-bsp/grub/grub-efi-native_2.00.bb, do_deploy) failed with exit code '1' Currently 3 running tasks (4427 of 4432): 0: core-image-realtime-sdk-1.0-r0 do_rootfs (pid 3668) 1: syslinux-4.03-r9 do_package_write_rpm (pid 19504) 2: core-image-minimal-initramfs-1.0-r0 do_rootfs (pid 23423) -- Thank you, Insop ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] custom hddimg failure (mkdosfs: seek failed)
Thank you.
Works, I can log in without password
Insop
On Mar 23, 2013, at 0:04, Khem Raj wrote:
>
> On Mar 22, 2013, at 11:53 PM, Insop Song wrote:
>
>> Hi Khem,
>>
>> Thank you for the reply.
>>
>> I've tried and it worked only if I use "tools-sdk" like below:
>>
>> However, this image asks me the paaswrd, do you know?
>>
>> Thank you,
>>
>> Insop
>>
>> =
>> DEPENDS = "linux-yocto"
>>
>> IMAGE_FEATURES += "package-management ssh-server-dropbear"
>> EXTRA_IMAGE_FEATURES = "tools-sdk tools-profile"
>
> add 'debug-tweaks' also to EXTRA_IMAGE_FEATURES
>
>
>>
>> IMAGE_INSTALL = "\
>>${CORE_IMAGE_BASE_INSTALL} \
>>rt-app \
>>schedtool-dl \
>>
>> =
>>
>>
>>
>> On Thu, Mar 21, 2013 at 10:58 AM, Khem Raj wrote:
>>> EXTRA_IMAGE_FEATURES = "tools-sdk"
>>>
>>> On Mar 21, 2013, at 1:44 AM, Insop Song wrote:
>>>
>>>> Hi,
>>>>
>>>> I am trying to add sdk (gcc ..) to meta-realtime
>>>> (http://git.yoctoproject.org/cgit/cgit.cgi/meta-realtime/).
>>>> Only difference between upstream meta-realtime is ""tools-sdk"
>>>>
>>>> -
>>>> require recipes-core/images/core-image-minimal-dev.bb
>>>>
>>>> DESCRIPTION = "Image with meta-realtime and sdk"
>>>>
>>>> DEPENDS = "linux-yocto"
>>>>
>>>> IMAGE_FEATURES += "package-management ssh-server-dropbear"
>>>> IMAGE_FEATURES += "tools-sdk"
>>>> EXTRA_IMAGE_FEATURES = "tools-debug debug-tweaks tools-profile dbg-pkgs"
>>>>
>>>> IMAGE_INSTALL = "\
>>>> ${CORE_IMAGE_BASE_INSTALL} \
>>>> rt-app \
>>>> schedtool-dl \
>>>> "
>>>>
>>>>
>>>>
>>>> I am keep getting hddimg failure with this message "mkdosfs: seek failed"
>>>>
>>>> I appreciate if anyone know on this issue.
>>>>
>>>> Thank you,
>>>>
>>>> Insop
>>>>
>>>> ---
>>>> This is full output including error message.
>>>>
>>>> $ time bitbake core-image-realtime-sdk
>>>> Pseudo is not present but is required, building this first before the main
>>>> build
>>>> Parsing recipes: 100%
>>>> ||
>>>> Time: 00:00:49
>>>> Parsing of 834 .bb files complete (0 cached, 834 parsed). 1144
>>>> targets, 29 skipped, 0 masked, 0 errors.
>>>>
>>>> Build Configuration:
>>>> BB_VERSION= "1.17.1"
>>>> BUILD_SYS = "i686-linux"
>>>> NATIVELSBSTRING = "Ubuntu-12.10"
>>>> TARGET_SYS= "i586-poky-linux"
>>>> MACHINE = "fri2"
>>>> DISTRO= "poky"
>>>> DISTRO_VERSION= "1.3+snapshot-20130321"
>>>> TUNE_FEATURES = "m32 core2"
>>>> TARGET_FPU= ""
>>>> meta
>>>> meta-yocto
>>>> meta-yocto-bsp= "master:9ffee9add2d0380f4025e7a678a166f25a7d659e"
>>>> meta-intel
>>>> meta-fri2 = "master:7a5e19e0c7d5967ef7b003ab775b7210c0ee16d7"
>>>> meta-realtime = "image-sdk:6825219a33a4b4d140a01cee5165d805951d1d75"
>>>>
>>>> NOTE: Resolving any missing task queue dependencies
>>>> NOTE: Preparing runqueue
>>>> NOTE: Executing SetScene Tasks
>>>> NOTE: Executing RunQueue Tasks
>>>> NOTE: Tasks Summary: Attempted 63 tasks of which 63 didn't need to be
>>>> rerun and all succeeded.
>>>> No currently running tasks (2 of 9)
>>>> Loading cache: 100%
>>>> |##|
>>>> ETA: 00:00:00
>>>> Loaded 1145 entries from dependency cache.
>>>>
>>>> Build Configuration:
>>>> BB_VERSION= "1.17.1"
>>>> BUILD_SYS = "i686-linux"
>>>> NATIVELSBSTRING = "Ubuntu-12.10"
Re: [yocto] custom hddimg failure (mkdosfs: seek failed)
Hi Khem,
Thank you for the reply.
I've tried and it worked only if I use "tools-sdk" like below:
However, this image asks me the paaswrd, do you know?
Thank you,
Insop
=
DEPENDS = "linux-yocto"
IMAGE_FEATURES += "package-management ssh-server-dropbear"
EXTRA_IMAGE_FEATURES = "tools-sdk tools-profile"
IMAGE_INSTALL = "\
${CORE_IMAGE_BASE_INSTALL} \
rt-app \
schedtool-dl \
=
On Thu, Mar 21, 2013 at 10:58 AM, Khem Raj wrote:
> EXTRA_IMAGE_FEATURES = "tools-sdk"
>
> On Mar 21, 2013, at 1:44 AM, Insop Song wrote:
>
>> Hi,
>>
>> I am trying to add sdk (gcc ..) to meta-realtime
>> (http://git.yoctoproject.org/cgit/cgit.cgi/meta-realtime/).
>> Only difference between upstream meta-realtime is ""tools-sdk"
>>
>> -
>> require recipes-core/images/core-image-minimal-dev.bb
>>
>> DESCRIPTION = "Image with meta-realtime and sdk"
>>
>> DEPENDS = "linux-yocto"
>>
>> IMAGE_FEATURES += "package-management ssh-server-dropbear"
>> IMAGE_FEATURES += "tools-sdk"
>> EXTRA_IMAGE_FEATURES = "tools-debug debug-tweaks tools-profile dbg-pkgs"
>>
>> IMAGE_INSTALL = "\
>> ${CORE_IMAGE_BASE_INSTALL} \
>> rt-app \
>> schedtool-dl \
>> "
>>
>>
>>
>> I am keep getting hddimg failure with this message "mkdosfs: seek failed"
>>
>> I appreciate if anyone know on this issue.
>>
>> Thank you,
>>
>> Insop
>>
>> ---
>> This is full output including error message.
>>
>> $ time bitbake core-image-realtime-sdk
>> Pseudo is not present but is required, building this first before the main
>> build
>> Parsing recipes: 100%
>> ||
>> Time: 00:00:49
>> Parsing of 834 .bb files complete (0 cached, 834 parsed). 1144
>> targets, 29 skipped, 0 masked, 0 errors.
>>
>> Build Configuration:
>> BB_VERSION= "1.17.1"
>> BUILD_SYS = "i686-linux"
>> NATIVELSBSTRING = "Ubuntu-12.10"
>> TARGET_SYS= "i586-poky-linux"
>> MACHINE = "fri2"
>> DISTRO= "poky"
>> DISTRO_VERSION= "1.3+snapshot-20130321"
>> TUNE_FEATURES = "m32 core2"
>> TARGET_FPU= ""
>> meta
>> meta-yocto
>> meta-yocto-bsp= "master:9ffee9add2d0380f4025e7a678a166f25a7d659e"
>> meta-intel
>> meta-fri2 = "master:7a5e19e0c7d5967ef7b003ab775b7210c0ee16d7"
>> meta-realtime = "image-sdk:6825219a33a4b4d140a01cee5165d805951d1d75"
>>
>> NOTE: Resolving any missing task queue dependencies
>> NOTE: Preparing runqueue
>> NOTE: Executing SetScene Tasks
>> NOTE: Executing RunQueue Tasks
>> NOTE: Tasks Summary: Attempted 63 tasks of which 63 didn't need to be
>> rerun and all succeeded.
>> No currently running tasks (2 of 9)
>> Loading cache: 100%
>> |##|
>> ETA: 00:00:00
>> Loaded 1145 entries from dependency cache.
>>
>> Build Configuration:
>> BB_VERSION= "1.17.1"
>> BUILD_SYS = "i686-linux"
>> NATIVELSBSTRING = "Ubuntu-12.10"
>> TARGET_SYS= "i586-poky-linux"
>> MACHINE = "fri2"
>> DISTRO= "poky"
>> DISTRO_VERSION= "1.3+snapshot-20130321"
>> TUNE_FEATURES = "m32 core2"
>> TARGET_FPU= ""
>> meta
>> meta-yocto
>> meta-yocto-bsp= "master:9ffee9add2d0380f4025e7a678a166f25a7d659e"
>> meta-intel
>> meta-fri2 = "master:7a5e19e0c7d5967ef7b003ab775b7210c0ee16d7"
>> meta-realtime = "image-sdk:6825219a33a4b4d140a01cee5165d805951d1d75"
>>
>> NOTE: Resolving any missing task queue dependencies
>> NOTE: Preparing runqueue
>> NOTE: Executing SetScene Tasks
>> NOTE: Executing RunQueue Tasks
>> ERROR: Function failed: build_hddimg (see
>> /home/insop/mybuilds/fri2-1.4/tmp/work/fri2-poky-linux/core-image-realtime-sdk/1.0-r0/temp/log.do_bootimg.21803
>> for further information)
>> ERROR: Logfile of failure stored in:
>> /home/insop/mybuilds/fri2-1.4/tmp/work/fri2-poky
[yocto] custom hddimg failure (mkdosfs: seek failed)
Hi,
I am trying to add sdk (gcc ..) to meta-realtime
(http://git.yoctoproject.org/cgit/cgit.cgi/meta-realtime/).
Only difference between upstream meta-realtime is ""tools-sdk"
-
require recipes-core/images/core-image-minimal-dev.bb
DESCRIPTION = "Image with meta-realtime and sdk"
DEPENDS = "linux-yocto"
IMAGE_FEATURES += "package-management ssh-server-dropbear"
IMAGE_FEATURES += "tools-sdk"
EXTRA_IMAGE_FEATURES = "tools-debug debug-tweaks tools-profile dbg-pkgs"
IMAGE_INSTALL = "\
${CORE_IMAGE_BASE_INSTALL} \
rt-app \
schedtool-dl \
"
I am keep getting hddimg failure with this message "mkdosfs: seek failed"
I appreciate if anyone know on this issue.
Thank you,
Insop
---
This is full output including error message.
$ time bitbake core-image-realtime-sdk
Pseudo is not present but is required, building this first before the main build
Parsing recipes: 100%
||
Time: 00:00:49
Parsing of 834 .bb files complete (0 cached, 834 parsed). 1144
targets, 29 skipped, 0 masked, 0 errors.
Build Configuration:
BB_VERSION= "1.17.1"
BUILD_SYS = "i686-linux"
NATIVELSBSTRING = "Ubuntu-12.10"
TARGET_SYS= "i586-poky-linux"
MACHINE = "fri2"
DISTRO= "poky"
DISTRO_VERSION= "1.3+snapshot-20130321"
TUNE_FEATURES = "m32 core2"
TARGET_FPU= ""
meta
meta-yocto
meta-yocto-bsp= "master:9ffee9add2d0380f4025e7a678a166f25a7d659e"
meta-intel
meta-fri2 = "master:7a5e19e0c7d5967ef7b003ab775b7210c0ee16d7"
meta-realtime = "image-sdk:6825219a33a4b4d140a01cee5165d805951d1d75"
NOTE: Resolving any missing task queue dependencies
NOTE: Preparing runqueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
NOTE: Tasks Summary: Attempted 63 tasks of which 63 didn't need to be
rerun and all succeeded.
No currently running tasks (2 of 9)
Loading cache: 100%
|##|
ETA: 00:00:00
Loaded 1145 entries from dependency cache.
Build Configuration:
BB_VERSION= "1.17.1"
BUILD_SYS = "i686-linux"
NATIVELSBSTRING = "Ubuntu-12.10"
TARGET_SYS= "i586-poky-linux"
MACHINE = "fri2"
DISTRO= "poky"
DISTRO_VERSION= "1.3+snapshot-20130321"
TUNE_FEATURES = "m32 core2"
TARGET_FPU= ""
meta
meta-yocto
meta-yocto-bsp= "master:9ffee9add2d0380f4025e7a678a166f25a7d659e"
meta-intel
meta-fri2 = "master:7a5e19e0c7d5967ef7b003ab775b7210c0ee16d7"
meta-realtime = "image-sdk:6825219a33a4b4d140a01cee5165d805951d1d75"
NOTE: Resolving any missing task queue dependencies
NOTE: Preparing runqueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: Function failed: build_hddimg (see
/home/insop/mybuilds/fri2-1.4/tmp/work/fri2-poky-linux/core-image-realtime-sdk/1.0-r0/temp/log.do_bootimg.21803
for further information)
ERROR: Logfile of failure stored in:
/home/insop/mybuilds/fri2-1.4/tmp/work/fri2-poky-linux/core-image-realtime-sdk/1.0-r0/temp/log.do_bootimg.21803
Log data follows:
| DEBUG: Executing python function do_bootimg
| DEBUG: Executing python function build_syslinux_cfg
| DEBUG: Python function build_syslinux_cfg finished
| DEBUG: Executing python function build_grub_cfg
| DEBUG: Python function build_grub_cfg finished
| DEBUG: Executing shell function build_hddimg
| mkdosfs: seek failed
| mkdosfs 2.11 (12 Mar 2005)
| DEBUG: Python function do_bootimg finished
| ERROR: Function failed: build_hddimg (see
/home/insop/mybuilds/fri2-1.4/tmp/work/fri2-poky-linux/core-image-realtime-sdk/1.0-r0/temp/log.do_bootimg.21803
for further information)
ERROR: Task 8
(/home/insop/poky/meta-realtime/recipes-extended/images/core-image-realtime-sdk.bb,
do_bootimg) failed with exit code '1'
NOTE: Tasks Summary: Attempted 4522 tasks of which 3799 didn't need to
be rerun and 1 failed.
No currently running tasks (4522 of 4523)
Summary: 1 task failed:
/home/insop/poky/meta-realtime/recipes-extended/images/core-image-realtime-sdk.bb,
do_bootimg
Summary: There was 1 ERROR message shown, returning a non-zero exit code.
real48m10.876s
user55m35.948s
sys 9m36.128s
insop@chai ~/mybuilds/fri2-1.4 $
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [linux-yocto] [meta-realtime][PATCH 1/1] create a script directory and add a script to run test program and collect data
Thank you Bruce,
More documentations and scripts for testing and analysis the data will follow.
Regards,
Insop
On Tue, Mar 19, 2013 at 11:41 AM, Bruce Ashfield
wrote:
> On 13-03-19 07:14 AM, Insop Song wrote:
>>
>> - run_rt-app.py runs rt-app on the target machine and collects the
>>output log to host
>>
>> - how to run:
>> $ fab -f run_rt-app.py run_app
>>
>> Note: requires fabric (python program) on the host
>>
>> Signed-off-by: Insop Song
>> ---
>> docs/00-INDEX |4 +--
>> docs/00-README|6 ++--
>> scripts/README|1 +
>> scripts/run_rt-app.py | 88
>> +
>> 4 files changed, 94 insertions(+), 5 deletions(-)
>> create mode 100644 scripts/README
>> create mode 100644 scripts/run_rt-app.py
>>
>> diff --git a/docs/00-INDEX b/docs/00-INDEX
>> index 41d83a5..878e5d0 100644
>> --- a/docs/00-INDEX
>> +++ b/docs/00-INDEX
>> @@ -1,4 +1,4 @@
>> -This is a brief list of all the files in meta-virtualization/docs and
>> what
>> +This is a brief list of all the files in meta-realtime/docs and what
>> they contain. If you add a documentation file, please list it here in
>> alphabetical order as well.
>>
>> @@ -6,5 +6,5 @@ alphabetical order as well.
>> - this file.
>>
>> 00-README
>> -- info on the goals of meta-virtualization and this docs subdir
>> +- info on the goals of meta-realtime and this docs subdir
>
>
> Something strange is happening here, I had cherry picked my meta-virt
> README structure over to meta-realtime, and fixed the references .. but
> the changes didn't get pushed out. I've done that now. So I'll drop
> these chunks of the patch.
>
> Thanks for catching this.
>
> The rest looks good, and I've merged the changes.
>
> Bruce
>
>
>>
>> diff --git a/docs/00-README b/docs/00-README
>> index 6fea112..f20baca 100644
>> --- a/docs/00-README
>> +++ b/docs/00-README
>> @@ -1,6 +1,6 @@
>> -meta-virtualization: docs
>> +meta-realtime: docs
>> =
>>
>> -The docs subdirectory is a holding tank for meta-virtualization related
>> +The docs subdirectory is a holding tank for meta-realtime related
>> READMEs, documentation, testing information, configuration and other
>> -notes that help the users of meta-virt.
>> +notes that help the users of meta-realtime.
>> diff --git a/scripts/README b/scripts/README
>> new file mode 100644
>> index 000..48034e6
>> --- /dev/null
>> +++ b/scripts/README
>> @@ -0,0 +1 @@
>> +This directory contains Various useful scripts for working with
>> meta-realtime
>> diff --git a/scripts/run_rt-app.py b/scripts/run_rt-app.py
>> new file mode 100644
>> index 000..3beb20c
>> --- /dev/null
>> +++ b/scripts/run_rt-app.py
>> @@ -0,0 +1,88 @@
>> +#
>> +# run rt-app on remote machine and collect the data
>> +#
>> +# note:
>> +#
>> +# 0. install fabric 1.6 on the develop host
>> +# - $ pip install fabric
>> +#
>> +# 1. copy ssh public key (copy and paste host's "~/.ssh/id_rsa.pub" to
>> the remote's ~/.ssh/authorized_keys)
>> +#
>> +# 2. update the "env.hosts" with your remote system
>> +#
>> +# 3. run the script from the host
>> +# - $ fab -f run_rt-app.py run_app
>> +#
>> +
>> +from __future__ import with_statement
>> +from fabric.api import *
>> +from fabric.contrib import *
>> +from fabric.contrib.console import confirm
>> +
>> +import socket
>> +import getpass
>> +import datetime
>> +import time
>> +import datetime
>> +
>> +
>> +env.hosts = ['root@192.168.1.78']
>> +remote_ip = env.hosts[0]
>> +
>> +now = datetime.datetime.now()
>> +
>> +YES= "/usr/bin/yes"
>> +KILLALL= "/usr/bin/killall"
>> +SCP= "/usr/bin/scp"
>> +
>> +RTAPP = "/usr/bin/rt-app"
>> +
>> +period_t = 10
>> +run_t = 3
>> +
>> +num_run = 10
>> +sec_run = 100
>> +
>> +dir_name = "/home/root"
>> +f_name = "rt-app_run_log-%s.txt" % now.strftime("%Y-%m-%d-%H-%M")
>> +file_name = "%s/%s" % (dir_name, f_name)
>> +
>> +def pre():
>> + print
>> "\n==
[yocto] [meta-realtime][PATCH 1/1] create a script directory and add a script to run test program and collect data
- run_rt-app.py runs rt-app on the target machine and collects the
output log to host
- how to run:
$ fab -f run_rt-app.py run_app
Note: requires fabric (python program) on the host
Signed-off-by: Insop Song
---
docs/00-INDEX |4 +--
docs/00-README|6 ++--
scripts/README|1 +
scripts/run_rt-app.py | 88 +
4 files changed, 94 insertions(+), 5 deletions(-)
create mode 100644 scripts/README
create mode 100644 scripts/run_rt-app.py
diff --git a/docs/00-INDEX b/docs/00-INDEX
index 41d83a5..878e5d0 100644
--- a/docs/00-INDEX
+++ b/docs/00-INDEX
@@ -1,4 +1,4 @@
-This is a brief list of all the files in meta-virtualization/docs and what
+This is a brief list of all the files in meta-realtime/docs and what
they contain. If you add a documentation file, please list it here in
alphabetical order as well.
@@ -6,5 +6,5 @@ alphabetical order as well.
- this file.
00-README
-- info on the goals of meta-virtualization and this docs subdir
+- info on the goals of meta-realtime and this docs subdir
diff --git a/docs/00-README b/docs/00-README
index 6fea112..f20baca 100644
--- a/docs/00-README
+++ b/docs/00-README
@@ -1,6 +1,6 @@
-meta-virtualization: docs
+meta-realtime: docs
=
-The docs subdirectory is a holding tank for meta-virtualization related
+The docs subdirectory is a holding tank for meta-realtime related
READMEs, documentation, testing information, configuration and other
-notes that help the users of meta-virt.
+notes that help the users of meta-realtime.
diff --git a/scripts/README b/scripts/README
new file mode 100644
index 000..48034e6
--- /dev/null
+++ b/scripts/README
@@ -0,0 +1 @@
+This directory contains Various useful scripts for working with meta-realtime
diff --git a/scripts/run_rt-app.py b/scripts/run_rt-app.py
new file mode 100644
index 000..3beb20c
--- /dev/null
+++ b/scripts/run_rt-app.py
@@ -0,0 +1,88 @@
+#
+# run rt-app on remote machine and collect the data
+#
+# note:
+#
+# 0. install fabric 1.6 on the develop host
+# - $ pip install fabric
+#
+# 1. copy ssh public key (copy and paste host's "~/.ssh/id_rsa.pub" to the
remote's ~/.ssh/authorized_keys)
+#
+# 2. update the "env.hosts" with your remote system
+#
+# 3. run the script from the host
+# - $ fab -f run_rt-app.py run_app
+#
+
+from __future__ import with_statement
+from fabric.api import *
+from fabric.contrib import *
+from fabric.contrib.console import confirm
+
+import socket
+import getpass
+import datetime
+import time
+import datetime
+
+
+env.hosts = ['root@192.168.1.78']
+remote_ip = env.hosts[0]
+
+now = datetime.datetime.now()
+
+YES= "/usr/bin/yes"
+KILLALL= "/usr/bin/killall"
+SCP= "/usr/bin/scp"
+
+RTAPP = "/usr/bin/rt-app"
+
+period_t = 10
+run_t = 3
+
+num_run = 10
+sec_run = 100
+
+dir_name = "/home/root"
+f_name = "rt-app_run_log-%s.txt" % now.strftime("%Y-%m-%d-%H-%M")
+file_name = "%s/%s" % (dir_name, f_name)
+
+def pre():
+ print "\n==="
+ print "1. Conecting remote : %s" % env.hosts[0]
+ print "===\n"
+
+ # scripts that runs on the remote
+ un = run("uname -a", quiet=True)
+ hn = run("hostname", quiet=True)
+ print "running script on host [%s], OS[%s]" % (hn, un)
+
+#
+# run the app on the remote and collect the data into log
+#
+def main():
+ print "\n==="
+ print "2. Running rt-app %s times.." % num_run
+ print "===\n"
+
+ run('echo \"test log (period = %s, execution time %s) run %s times on
each %s sec \n\n\" > %s' % \
+ (period_t, run_t, num_run, sec_run, file_name))
+ for i in range(0, num_run):
+ run("%s -t %s:%s:d -D %s >> %s" % \
+ (RTAPP, period_t, run_t, sec_run, file_name))
+
+#
+# bring the data log to the host
+#
+def post():
+ # running this from local host
+ local("%s %s:%s ." % (SCP, remote_ip, file_name))
+
+ print
"\n=="
+ print "3. Run finished, and log file ""%s"" is copied to host." % f_name
+ print
"==\n"
+
+def run_app():
+ pre()
+ main()
+ post()
--
1.7.9.5
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-realtime][PATCH 0/1] create a script directory and add a script to run test program and collect data
create a script directory and add a script to run test program and collect data - test scripts will help to run and collect the data, automate the test and re-producible by others - run_rt-app.py runs rt-app on the target machine and collects the output log to host - how to run: $ fab -f run_rt-app.py run_app Note: requires fabric (python program) on the host -- Run example -- $ fab -f run_rt-app.py run_app [root@192.168.1.78] Executing task 'run_app' === 1. Conecting remote : root@192.168.1.78 === running script on host [fri2], OS[Linux fri2 3.8.1-yocto-standard #1 SMP PREEMPT Sat Mar 16 03:20:59 PDT 2013 i686 GNU/Linux] === 2. Running rt-app 1 times.. === [root@192.168.1.78] run: echo "test log (period = 10, execution time 2) run 1 times on each 10 sec " > /home/root/rt-app_run_log-2013-03-19-03-52.txt [root@192.168.1.78] run: /usr/bin/rt-app -t 10:2:d -D 10 >> /home/root/rt-app_run_log-2013-03-19-03-52.txt [root@192.168.1.78] out: [rt-app] [0] Using SCHED_DEADLINE policy: [root@192.168.1.78] out: [rt-app] [0] starting thread with period: 10, exec: 2,deadline: 10, priority: 10 [root@192.168.1.78] out: [rt-app] [0] Locking pages in memory [root@192.168.1.78] out: [rt-app] [0] Exiting. [root@192.168.1.78] out: [localhost] local: /usr/bin/scp root@192.168.1.78:/home/root/rt-app_run_log-2013-03-19-03-52.txt . rt-app_run_log-2013-03-19-03-52.txt 100% 7552 7.4KB/s 00:00 == 3. Run finished, and log file rt-app_run_log-2013-03-19-03-52.txt is copied to host. == Done. Disconnecting from root@192.168.1.78... done. -- Log file output -- cat /home/root/rt-app_run_log-2013-03-19-03-52.txt test log (period = 10, execution time 2) run 1 times on each 10 sec #idxperiod min_et max_et rel_st start end deadlinedur.slack Budget Used Budget 0 10 2 2 33061 1859244267 1859264275 1859344264 20008 79989 0 10 2 2 133176 1859344382 1859364389 1859444264 20007 79876 0 10 2 2 233177 1859444383 1859464391 1859544264 20009 79873 0 10 2 2 333174 1859544380 1859564389 1859644264 20009 79875 0 10 2 2 433186 1859644392 1859664402 1859744264 20010 79862 ... 0 10 2 2 9533182 1868744388 1868764398 1868844264 20009 79867 0 10 2 2 9633185 1868844391 1868864400 1868944264 20010 79864 0 10 2 2 9733182 1868944388 1868964398 1869044264 20010 79867 0 10 2 2 9833141 1869044347 1869064356 1869144264 20009 79908 0 10 2 2 9933162 1869144368 1869164375 1869244264 20007 79889 $ Insop Song (1): create a script directory and add a script to run test program and collect data docs/00-INDEX |4 +-- docs/00-README|6 ++-- scripts/README|1 + scripts/run_rt-app.py | 88 + 4 files changed, 94 insertions(+), 5 deletions(-) create mode 100644 scripts/README create mode 100644 scripts/run_rt-app.py -- 1.7.9.5 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [linux-yocto] [PATCH 0/1] [meta-realtime] Add rt-app, schedtool, define core-image-realtime, and append recipies-kernel
On Mon, Mar 18, 2013 at 7:21 AM, Bruce Ashfield wrote: > > > I went with core-image-rt-extended this morning. > > The changes have been merged, briefly tested and pushed to the > yocto layer. > > I've also created a docs/ subirectory in the layer, if you have > test steps, READMEs or other information to contribute, that's the > place we should put it. > > We can tweak this as required from here. > Thank you and will update the docs dir soon. Regards, Insop ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [question] "icecc: improve interaction with sstate"
On Sun, Mar 17, 2013 at 4:17 PM, Martin Jansa wrote: > On Fri, Mar 15, 2013 at 10:37:56PM -0700, Insop Song wrote: >> Hi, >> >> I am using HEAD of master, and I have this error after I use commit > > Please use better Subject next time, I was wondering what could be > broken by my patch to icecc and your question is quite unrelated to that > commit. > > Something like "neard failing to build with latest poky" would be > better. Yes, agree and will do better next time. Thank you. Insop ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] problems building 'neard'
I've also ran into this issue and raised in other mail thread. It seems it is fixed with the latest pull. Here was my mail response for your reference: On Sat, Mar 16, 2013 at 5:38 PM, Burton, Ross wrote: > On 16 March 2013 01:16, Insop Song wrote: >> So at this point, I will wait to see if any one is seen this recently. > > The autobuilder appears to be hitting this still, but as several > oe-core maintainers are still travelling after a conference you may > have to wait until Monday. Thank you for the update while you are on the road. I pull the latest again (http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=2381e46e77c8d33472f60861f66e44addd53af68) And it is okay now. Could be the Richard's this commit fixed it. "package_rpm: Ensure PV manipulations are correct Richard Purdie" (b5e5d25c25f30db1f9855e24afef9d8f0bb77d35) Here is my output: --- ~/mybuilds/meta-realtime $ time bitbake core-image-realtime Loading cache: 100% |##| ETA: 00:00:00 Loaded 1123 entries from dependency cache. Build Configuration: BB_VERSION= "1.17.1" BUILD_SYS = "i686-linux" NATIVELSBSTRING = "Ubuntu-12.10" TARGET_SYS= "i586-poky-linux" MACHINE = "qemux86" DISTRO= "poky" DISTRO_VERSION= "1.3+snapshot-20130316" TUNE_FEATURES = "m32 i586" TARGET_FPU= "" meta meta-yocto meta-yocto-bsp= "master:2381e46e77c8d33472f60861f66e44addd53af68" meta-realtime = "schedtool-sq:ed7886f649ab945625ccbfed0ecc74a500a7c22d" NOTE: Resolving any missing task queue dependencies NOTE: Preparing runqueue NOTE: Executing SetScene Tasks NOTE: Executing RunQueue Tasks NOTE: Tasks Summary: Attempted 3938 tasks of which 2355 didn't need to be rerun and all succeeded. real122m1.472s user514m20.641s sys 73m56.453s -- regards, Insop On Sun, Mar 17, 2013 at 2:44 PM, Martin Jansa wrote: > Update your oe-core to include > http://git.openembedded.org/openembedded-core/commit/?id=0f8447a7d99d2645b932eac1c24149f0c2d3791e > > > On Sun, Mar 17, 2013 at 10:37 PM, Trevor Woerner wrote: >> >> I'm not sure if this is specific to my host, but: >> >> Build Configuration: >> BB_VERSION= "1.17.1" >> BUILD_SYS = "x86_64-linux" >> NATIVELSBSTRING = "openSUSE-project-12.3" >> TARGET_SYS= "i586-poky-linux" >> MACHINE = "qemux86" >> DISTRO= "poky" >> DISTRO_VERSION= "1.3+snapshot-20130317" >> TUNE_FEATURES = "m32 i586" >> TARGET_FPU= "" >> meta >> meta-yocto >> meta-yocto-bsp= "master:1ceb13dda11645229053fc4840954333f8910ba4" >> >> ERROR: Function failed: BUILDSPEC (see >> /home/trevor/devel/yocto/git-method/coreimgmin/tmp/work/i586-poky-linux/neard/0.9-gitAUTOINC+1e20e396cb837017b7e5ef822bfdab6ce060d2cf-r1/temp/log.do_package_write_rpm.15728 >> for further information) >> ERROR: Logfile of failure stored in: >> /home/trevor/devel/yocto/git-method/coreimgmin/tmp/work/i586-poky-linux/neard/0.9-gitAUTOINC+1e20e396cb837017b7e5ef822bfdab6ce060d2cf-r1/temp/log.do_package_write_rpm.15728 >> Log data follows: >> | DEBUG: Executing python function sstate_task_prefunc >> | DEBUG: Python function sstate_task_prefunc finished >> | DEBUG: Executing python function do_package_write_rpm >> | DEBUG: Executing python function read_subpackage_metadata >> | DEBUG: Python function read_subpackage_metadata finished >> | DEBUG: Executing python function do_package_rpm >> | DEBUG: Executing python function write_specfile >> | NOTE: Not creating empty RPM package for neard-tests >> | NOTE: Creating RPM package for neard-dbg >> | NOTE: Not creating empty RPM package for neard-staticdev >> | NOTE: Creating RPM package for neard-dev >> | NOTE: Not creating empty RPM package for neard-doc >> | NOTE: Not creating empty RPM package for neard-locale >> | NOTE: Creating RPM package for neard >> | NOTE: Creating RPM package for neard >> | DEBUG: Python function write_specfile finished >> | DEBUG: SITE files ['endian-little', 'bit-32', 'ix86-common', >> 'common-linux', 'common-glibc', 'i586-linux', 'common'] >> | DEBUG: Executing shell function BUILDSPEC >> | error: line 152: Illegal char '-' in EVR: Suggests: neard = >> 0.9-git0+1e20e396cb837017b7e5ef822bfdab6ce060
Re: [yocto] [linux-yocto] [PATCH 0/1] [meta-realtime] Add rt-app, schedtool, define core-image-realtime, and append recipies-kernel
On Sat, Mar 16, 2013 at 9:04 PM, Bruce Ashfield wrote: > > This looks good to me now, I still think we'll have some confusion > between the core "rt" images and core-image-realtime that we are > introducing here. > > I may rename it core-image-realtime-extended as part of the merge, > if that's acceptable to you ? I think it will be something that > we'll need to revisit at some point, but that's not a good reason > to hold this back anymore. > > I'll merge, do a quick test and push this out on Monday. "core-image-realtime-extended" or "core-image-rt-extended (to be aligned with existing core-image-rt)" or something along this line sounds fine to me. I was thinking of updating my patch, but it would be better if you decide the final name, so I won't update the patch for now. Or if you know which name is the best, then just let me know, I will update the patch and send it to you. Thank you, Insop ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH 1/1] add scheedtool-dl for testing sched_deadline use jiri's github as a main repo
On Sat, Mar 16, 2013 at 10:01 PM, Khem Raj wrote:
>
> On Mar 15, 2013, at 4:47 AM, Insop Song wrote:
>
>> +SRCREV = "${AUTOREV}"
>
> IMO find a good revision and send that one here. you can use AUTOREV
> internally for your
> development thats all fine
Hi Khem,
Thank you for the review.
I've updated that already as Bruce suggested the same as well in the
latest patch update.
Here is the update patch for your reference.
Thank you.
Insop
+From 041b2b65889c44c47f90313c5bf9ce61effa96df Mon Sep 17 00:00:00 2001
+From: Insop Song
+Date: Sat, 9 Mar 2013 01:23:24 -0800
+Subject: [PATCH] set "--with-deadline" as a default to go around yocto build
+ error on deadline enabled
+
+---
+ configure.ac |2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/configure.ac b/configure.ac
+index a5e2990..64e57e4 100644
+--- a/configure.ac
b/configure.ac
+@@ -34,7 +34,7 @@ AC_ARG_WITH([deadline],
+ [AS_HELP_STRING([--with-deadline],
+ [Add support for SCHED_DEADLINE])],
+ [],
+- [with_deadline=no])
++ [with_deadline=yes])
+
+ AS_IF([test "x$with_deadline" != xno],
+ [AC_DEFINE([DLSCHED], [1], [Define if you have SCHED_DEADLINE support])
+--
+1.7.9.5
+
diff --git a/recipes-tools/rt-app/rt-app.bb b/recipes-tools/rt-app/rt-app.bb
new file mode 100644
index 000..acce437
--- /dev/null
+++ b/recipes-tools/rt-app/rt-app.bb
@@ -0,0 +1,28 @@
+DESCRIPTION = "rt-app is a test application that starts multiple
periodic threads in order to simulate a real-time periodic load"
+SECTION = "devel"
+LICENSE = "GPLv2"
+LIC_FILES_CHKSUM =
"file://COPYING;endline=339;md5=e43fc16fccd8519fba405f0a0ff6e8a3"
+PR = "r1"
+
+SRCREV = "e81cbe9f76ee298feded17bb7455d4deb2fb32af"
+
+SRC_URI = "git://github.com/gbagnoli/rt-app.git \
+ file://0001-set-with-deadline-as-a-default-to-go-around-yocto-bu.patch \
+ "
+
+S = "${WORKDIR}/git"
+
+inherit autotools gettext pkgconfig
+
+do_configure_prepend() {
+ autoreconf --install --verbose --force
+}
+
+do_install() {
+ install -d ${D}${bindir}
+ install -m 0755 src/rt-app ${D}${bindir}
+}
+
+FILES_{PN} = "${bindir}/rt-app"
+
+PARALLEL_MAKE = ""
diff --git a/recipes-tools/schedtool-dl/schedtool-dl.bb
b/recipes-tools/schedtool-dl/schedtool-dl.bb
new file mode 100644
index 000..5592175
--- /dev/null
+++ b/recipes-tools/schedtool-dl/schedtool-dl.bb
@@ -0,0 +1,23 @@
+DESCRIPTION = "schedtool-dl (scheduler test tool) for deadline scheduler"
+SECTION = "devel"
+LICENSE = "GPLv2"
+LIC_FILES_CHKSUM =
"file://Makefile;endline=55;md5=e4b4e8ed9c2132e1d727a1bb5e3bd984"
+PR = "r1"
+
+SRC_URI = "git://github.com/jlelli/schedtool-dl.git;protocol=git"
+SRCREV = "cd4e3f2f5a33c3266e25e447e8efbacb3b8c88da"
+
+S = "${WORKDIR}/git"
+
+do_compile() {
+ oe_runmake
+}
+
+do_install() {
+ install -d ${D}${bindir}
+ install -m 0755 schedtool ${D}${bindir}
+}
+
+FILES_{PN} = "${bindir}/schedtool"
+
+PARALLEL_MAKE = ""
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [question] "icecc: improve interaction with sstate"
On Sat, Mar 16, 2013 at 5:38 PM, Burton, Ross wrote: > On 16 March 2013 01:16, Insop Song wrote: >> So at this point, I will wait to see if any one is seen this recently. > > The autobuilder appears to be hitting this still, but as several > oe-core maintainers are still travelling after a conference you may > have to wait until Monday. Thank you for the update while you are on the road. I pull the latest again (http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=2381e46e77c8d33472f60861f66e44addd53af68) And it is okay now. Could be the Richard's this commit fixed it. "package_rpm: Ensure PV manipulations are correct Richard Purdie" (b5e5d25c25f30db1f9855e24afef9d8f0bb77d35) Here is my output: --- ~/mybuilds/meta-realtime $ time bitbake core-image-realtime Loading cache: 100% |##| ETA: 00:00:00 Loaded 1123 entries from dependency cache. Build Configuration: BB_VERSION= "1.17.1" BUILD_SYS = "i686-linux" NATIVELSBSTRING = "Ubuntu-12.10" TARGET_SYS= "i586-poky-linux" MACHINE = "qemux86" DISTRO= "poky" DISTRO_VERSION= "1.3+snapshot-20130316" TUNE_FEATURES = "m32 i586" TARGET_FPU= "" meta meta-yocto meta-yocto-bsp= "master:2381e46e77c8d33472f60861f66e44addd53af68" meta-realtime = "schedtool-sq:ed7886f649ab945625ccbfed0ecc74a500a7c22d" NOTE: Resolving any missing task queue dependencies NOTE: Preparing runqueue NOTE: Executing SetScene Tasks NOTE: Executing RunQueue Tasks NOTE: Tasks Summary: Attempted 3938 tasks of which 2355 didn't need to be rerun and all succeeded. real122m1.472s user514m20.641s sys 73m56.453s -- regards, Insop ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH 1/1] [meta-realtime] Add rt-app, schedtool, define core-image-realtime, and append recipies-kernel
*applications tested
1. rt-app
- "rt-app" is a test application that starts multiple periodic threads
in order to simulate a real-time periodic load
- run example
root@qemux86:~# rt-app -t 10:35000:d -D 1
[rt-app] [0] Using SCHED_DEADLINE policy:
[rt-app] [0] starting thread with period: 10, exec:
35000,deadline: 10, priority: 10
[rt-app] [0] Locking pages in memory
idx period min_et max_et rel_st start end
deadline dur.slack Budget Used Budget
0 10 35000 35000 64705 305724113 305759126
305824105 35013 64979
...
0 10 35000 35000 965099 306624507 306659526
306724105 35019 64578
[rt-app] [0] Exiting.
2. schedtool
- scheduler test tool
- run example
root@qemux86:~# schedtool -E -t 1:10 -a 0 -e yes > /dev/null&
root@qemux86:~# schedtool -E -t 3:10 -a 0 -e yes > /dev/null&
root@qemux86:~# jobs
[1]- Running schedtool -E -t 1:10 -a 0 -e yes
> /dev/null &
[2]+ Running schedtool -E -t 3:10 -a 0 -e yes
> /dev/null &
$ top
Mem: 33616K used, 84308K free, 0K shrd, 2684K buff, 13904K cached
CPU: 37% usr 5% sys 0% nic 56% idle 0% io 0% irq 0% sirq
Load average: 911.65 428.84 84.32 35501/62 715
PID PPID USER STAT VSZ %VSZ %CPU COMMAND
714 688 root R 2352 2% 28% yes
713 688 root R 2352 2% 9% yes
715 688 root R 2724 2% 4% top
---
recipes-extended/images/core-image-realtime.bb | 12 +
recipes-kernel/linux/linux-yocto_3.8.bbappend |9 +++
...adline-as-a-default-to-go-around-yocto-bu.patch | 26 ++
recipes-tools/rt-app/rt-app.bb | 28
recipes-tools/schedtool-dl/schedtool-dl.bb | 23
5 files changed, 98 insertions(+)
create mode 100644 recipes-extended/images/core-image-realtime.bb
create mode 100644 recipes-kernel/linux/linux-yocto_3.8.bbappend
create mode 100644
recipes-tools/rt-app/files/0001-set-with-deadline-as-a-default-to-go-around-yocto-bu.patch
create mode 100644 recipes-tools/rt-app/rt-app.bb
create mode 100644 recipes-tools/schedtool-dl/schedtool-dl.bb
diff --git a/recipes-extended/images/core-image-realtime.bb
b/recipes-extended/images/core-image-realtime.bb
new file mode 100644
index 000..d449e69
--- /dev/null
+++ b/recipes-extended/images/core-image-realtime.bb
@@ -0,0 +1,12 @@
+require recipes-core/images/core-image-minimal-dev.bb
+
+DEPENDS = "linux-yocto"
+
+IMAGE_FEATURES += "package-management ssh-server-dropbear"
+EXTRA_IMAGE_FEATURES = "tools-debug debug-tweaks tools-profile dbg-pkgs"
+
+IMAGE_INSTALL = "\
+ ${CORE_IMAGE_BASE_INSTALL} \
+ rt-app \
+ schedtool-dl \
+ "
diff --git a/recipes-kernel/linux/linux-yocto_3.8.bbappend
b/recipes-kernel/linux/linux-yocto_3.8.bbappend
new file mode 100644
index 000..175ab91
--- /dev/null
+++ b/recipes-kernel/linux/linux-yocto_3.8.bbappend
@@ -0,0 +1,9 @@
+FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
+
+KBRANCH_qemux86 = "standard/edf"
+KBRANCH_fri2 = "standard/edf"
+
+SRCREV_machine_qemux86 = "62d98f6b12f91cc7419b88dfa2e0abe077c94f9f"
+SRCREV_machine_fri2 = "62d98f6b12f91cc7419b88dfa2e0abe077c94f9f"
+
+KERNEL_FEATURES_append =" cfg/edf.scc"
diff --git
a/recipes-tools/rt-app/files/0001-set-with-deadline-as-a-default-to-go-around-yocto-bu.patch
b/recipes-tools/rt-app/files/0001-set-with-deadline-as-a-default-to-go-around-yocto-bu.patch
new file mode 100644
index 000..a697e89
--- /dev/null
+++
b/recipes-tools/rt-app/files/0001-set-with-deadline-as-a-default-to-go-around-yocto-bu.patch
@@ -0,0 +1,26 @@
+From 041b2b65889c44c47f90313c5bf9ce61effa96df Mon Sep 17 00:00:00 2001
+From: Insop Song
+Date: Sat, 9 Mar 2013 01:23:24 -0800
+Subject: [PATCH] set "--with-deadline" as a default to go around yocto build
+ error on deadline enabled
+
+---
+ configure.ac |2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/configure.ac b/configure.ac
+index a5e2990..64e57e4 100644
+--- a/configure.ac
b/configure.ac
+@@ -34,7 +34,7 @@ AC_ARG_WITH([deadline],
+ [AS_HELP_STRING([--with-deadline],
+ [Add support for SCHED_DEADLINE])],
+ [],
+- [with_deadline=no])
++ [with_deadline=yes])
+
+ AS_IF([test "x$with_deadline" != xno],
+ [AC_DEFINE([DLSCHED], [1], [Define if you have SCHED_DEADLINE support])
+--
+1.7.9.5
+
diff --git a/recipes-tools/rt-app/rt-app.bb b/recipes-tools/rt-app/rt-app.bb
new file mode 100644
index 000..acce437
--- /dev/null
+++ b/recipes-tools/rt-app/rt-app.bb
@@ -0,0 +1,28 @@
+DESCRIPTION = "rt-app is a test application that starts multiple periodic
threads in order to simulate a real-ti
[yocto] [PATCH 0/1] [meta-realtime] Add rt-app, schedtool, define core-image-realtime, and append recipies-kernel
meta-realtime layer for testing sched_deadline and other real-time applications Add rt-app, schedtool, define core-image-realtime, and append recipies-kernel *applications tested are shown below: 1. rt-app - "rt-app" is a test application that starts multiple periodic threads in order to simulate a real-time periodic load - run example root@qemux86:~# rt-app -t 10:35000:d -D 1 [rt-app] [0] Using SCHED_DEADLINE policy: [rt-app] [0] starting thread with period: 10, exec: 35000,deadline: 10, priority: 10 [rt-app] [0] Locking pages in memory idx period min_et max_et rel_st start end deadline dur.slack Budget Used Budget 0 10 35000 35000 64705 305724113 305759126 305824105 35013 64979 ... 0 10 35000 35000 965099 306624507 306659526 306724105 35019 64578 [rt-app] [0] Exiting. 2. schedtool - scheduler test tool - run example root@qemux86:~# schedtool -E -t 1:10 -a 0 -e yes > /dev/null& root@qemux86:~# schedtool -E -t 3:10 -a 0 -e yes > /dev/null& root@qemux86:~# jobs [1]- Running schedtool -E -t 1:10 -a 0 -e yes > /dev/null & [2]+ Running schedtool -E -t 3:10 -a 0 -e yes > /dev/null & $ top Mem: 33616K used, 84308K free, 0K shrd, 2684K buff, 13904K cached CPU: 37% usr 5% sys 0% nic 56% idle 0% io 0% irq 0% sirq Load average: 911.65 428.84 84.32 35501/62 715 PID PPID USER STAT VSZ %VSZ %CPU COMMAND 714 688 root R 2352 2% 28% yes 713 688 root R 2352 2% 9% yes 715 688 root R 2724 2% 4% top Insop Song (1): Add rt-app, schedtool, define core-image-realtime, and append recipies-kernel recipes-extended/images/core-image-realtime.bb | 12 + recipes-kernel/linux/linux-yocto_3.8.bbappend |9 +++ ...adline-as-a-default-to-go-around-yocto-bu.patch | 26 ++ recipes-tools/rt-app/rt-app.bb | 28 recipes-tools/schedtool-dl/schedtool-dl.bb | 23 5 files changed, 98 insertions(+) create mode 100644 recipes-extended/images/core-image-realtime.bb create mode 100644 recipes-kernel/linux/linux-yocto_3.8.bbappend create mode 100644 recipes-tools/rt-app/files/0001-set-with-deadline-as-a-default-to-go-around-yocto-bu.patch create mode 100644 recipes-tools/rt-app/rt-app.bb create mode 100644 recipes-tools/schedtool-dl/schedtool-dl.bb -- 1.7.9.5 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH 1/1] add scheedtool-dl for testing sched_deadline use jiri's github as a main repo
On Fri, Mar 15, 2013 at 7:46 AM, Bruce Ashfield
wrote:
> On 13-03-15 04:47 AM, Insop Song wrote:
>>
>> ---
>> recipes-extended/images/core-image-realtime.bb |1 +
>> recipes-tools/schedtool-dl/schedtool-dl.bb | 23
>> +++
>> 2 files changed, 24 insertions(+)
>> create mode 100644 recipes-tools/schedtool-dl/schedtool-dl.bb
>>
>> diff --git a/recipes-extended/images/core-image-realtime.bb
>> b/recipes-extended/images/core-image-realtime.bb
>> index 624aacf..386b16b 100644
>> --- a/recipes-extended/images/core-image-realtime.bb
>> +++ b/recipes-extended/images/core-image-realtime.bb
>> @@ -8,5 +8,6 @@ EXTRA_IMAGE_FEATURES = "tools-debug debug-tweaks
>> tools-profile dbg-pkgs"
>> IMAGE_INSTALL = "\
>> ${CORE_IMAGE_BASE_INSTALL} \
>> rt-app \
>> + schedtool-dl \
>> libgcc \
>> "
>
>
> This part of the patch is still a problem, so I'll drop it on merge.
> We still need to rationalize why we can't extend the oe-core
> rt images:
>
> ./recipes-rt/images/core-image-rt.bb
> ./recipes-rt/images/core-image-rt-sdk.bb
>
> For this addition. Until we work through that, you can carry a local
> patch, or add the tools back via your local.conf adding it to IMAGE_INSTALL.
>
>
I put the "libgcc" because rt-app complained during finish regarding
pthread and libgcc during my previous meta-realtime/meta-dl, which was
using core-image-minimal.
Since, I updated my image bases this time, I might not need it.
I will test without "libgcc" and will update the patch.
I've updated my poky tree to the latest, and I am having trouble due
to "neard" package failure (I post a question on this).
That's why it's taking long to verify and update the patch.
>> diff --git a/recipes-tools/schedtool-dl/schedtool-dl.bb
>> b/recipes-tools/schedtool-dl/schedtool-dl.bb
>> new file mode 100644
>> index 000..6b298f1
>> --- /dev/null
>> +++ b/recipes-tools/schedtool-dl/schedtool-dl.bb
>> @@ -0,0 +1,23 @@
>> +DESCRIPTION = "schedtool-dl (scheduler test tool) for deadline scheduler"
>> +SECTION = "devel"
>> +LICENSE = "GPLv2"
>> +LIC_FILES_CHKSUM =
>> "file://Makefile;endline=55;md5=e4b4e8ed9c2132e1d727a1bb5e3bd984"
>> +PR = "r1"
>> +
>> +SRC_URI = "git://github.com/jlelli/schedtool-dl.git;protocol=git"
>> +SRCREV = "${AUTOREV}"
>
>
> We also want to lock down the SRCREV vs autorev. I'd expect that going
> forward,
> you can maintain/update this once we've merged it, so when a SRCREV
> is known to be good, you can send update patches with the new values
> (just like I do with linux-yocto in oe-core). But in the general case,
> we want to have consistent and reproducible builds and to do that,
> we need a well defined SRCREV.
>
updated and testing is in-progress.
> So one more version of the series and we should be good (you can
> drop the image addition as part of that) .. sorry for all the
> iterations, the first merges always take the longest.
>
I appreciate your through review and will send out the revision soon
as I am done testing.
Insop
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Loading a new yocto image to Intel Fri2 board
On Fri, Mar 15, 2013 at 8:58 AM, Darren Hart wrote: > > Check this image, I think you'll find that rootwait is missing for this > image. > yes, no rootwait for "sda" type generation. Regards, Insop ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [question] "icecc: improve interaction with sstate"
Wither further more testing, even at "e609afe4d747059480b406602cab90b7c36a0572", I still get the neard error. I suspect my sstate or working files, since this error comes at package generation. So I did "-c cleansstate" "-c cleanall" then run it with Richard fix as my master head (7803f5f98cf4d12d59ac793d9eb0048b701cafb7) It still gives me an error. So at this point, I will wait to see if any one is seen this recently. Thank you. Insop On Fri, Mar 15, 2013 at 10:55 PM, Insop Song wrote: > On Fri, Mar 15, 2013 at 10:45 PM, Burton, Ross wrote: >> On 15 March 2013 22:37, Insop Song wrote: >>> I am using HEAD of master, and I have this error after I use commit >>> >>> " >>> commit 1ceb13dda11645229053fc4840954333f8910ba4 >>> Author: Martin Jansa >>> Date: Wed Mar 13 20:04:51 2013 +0100 >>> " >>> >>> Could anyone know about this? >> >> Are you sure you're using head? This should have been fixed with this >> commit: >> >> https://bugzilla.yoctoproject.org/show_bug.cgi?id=4022 >> >> Ross > > Thank you for the information. > Yes, I am on master, see this from my log in previous email. > I have the fix for the bug (4022) in my master, but that don't fix it, > until I my my head to "e609afe4d747059480b406602cab90b7c36a0572" > >> meta >> meta-yocto= "master:1ceb13dda11645229053fc4840954333f8910ba4" >> meta-realtime = "schedtool:a766d16a1cf4da3c2dd13b8c7e53f89775733187" >> meta-yocto-bsp= "master:1ceb13dda11645229053fc4840954333f8910ba4" > > Thank you, > > Insop ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [question] "icecc: improve interaction with sstate"
On Fri, Mar 15, 2013 at 10:45 PM, Burton, Ross wrote: > On 15 March 2013 22:37, Insop Song wrote: >> I am using HEAD of master, and I have this error after I use commit >> >> " >> commit 1ceb13dda11645229053fc4840954333f8910ba4 >> Author: Martin Jansa >> Date: Wed Mar 13 20:04:51 2013 +0100 >> " >> >> Could anyone know about this? > > Are you sure you're using head? This should have been fixed with this commit: > > https://bugzilla.yoctoproject.org/show_bug.cgi?id=4022 > > Ross Thank you for the information. Yes, I am on master, see this from my log in previous email. I have the fix for the bug (4022) in my master, but that don't fix it, until I my my head to "e609afe4d747059480b406602cab90b7c36a0572" > meta > meta-yocto= "master:1ceb13dda11645229053fc4840954333f8910ba4" > meta-realtime = "schedtool:a766d16a1cf4da3c2dd13b8c7e53f89775733187" > meta-yocto-bsp= "master:1ceb13dda11645229053fc4840954333f8910ba4" Thank you, Insop ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [question] "icecc: improve interaction with sstate"
Hi, Sorry, I pressed "send" too quick. Not the first commit, but after this commit I see the following error in my first email. Any one see this? Author: Olivier Guiter 2013-03-12 13:33:52 Committer: Richard Purdie 2013-03-14 18:53:04 Parent: e609afe4d747059480b406602cab90b7c36a0572 (qemu-native:fix do_compile failed on SLED 11.2) Child: 31c134bc2c5be925edcb13804f35651a7b325acc (inputproto: upgrade to 2.3) Branch: remotes/origin/master Follows: 1.4_M4.final, 1.4_M4.rc1 Precedes: - Regards, Insop On Fri, Mar 15, 2013 at 10:37 PM, Insop Song wrote: > Hi, > > I am using HEAD of master, and I have this error after I use commit > > " > commit 1ceb13dda11645229053fc4840954333f8910ba4 > Author: Martin Jansa > Date: Wed Mar 13 20:04:51 2013 +0100 > " > > Could anyone know about this? > > > - my config > > Build Configuration: > BB_VERSION= "1.17.1" > BUILD_SYS = "x86_64-linux" > NATIVELSBSTRING = "Ubuntu-12.04" > TARGET_SYS= "i586-poky-linux" > MACHINE = "qemux86" > DISTRO= "poky" > DISTRO_VERSION= "1.3+snapshot-20130316" > TUNE_FEATURES = "m32 i586" > TARGET_FPU= "" > meta > meta-yocto= "master:1ceb13dda11645229053fc4840954333f8910ba4" > meta-realtime = "schedtool:a766d16a1cf4da3c2dd13b8c7e53f89775733187" > meta-yocto-bsp= "master:1ceb13dda11645229053fc4840954333f8910ba4" > > > - error output: > ERROR: Function failed: BUILDSPEC (see > /home/insop/mybuilds/meta-realtime/tmp/work/i586-poky-linux/neard/0.9-gitAUTOINC+1e20e396cb837017b7e5ef822bfdab6ce060d2cf-r1/temp/log.do_package_write_rpm.31563 > for further information) > ERROR: Logfile of failure stored in: > /home/insop/mybuilds/meta-realtime/tmp/work/i586-poky-linux/neard/0.9-gitAUTOINC+1e20e396cb837017b7e5ef822bfdab6ce060d2cf-r1/temp/log.do_package_write_rpm.31563 > > > > - full output: > > ~/mybuilds/meta-realtime $ time bitbake core-image-realtime > Loading cache: 100% > || > ETA: 00:00:00 > Loaded 1121 entries from dependency cache. > Parsing recipes: 100% > |##| > Time: 00:00:00 > Parsing of 813 .bb files complete (812 cached, 1 parsed). 1121 > targets, 27 skipped, 0 masked, 0 errors. > > Build Configuration: > BB_VERSION= "1.17.1" > BUILD_SYS = "x86_64-linux" > NATIVELSBSTRING = "Ubuntu-12.04" > TARGET_SYS= "i586-poky-linux" > MACHINE = "qemux86" > DISTRO= "poky" > DISTRO_VERSION= "1.3+snapshot-20130316" > TUNE_FEATURES = "m32 i586" > TARGET_FPU= "" > meta > meta-yocto= "master:1ceb13dda11645229053fc4840954333f8910ba4" > meta-realtime = "schedtool:a766d16a1cf4da3c2dd13b8c7e53f89775733187" > meta-yocto-bsp= "master:1ceb13dda11645229053fc4840954333f8910ba4" > > NOTE: Resolving any missing task queue dependencies > NOTE: Preparing runqueue > NOTE: Executing SetScene Tasks > NOTE: Executing RunQueue Tasks > ERROR: Function failed: BUILDSPEC (see > /home/insop/mybuilds/meta-realtime/tmp/work/i586-poky-linux/neard/0.9-gitAUTOINC+1e20e396cb837017b7e5ef822bfdab6ce060d2cf-r1/temp/log.do_package_write_rpm.31563 > for further information) > ERROR: Logfile of failure stored in: > /home/insop/mybuilds/meta-realtime/tmp/work/i586-poky-linux/neard/0.9-gitAUTOINC+1e20e396cb837017b7e5ef822bfdab6ce060d2cf-r1/temp/log.do_package_write_rpm.31563 > Log data follows: > | DEBUG: Executing python function sstate_task_prefunc > | DEBUG: Python function sstate_task_prefunc finished > | DEBUG: Executing python function do_package_write_rpm > | DEBUG: Executing python function read_subpackage_metadata > | DEBUG: Python function read_subpackage_metadata finished > | DEBUG: Executing python function do_package_rpm > | DEBUG: Executing python function write_specfile > | NOTE: Not creating empty RPM package for neard-tests > | NOTE: Creating RPM package for neard-dbg > | NOTE: Not creating empty RPM package for neard-staticdev > | NOTE: Creating RPM package for neard-dev > | NOTE: Not creating empty RPM package for neard-doc > | NOTE: Not creating empty RPM package for neard-locale > | NOTE: Creating RPM package for neard > | NOTE: Creating RPM package for neard > | DEBUG: Python function write_specfile finished > | DEBUG: SITE files ['endian-little', 'bit-32', 'ix
[yocto] [question] "icecc: improve interaction with sstate"
Hi, I am using HEAD of master, and I have this error after I use commit " commit 1ceb13dda11645229053fc4840954333f8910ba4 Author: Martin Jansa Date: Wed Mar 13 20:04:51 2013 +0100 " Could anyone know about this? - my config Build Configuration: BB_VERSION= "1.17.1" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "Ubuntu-12.04" TARGET_SYS= "i586-poky-linux" MACHINE = "qemux86" DISTRO= "poky" DISTRO_VERSION= "1.3+snapshot-20130316" TUNE_FEATURES = "m32 i586" TARGET_FPU= "" meta meta-yocto= "master:1ceb13dda11645229053fc4840954333f8910ba4" meta-realtime = "schedtool:a766d16a1cf4da3c2dd13b8c7e53f89775733187" meta-yocto-bsp= "master:1ceb13dda11645229053fc4840954333f8910ba4" - error output: ERROR: Function failed: BUILDSPEC (see /home/insop/mybuilds/meta-realtime/tmp/work/i586-poky-linux/neard/0.9-gitAUTOINC+1e20e396cb837017b7e5ef822bfdab6ce060d2cf-r1/temp/log.do_package_write_rpm.31563 for further information) ERROR: Logfile of failure stored in: /home/insop/mybuilds/meta-realtime/tmp/work/i586-poky-linux/neard/0.9-gitAUTOINC+1e20e396cb837017b7e5ef822bfdab6ce060d2cf-r1/temp/log.do_package_write_rpm.31563 - full output: ~/mybuilds/meta-realtime $ time bitbake core-image-realtime Loading cache: 100% || ETA: 00:00:00 Loaded 1121 entries from dependency cache. Parsing recipes: 100% |##| Time: 00:00:00 Parsing of 813 .bb files complete (812 cached, 1 parsed). 1121 targets, 27 skipped, 0 masked, 0 errors. Build Configuration: BB_VERSION= "1.17.1" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "Ubuntu-12.04" TARGET_SYS= "i586-poky-linux" MACHINE = "qemux86" DISTRO= "poky" DISTRO_VERSION= "1.3+snapshot-20130316" TUNE_FEATURES = "m32 i586" TARGET_FPU= "" meta meta-yocto= "master:1ceb13dda11645229053fc4840954333f8910ba4" meta-realtime = "schedtool:a766d16a1cf4da3c2dd13b8c7e53f89775733187" meta-yocto-bsp= "master:1ceb13dda11645229053fc4840954333f8910ba4" NOTE: Resolving any missing task queue dependencies NOTE: Preparing runqueue NOTE: Executing SetScene Tasks NOTE: Executing RunQueue Tasks ERROR: Function failed: BUILDSPEC (see /home/insop/mybuilds/meta-realtime/tmp/work/i586-poky-linux/neard/0.9-gitAUTOINC+1e20e396cb837017b7e5ef822bfdab6ce060d2cf-r1/temp/log.do_package_write_rpm.31563 for further information) ERROR: Logfile of failure stored in: /home/insop/mybuilds/meta-realtime/tmp/work/i586-poky-linux/neard/0.9-gitAUTOINC+1e20e396cb837017b7e5ef822bfdab6ce060d2cf-r1/temp/log.do_package_write_rpm.31563 Log data follows: | DEBUG: Executing python function sstate_task_prefunc | DEBUG: Python function sstate_task_prefunc finished | DEBUG: Executing python function do_package_write_rpm | DEBUG: Executing python function read_subpackage_metadata | DEBUG: Python function read_subpackage_metadata finished | DEBUG: Executing python function do_package_rpm | DEBUG: Executing python function write_specfile | NOTE: Not creating empty RPM package for neard-tests | NOTE: Creating RPM package for neard-dbg | NOTE: Not creating empty RPM package for neard-staticdev | NOTE: Creating RPM package for neard-dev | NOTE: Not creating empty RPM package for neard-doc | NOTE: Not creating empty RPM package for neard-locale | NOTE: Creating RPM package for neard | NOTE: Creating RPM package for neard | DEBUG: Python function write_specfile finished | DEBUG: SITE files ['endian-little', 'bit-32', 'ix86-common', 'common-linux', 'common-glibc', 'i586-linux', 'common'] | DEBUG: Executing shell function BUILDSPEC | error: line 152: Illegal char '-' in EVR: Suggests: neard = 0.9-git0+1e20e396cb837017b7e5ef822bfdab6ce060d2cf-r1 | error: Package has no %description: neard-dbg.i586 | Building target platforms: i586-poky-linux | DEBUG: Python function do_package_rpm finished | DEBUG: Python function do_package_write_rpm finished | ERROR: Function failed: BUILDSPEC (see /home/insop/mybuilds/meta-realtime/tmp/work/i586-poky-linux/neard/0.9-gitAUTOINC+1e20e396cb837017b7e5ef822bfdab6ce060d2cf-r1/temp/log.do_package_write_rpm.31563 for further information) ERROR: Task 1370 (/home/insop/poky/meta/recipes-connectivity/neard/neard_0.9.bb, do_package_write_rpm) failed with exit code '1' NOTE: Tasks Summary: Attempted 3322 tasks of which 3281 didn't need to be rerun and 1 failed. Waiting for 0 running tasks to finish: Summary: 1 task failed: /home/insop/poky/meta/recipes-connectivity/neard/neard_0.9.bb, do_package_write_rpm Summary: There was 1 ERROR message shown, returning a non-zero exit code. real0m27.611s user0m30.158s sys 0m4.900s ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-realtime][PATCH] add sched_deadline reckpies-kernel for 3.8 kernel
On Thu, Mar 14, 2013 at 11:27 PM, Bruce Ashfield wrote: > > I was just merging your changes, and realized that gmail may have dropped > your schedtool-dl recipe. > > Can you resend it with your updated series ? I have another schedtool > recipe here, but it's against an older sched_dl release, so I'd like to > compare it to yours and merge the two of them together. I've sent out a new patch that has schedtool_dl. I used Juri's github as a main repo, which he has been updating recently. So now, I will look more on scripts for testing using these applications. Also will look to see the test and data collection using ftrace. I've done this before, but I will make it more easier to reproducible using meta-realtime layer. Let me know if you have any suggestion. Regards, Insop ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH 1/1] add scheedtool-dl for testing sched_deadline use jiri's github as a main repo
---
recipes-extended/images/core-image-realtime.bb |1 +
recipes-tools/schedtool-dl/schedtool-dl.bb | 23 +++
2 files changed, 24 insertions(+)
create mode 100644 recipes-tools/schedtool-dl/schedtool-dl.bb
diff --git a/recipes-extended/images/core-image-realtime.bb
b/recipes-extended/images/core-image-realtime.bb
index 624aacf..386b16b 100644
--- a/recipes-extended/images/core-image-realtime.bb
+++ b/recipes-extended/images/core-image-realtime.bb
@@ -8,5 +8,6 @@ EXTRA_IMAGE_FEATURES = "tools-debug debug-tweaks tools-profile
dbg-pkgs"
IMAGE_INSTALL = "\
${CORE_IMAGE_BASE_INSTALL} \
rt-app \
+ schedtool-dl \
libgcc \
"
diff --git a/recipes-tools/schedtool-dl/schedtool-dl.bb
b/recipes-tools/schedtool-dl/schedtool-dl.bb
new file mode 100644
index 000..6b298f1
--- /dev/null
+++ b/recipes-tools/schedtool-dl/schedtool-dl.bb
@@ -0,0 +1,23 @@
+DESCRIPTION = "schedtool-dl (scheduler test tool) for deadline scheduler"
+SECTION = "devel"
+LICENSE = "GPLv2"
+LIC_FILES_CHKSUM =
"file://Makefile;endline=55;md5=e4b4e8ed9c2132e1d727a1bb5e3bd984"
+PR = "r1"
+
+SRC_URI = "git://github.com/jlelli/schedtool-dl.git;protocol=git"
+SRCREV = "${AUTOREV}"
+
+S = "${WORKDIR}/git"
+
+do_compile() {
+ oe_runmake
+}
+
+do_install() {
+ install -d ${D}${bindir}
+ install -m 0755 schedtool ${D}${bindir}
+}
+
+FILES_{PN} = "${bindir}/schedtool"
+
+PARALLEL_MAKE = ""
--
1.7.9.5
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH 0/1] add scheedtool-dl for testing sched_deadline
add scheedtool-dl for testing sched_deadline Insop Song (1): add scheedtool-dl for testing sched_deadline use jiri's github as a main repo recipes-extended/images/core-image-realtime.bb |1 + recipes-tools/schedtool-dl/schedtool-dl.bb | 23 +++ 2 files changed, 24 insertions(+) create mode 100644 recipes-tools/schedtool-dl/schedtool-dl.bb -- 1.7.9.5 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [linux-yocto] [meta-realtime][PATCH] add sched_deadline reckpies-kernel for 3.8 kernel
On Thu, Mar 14, 2013 at 11:46 PM, Bruce Ashfield wrote: > > I hit send too soon, I meant to point out that in a situation such > as this, you can ammend your original commit with your second set > of change and re-submit just the single patch. I can squash the > commits here, but it's easier to do on your end. > > Just summarize the v2 in your new patch email when you ammend/squash > changes, so we won't forget what was changed :) > Yup, sent out a squashed patch just now. Regards, Insop ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-realtime][PATCH] add sched_deadline reckpies-kernel for 3.8 kernel
On Thu, Mar 14, 2013 at 11:44 PM, Bruce Ashfield wrote: > > Are you trying to send via git send-email ? The following is the > way that I'd relay through gmail: > > > git send-email --smtp-server smtp.gmail.com --smtp-user > bruce.ashfi...@gmail.com --smtp-pass --smtp-ssl ~/rr/ > > And to generate the patches and introductory email, look at > the oe-core scripts/create-pull-request. > > That's the best and easiest way to send patches. > Thank you for the information. I have to create a new application specific password from gmail (2 phase password). Once I set that up, I am able to send patch/cover email. Regards, Insop ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH 1/1] add sched_deadline reckpies-kernel for 3.8 kernel
---
recipes-kernel/linux/linux-yocto_3.8.bbappend |9 +
1 file changed, 9 insertions(+)
create mode 100644 recipes-kernel/linux/linux-yocto_3.8.bbappend
diff --git a/recipes-kernel/linux/linux-yocto_3.8.bbappend
b/recipes-kernel/linux/linux-yocto_3.8.bbappend
new file mode 100644
index 000..175ab91
--- /dev/null
+++ b/recipes-kernel/linux/linux-yocto_3.8.bbappend
@@ -0,0 +1,9 @@
+FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
+
+KBRANCH_qemux86 = "standard/edf"
+KBRANCH_fri2 = "standard/edf"
+
+SRCREV_machine_qemux86 = "62d98f6b12f91cc7419b88dfa2e0abe077c94f9f"
+SRCREV_machine_fri2 = "62d98f6b12f91cc7419b88dfa2e0abe077c94f9f"
+
+KERNEL_FEATURES_append =" cfg/edf.scc"
--
1.7.9.5
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH 0/1] add sched_deadline reckpies-kernel for 3.8 kernel
add sched_deadline reckpies-kernel for 3.8 kernel Insop Song (1): add sched_deadline reckpies-kernel for 3.8 kernel recipes-kernel/linux/linux-yocto_3.8.bbappend |9 + 1 file changed, 9 insertions(+) create mode 100644 recipes-kernel/linux/linux-yocto_3.8.bbappend -- 1.7.9.5 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Loading a new yocto image to Intel Fri2 board
On Thu, Mar 14, 2013 at 1:15 PM, Darren Hart wrote: > On 03/14/2013 12:56 PM, Insop Song wrote: >> Hi Darren, >> >> mkefidisk.sh works, thank you. >> >> What I found was, USB still doesn't work even with mkefidisk.sh. >> So I used micro sd card instead. > > Aha, yes. You will need to add "rootwait" to your kernel command line > for reliable booting over usb. There is no way I see to determine if USB > is being used (/dev/sda could just as easily be SATA). Perhaps mkefidisk > should just use rootwait by default. Patches accepted. > "rootwait" was there. 1. when I run "sudo ~/bin/mkefidisk.sh /dev/sda core-image-sato-sdk-fri2-20130309091839.hddimg /dev/mmcblk0" but "root=" was set to mmcblk0. So I changed "root=" manually to sda2, usb is booted as well. yes, I should have put the last parameter to be "/dev/sda" instead.. 2. so when I run "sudo ~/bin/mkefidisk.sh /dev/sda core-image-sato-sdk-fri2-20130309091839.hddimg /dev/sda" USB is also working fine. Thank you very much for the help, now I can use fri2 to test "meta-realtime" Insop ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-realtime][PATCH] add sched_deadline reckpies-kernel for 3.8 kernel
On Thu, Mar 14, 2013 at 11:13 PM, Bruce Ashfield
wrote:
>
> Hmm. One of the arbiters is me .. if it doesn't work this time, let me know
> and I'll check the list membership.
I've just signed up and got a confirmation email.
>>
>> I was do some testing on "make localmodconfig", which will gets me the
>> using module build .config.
>> So let me me ask you this before I send out an updated patch.
>>
>> I ran "lsmod > /tmp/lsmod" on my qemux86
>> On dev host, run "make LSMOD=/tmp/lsmod localmodconfig" to get this
>> localmodconfig_qemux86.cfg file, which has less module configurations.
>>
>> Then I use this in bbappend file like below:
>>
>> ---
>> SRC_URI =
>> "git://git.yoctoproject.org/linux-yocto-3.8.git;protocol=git;bareclone=1;branch=${KBRANCH},${KMETA};name=machine,meta
>> \
>> file://localmodconfig_qemux86.cfg \
>> "
>>
>>
>> what do you think?
>
> We want to track the modules and policies of the main qemu BSP,
> not override them all here. Extra layers should be only changing board
> functionality that is specific to their functionality, not the base board
> configuration.
>
> If you think there are modules that are enabled that shouldn't be, we
> can address that by looking at the base policy and deciding if that
> base policy is wrong.
>
> Cheers,
>
I see, let me follow up the current patch update and do some more look
on qemu bsp and deal with a separate patch.
Here are the update patches 2/2.
And let me know if you want to see in different ways of patch
delivery? since, I haven't set up my gmail smtp set up yet (due to
application specific athentication), so I manually copy and paste and
attach the files.
--
Subject: [meta-realtime][PATCH 2/2] remove edf.cfg and follow up review
feedback
---
recipes-kernel/linux/linux-yocto/edf.cfg |4
recipes-kernel/linux/linux-yocto_3.8.bbappend |5 -
2 files changed, 9 deletions(-)
delete mode 100644 recipes-kernel/linux/linux-yocto/edf.cfg
diff --git a/recipes-kernel/linux/linux-yocto/edf.cfg
b/recipes-kernel/linux/linux-yocto/edf.cfg
deleted file mode 100644
index ccf004f..000
--- a/recipes-kernel/linux/linux-yocto/edf.cfg
+++ /dev/null
@@ -1,4 +0,0 @@
-CONFIG_CGROUPS=y
-CONFIG_CGROUP_SCHED=y
-CONFIG_DEADLINE_GROUP_SCHED=y
-
diff --git a/recipes-kernel/linux/linux-yocto_3.8.bbappend
b/recipes-kernel/linux/linux-yocto_3.8.bbappend
index c6a969f..175ab91 100644
--- a/recipes-kernel/linux/linux-yocto_3.8.bbappend
+++ b/recipes-kernel/linux/linux-yocto_3.8.bbappend
@@ -1,13 +1,8 @@
FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
-COMPATIBLE_MACHINE_qemux86 = "qemux86"
-COMPATIBLE_MACHINE_fri2 = "fri2"
KBRANCH_qemux86 = "standard/edf"
KBRANCH_fri2 = "standard/edf"
-KMACHINE_qemux86 = "qemux86"
-KMACHINE_fri2 = "fri2"
-
SRCREV_machine_qemux86 = "62d98f6b12f91cc7419b88dfa2e0abe077c94f9f"
SRCREV_machine_fri2 = "62d98f6b12f91cc7419b88dfa2e0abe077c94f9f"
--
1.7.9.5
0001-add-sched_deadline-reckpies-kernel-for-3.8-kernel.patch
Description: Binary data
0002-remove-edf.cfg-and-follow-up-review-feedback.patch
Description: Binary data
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-realtime][PATCH] add sched_deadline reckpies-kernel for 3.8 kernel
On Thu, Mar 14, 2013 at 10:15 PM, Bruce Ashfield
wrote:
>
> FYI: your email keeps bouncing from the linux-yocto mailing list,
> check to be sure you signed up with your gmail account, I keep
> approving them for now :)
>
I've signed up last time you suggested, I will try one more and send a
separate email to the arbiter.
Thank you for reminding me.
>
>>
>> - tested on qemux86
>> ===
>>
>> root@qemux86:~# uname -a
>> Linux qemux86 3.8.1-yocto-standard #1 SMP PREEMPT Thu Mar 14 21:57:12
>> PDT 2013 i686 GNU/Linux
>> root@qemux86:~# rt-app -t 10:35000:d -D 2
>> [rt-app] [0] Using SCHED_DEADLINE policy:
>> [rt-app] [0] starting thread with period: 10, exec:
>> 35000,deadline: 10, priority: 10
>> [rt-app] [0] Locking pages in memory
>> #idxperiod min_et max_et rel_st start end
>> deadlinedur.slack Budget Used
>> Budget
>> 0 10 35000 35000 65466 354577907 354612918
>> 354677899 35011 64981
>> 0 10 35000 35000 165585 354678026 354713105
>> 354777899 35079 64794
>> ...
>> 0 10 35000 35000 1965672 356478113 356513126
>> 356577899 35014 64772
>> [rt-app] [0] Exiting.
>> root@qemux86:~#
>>
>> ===
>>
>> Let me know what you think.
>>
>> Regards,
>>
>> Insop
>>
>> ===
>>
>>
>> Subject: [meta-realtime][PATCH] add sched_deadline reckpies-kernel for 3.8
>> kernel
>>
>> ---
>> recipes-kernel/linux/linux-yocto/edf.cfg |4
>> recipes-kernel/linux/linux-yocto_3.8.bbappend | 14 ++
>> 2 files changed, 18 insertions(+)
>> create mode 100644 recipes-kernel/linux/linux-yocto/edf.cfg
>> create mode 100644 recipes-kernel/linux/linux-yocto_3.8.bbappend
>>
>> diff --git a/recipes-kernel/linux/linux-yocto/edf.cfg
>> b/recipes-kernel/linux/linux-yocto/edf.cfg
>> new file mode 100644
>> index 000..ccf004f
>> --- /dev/null
>> +++ b/recipes-kernel/linux/linux-yocto/edf.cfg
>> @@ -0,0 +1,4 @@
>> +CONFIG_CGROUPS=y
>> +CONFIG_CGROUP_SCHED=y
>> +CONFIG_DEADLINE_GROUP_SCHED=y
>
>
> We don't need this fragment in recipe space, it's already in the
> kernel tree itself.
>
> I've already sent the pull request for the meta SRCREVs to be updated,
> so it's available for all builds now.
>
>
removed.
>> +
>> diff --git a/recipes-kernel/linux/linux-yocto_3.8.bbappend
>> b/recipes-kernel/linux/linux-yocto_3.8.bbappend
>> new file mode 100644
>> index 000..c6a969f
>> --- /dev/null
>> +++ b/recipes-kernel/linux/linux-yocto_3.8.bbappend
>> @@ -0,0 +1,14 @@
>> +FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
>> +COMPATIBLE_MACHINE_qemux86 = "qemux86"
>> +COMPATIBLE_MACHINE_fri2 = "fri2"
>
>
> These are already taken care of by meta-intel, we don't need to
> duplicate them here.
>
>
You meant two lines of "COMPATIBLE_MACHINE..."?
removed.
>> +
>> +KBRANCH_qemux86 = "standard/edf"
>> +KBRANCH_fri2 = "standard/edf"
>> +
>> +KMACHINE_qemux86 = "qemux86"
>> +KMACHINE_fri2 = "fri2"
>
>
> We don't need these two KMACHINE lines, this is the default.
>
removed.
I was do some testing on "make localmodconfig", which will gets me the
using module build .config.
So let me me ask you this before I send out an updated patch.
I ran "lsmod > /tmp/lsmod" on my qemux86
On dev host, run "make LSMOD=/tmp/lsmod localmodconfig" to get this
localmodconfig_qemux86.cfg file, which has less module configurations.
Then I use this in bbappend file like below:
---
SRC_URI =
"git://git.yoctoproject.org/linux-yocto-3.8.git;protocol=git;bareclone=1;branch=${KBRANCH},${KMETA};name=machine,meta
\
file://localmodconfig_qemux86.cfg \
"
what do you think?
let me know, I can either just fix the current patch and add new patch or
just do the current patch fix.
Thank you.
Insop
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-realtime][PATCH] add sched_deadline reckpies-kernel for 3.8 kernel
Hi Bruce,
I've added recipes-kernel to use edf branch and cfg.
- tested on qemux86
===
root@qemux86:~# uname -a
Linux qemux86 3.8.1-yocto-standard #1 SMP PREEMPT Thu Mar 14 21:57:12
PDT 2013 i686 GNU/Linux
root@qemux86:~# rt-app -t 10:35000:d -D 2
[rt-app] [0] Using SCHED_DEADLINE policy:
[rt-app] [0] starting thread with period: 10, exec:
35000,deadline: 10, priority: 10
[rt-app] [0] Locking pages in memory
#idxperiod min_et max_et rel_st start end
deadlinedur.slack Budget Used
Budget
0 10 35000 35000 65466 354577907 354612918
354677899 35011 64981
0 10 35000 35000 165585 354678026 354713105
354777899 35079 64794
...
0 10 35000 35000 1965672 356478113 356513126
356577899 35014 64772
[rt-app] [0] Exiting.
root@qemux86:~#
===
Let me know what you think.
Regards,
Insop
===
Subject: [meta-realtime][PATCH] add sched_deadline reckpies-kernel for 3.8
kernel
---
recipes-kernel/linux/linux-yocto/edf.cfg |4
recipes-kernel/linux/linux-yocto_3.8.bbappend | 14 ++
2 files changed, 18 insertions(+)
create mode 100644 recipes-kernel/linux/linux-yocto/edf.cfg
create mode 100644 recipes-kernel/linux/linux-yocto_3.8.bbappend
diff --git a/recipes-kernel/linux/linux-yocto/edf.cfg
b/recipes-kernel/linux/linux-yocto/edf.cfg
new file mode 100644
index 000..ccf004f
--- /dev/null
+++ b/recipes-kernel/linux/linux-yocto/edf.cfg
@@ -0,0 +1,4 @@
+CONFIG_CGROUPS=y
+CONFIG_CGROUP_SCHED=y
+CONFIG_DEADLINE_GROUP_SCHED=y
+
diff --git a/recipes-kernel/linux/linux-yocto_3.8.bbappend
b/recipes-kernel/linux/linux-yocto_3.8.bbappend
new file mode 100644
index 000..c6a969f
--- /dev/null
+++ b/recipes-kernel/linux/linux-yocto_3.8.bbappend
@@ -0,0 +1,14 @@
+FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
+COMPATIBLE_MACHINE_qemux86 = "qemux86"
+COMPATIBLE_MACHINE_fri2 = "fri2"
+
+KBRANCH_qemux86 = "standard/edf"
+KBRANCH_fri2 = "standard/edf"
+
+KMACHINE_qemux86 = "qemux86"
+KMACHINE_fri2 = "fri2"
+
+SRCREV_machine_qemux86 = "62d98f6b12f91cc7419b88dfa2e0abe077c94f9f"
+SRCREV_machine_fri2 = "62d98f6b12f91cc7419b88dfa2e0abe077c94f9f"
+
+KERNEL_FEATURES_append =" cfg/edf.scc"
--
1.7.9.5
0001-add-sched_deadline-reckpies-kernel-for-3.8-kernel.patch
Description: Binary data
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH] [meta-realtime] Add rt-app and define core-image-realtime
On Thu, Mar 14, 2013 at 1:56 PM, Bruce Ashfield wrote: > On 13-03-14 12:52 PM, Insop Song wrote: > > This patch looks ok, what are the differences from your original > layer ? I've already imported changes from there, so I'd just > like to hear about differences between the two. > do_configure with --with-deadline option fails, that's why I've added a patch to set "deadline" option by default instead of getting it from configure. I've tried to figure out the do_configure failure but was not able to figure it out. You can try this without my patch and add "--with-deadline" to configure. > I also have schedtool staged in the tree already, if you wait > until tomorrow, I can push that tree and you can test and extend > that base. > Sounds good. Regards, Insop ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Loading a new yocto image to Intel Fri2 board
Hi Darren, mkefidisk.sh works, thank you. What I found was, USB still doesn't work even with mkefidisk.sh. So I used micro sd card instead. I will use sd card for now, so it should be fine for now. Regards, Insop On Wed, Mar 13, 2013 at 10:03 AM, Darren Hart wrote: > On 03/10/2013 04:16 AM, Insop Song wrote: >> Hi, >> >> I have a question on loading a new yocto image to Intel Fri2 board. >> >> 1. Board: Intel Fri2 >> -- >> >> 2. Image: self built sato image with meta-fri2 >> -- >> I've followed an instruction from >> http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/tree/meta-fri2/README >> so do dd image of my sato image to usb as described >> - "dd if=core-image-sato-fri2-20101207053738.hddimg of=/dev/sdf" > > > Assuming you have the Intel provided UEFI fastboot firmware, I would > suggest using scripts/contrib/mkefidisk.sh rather than dd'ing the > hddimg. The hddimg is not in a format that is well supported by EFI. > > mkefidisk.sh partitions the target device and creates a proper EFI > partition and a root partition. > > >> >> 3. Sympton: stuck during boot and no ttyusb access >> -- >> And connect it to the host USB port. >> Then I can see the new grub menu that has "boot" and "install", so >> selected "boot" >> >> However, booting was stuck at around this line, >> - ":03:0a.2: ttyPCH1 at I/O 0x2050 (irq = 41) is a pch_uart" >> >> And I am not able to get the ttyUSB console working either. > > > You don't see GRUB over the serial port? Do you see the UEFI shell on > the serial port. Does the ttyUSB* device appear on your host machine? > Are you configured at 115200 8n1? > > >> 4. Others: official sato image for Fri2 is not working either >> -- >> Also just to make sure I "dd" the image from the official hdd img, but >> the result is the same as my own image. >> >> Anyone has tried the same? please let me know. > > > Try mkefidisk.sh and let us know the result. > > -- > Darren Hart > Intel Open Source Technology Center > Yocto Project - Technical Lead - Linux Kernel ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH] [meta-realtime] Add rt-app and define core-image-realtime
Hi Bruce,
This is for adding rt-app, please let me know what you think.
For next patch, I will add schedtool_dl
Regards,
Insop
--
- "rt-app" is a test application that starts multiple periodic threads
in order to simulate a real-time periodic load
- run example
root@qemux86:~# rt-app -t 10:35000:d -D 1
[rt-app] [0] Using SCHED_DEADLINE policy:
[rt-app] [0] starting thread with period: 10, exec:
35000,deadline: 10, priority: 10
[rt-app] [0] Locking pages in memory
deadline dur.slack Budget Used Budget
0 10 35000 35000 64705 305724113 305759126
305824105 35013 64979
0 10 35000 35000 165100 305824508 305859531
0 10 35000 35000 864955 306524363 306559381
306624105 35019 64724
0 10 35000 35000 965099 306624507 306659526
306724105 35019 64578
[rt-app] [0] Exiting.
---
recipes-extended/images/core-image-realtime.bb | 12 +
...adline-as-a-default-to-go-around-yocto-bu.patch | 26 ++
recipes-tools/rt-app/rt-app.bb | 28
3 files changed, 66 insertions(+)
create mode 100644 recipes-extended/images/core-image-realtime.bb
create mode 100644
recipes-tools/rt-app/files/0001-set-with-deadline-as-a-default-to-go-around-yocto-bu.patch
create mode 100644 recipes-tools/rt-app/rt-app.bb
diff --git a/recipes-extended/images/core-image-realtime.bb
b/recipes-extended/images/core-image-realtime.bb
new file mode 100644
index 000..624aacf
--- /dev/null
+++ b/recipes-extended/images/core-image-realtime.bb
@@ -0,0 +1,12 @@
+require recipes-core/images/core-image-minimal-dev.bb
+
+DEPENDS = "linux-yocto"
+
+IMAGE_FEATURES += "package-management ssh-server-dropbear"
+EXTRA_IMAGE_FEATURES = "tools-debug debug-tweaks tools-profile dbg-pkgs"
+
+IMAGE_INSTALL = "\
+ ${CORE_IMAGE_BASE_INSTALL} \
+ rt-app \
+ libgcc \
+ "
diff --git
a/recipes-tools/rt-app/files/0001-set-with-deadline-as-a-default-to-go-around-yocto-bu.patch
b/recipes-tools/rt-app/files/0001-set-with-deadline-as-a-default-to-go-around-yocto-bu.patch
new file mode 100644
index 000..a697e89
--- /dev/null
+++
b/recipes-tools/rt-app/files/0001-set-with-deadline-as-a-default-to-go-around-yocto-bu.patch
@@ -0,0 +1,26 @@
+From 041b2b65889c44c47f90313c5bf9ce61effa96df Mon Sep 17 00:00:00 2001
+From: Insop Song
+Date: Sat, 9 Mar 2013 01:23:24 -0800
+Subject: [PATCH] set "--with-deadline" as a default to go around yocto build
+ error on deadline enabled
+
+---
+ configure.ac |2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/configure.ac b/configure.ac
+index a5e2990..64e57e4 100644
+--- a/configure.ac
b/configure.ac
+@@ -34,7 +34,7 @@ AC_ARG_WITH([deadline],
+ [AS_HELP_STRING([--with-deadline],
+ [Add support for SCHED_DEADLINE])],
+ [],
+- [with_deadline=no])
++ [with_deadline=yes])
+
+ AS_IF([test "x$with_deadline" != xno],
+ [AC_DEFINE([DLSCHED], [1], [Define if you have SCHED_DEADLINE support])
+--
+1.7.9.5
+
diff --git a/recipes-tools/rt-app/rt-app.bb b/recipes-tools/rt-app/rt-app.bb
new file mode 100644
index 000..acce437
--- /dev/null
+++ b/recipes-tools/rt-app/rt-app.bb
@@ -0,0 +1,28 @@
+DESCRIPTION = "rt-app is a test application that starts multiple
periodic threads in order to simulate a real-time periodic load"
+SECTION = "devel"
+LICENSE = "GPLv2"
+LIC_FILES_CHKSUM =
"file://COPYING;endline=339;md5=e43fc16fccd8519fba405f0a0ff6e8a3"
+PR = "r1"
+
+SRCREV = "e81cbe9f76ee298feded17bb7455d4deb2fb32af"
+
+SRC_URI = "git://github.com/gbagnoli/rt-app.git \
+ file://0001-set-with-deadline-as-a-default-to-go-around-yocto-bu.patch \
+ "
+
+S = "${WORKDIR}/git"
+
+inherit autotools gettext pkgconfig
+
+do_configure_prepend() {
+ autoreconf --install --verbose --force
+}
+
+do_install() {
+ install -d ${D}${bindir}
+ install -m 0755 src/rt-app ${D}${bindir}
+}
+
+FILES_{PN} = "${bindir}/rt-app"
+
+PARALLEL_MAKE = ""
--
1.7.9.5
0001-Add-rt-app-and-define-core-image-realtime.patch
Description: Binary data
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] A question on adding a new program to a new meta layer
On Mon, Mar 11, 2013 at 10:03 AM, Bruce Ashfield wrote: > > If you are looking for push access, we'll wait on that for a bit. I'd like > to throttle changes into the new layer by sending them to the linux-yocto > mailing list first, have some review and then we can do a pull request > and merge model. > I see, that sounds fine for me. I just wasn't sure ways of working here. Thank you, Insop ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] A question on adding a new program to a new meta layer
On Mon, Mar 11, 2013 at 7:34 AM, Bruce Ashfield wrote: > > As an example, I have a schedtool recipe that uses the > git://gitorious.org/sched_deadline/schedtool-dl.git > repository with a 4 patch series to enable full sched_deadline/EDF > support versus the custom repository that you created on github. > We'll work to unify the edf and other -rt support in the upstream > projects, so we want to reference those trees whenever possible (unless > we get so much development, that a tracking tree makes sense). > Agree, It's better to unify. I will look into and will update you more on this. > Also, don't be concerned that I show up as the only maintainer in the > meta-realtime layer, as I merge parts from your existing layer, credit > will be given and if it is ok with you, I'll have you down as a maintainer > or co-maintainer where it makes sense. > > Since I'm going to be out of the office for the next few days, I may > push out my initial merges without much testing, so if you have a > chance to test, and send patches .. that would be a great help. > Could you tell me how to get the access to the git.yoctoproject? If you are busy due to OOO, don't worry on this. I should be able to manage in local git until you come back. Thank you. Insop ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] A question on adding a new program to a new meta layer
On Sun, Mar 10, 2013 at 8:28 PM, Bruce Ashfield > > Expect that the yocto project hosted meta-realtime will appear in a > week or so. I'm doing the legwork at the moment, but with some travel > in the upcoming week, the initial push will be delayed by a few days. > > Cheers, > > Bruce > > That's great! I saw the place holder on the git.yoctoproject this morning. Please let me know if you need anything for me to do or test. Regards, Insop ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Loading a new yocto image to Intel Fri2 board
Adding Scott, as I've followed the same procedure as described in "Hands-on Intro Lab on Barcelona 2012" by Scott. On Sun, Mar 10, 2013 at 4:16 AM, Insop Song wrote: > Hi, > > I have a question on loading a new yocto image to Intel Fri2 board. > > 1. Board: Intel Fri2 > -- > > 2. Image: self built sato image with meta-fri2 > -- > I've followed an instruction from > http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/tree/meta-fri2/README > so do dd image of my sato image to usb as described > - "dd if=core-image-sato-fri2-20101207053738.hddimg of=/dev/sdf" > > 3. Sympton: stuck during boot and no ttyusb access > -- > And connect it to the host USB port. > Then I can see the new grub menu that has "boot" and "install", so > selected "boot" > > However, booting was stuck at around this line, > - ":03:0a.2: ttyPCH1 at I/O 0x2050 (irq = 41) is a pch_uart" > > And I am not able to get the ttyUSB console working either. > > 4. Others: official sato image for Fri2 is not working either > -- > Also just to make sure I "dd" the image from the official hdd img, but > the result is the same as my own image. > > Anyone has tried the same? please let me know. > > Thank you very much, > > Insop ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Loading a new yocto image to Intel Fri2 board
Hi, I have a question on loading a new yocto image to Intel Fri2 board. 1. Board: Intel Fri2 -- 2. Image: self built sato image with meta-fri2 -- I've followed an instruction from http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/tree/meta-fri2/README so do dd image of my sato image to usb as described - "dd if=core-image-sato-fri2-20101207053738.hddimg of=/dev/sdf" 3. Sympton: stuck during boot and no ttyusb access -- And connect it to the host USB port. Then I can see the new grub menu that has "boot" and "install", so selected "boot" However, booting was stuck at around this line, - ":03:0a.2: ttyPCH1 at I/O 0x2050 (irq = 41) is a pch_uart" And I am not able to get the ttyUSB console working either. 4. Others: official sato image for Fri2 is not working either -- Also just to make sure I "dd" the image from the official hdd img, but the result is the same as my own image. Anyone has tried the same? please let me know. Thank you very much, Insop ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] A question on adding a new program to a new meta layer
On Fri, Mar 8, 2013 at 3:35 PM, Bruce Ashfield wrote: > On 13-03-08 12:01 PM, Darren Hart wrote: >> >> >> >> On 03/04/2013 08:04 PM, Insop Song wrote: >>> >>> Hi, >>> >>> I am preparing a new meta layer for testing and promoting a >>> sched_deadline scheduler, called "meta-dl". I am planning to add >>> scheduler testing tools and different kernel versions as well. >>> - http://insop.github.com/meta-dl/ >> >> >> Note that qemux86 doesn't support the EMGD graphics driver. You mention >> this and its license in the README, but it isn't necessary. If you are >> pulling that in, there is a problem with your recipes. > > > wow. mailing list delays are making this conversation *extremely* > painful and disjointed. > > Darren, Those that you've mentioned were from yocto kernel lab examples. I went over and cleaned them up. https://github.com/insop/meta-dl However, at this point, I am more looking at meta-realtime that uses yocto-linux-3.8 instead as Bruce's suggestion. https://github.com/insop/meta-realtime >> >> So you are using the sched_deadline patches, but not PREEMPT_RT, is that >> right? I had always assumed sched_deadline ran on top of PREEMPT_RT (but >> I haven't every tried building it myself). > > > sched_deadline applies to mainline, right on top of CFS as a scheduler > class. So in fact, I wouldn't suggest it with preempt-rt at all at the > moment. > > Right, previously, Juri maintained sched_deadline on top of preempt-rt, but not any more. >> >> What you have here is a good experimental layer. Looking forward, please >> consider: >> >> o Incorporating sched_deadline as a kernel feature into the >> linux-yocto_3.8 kernel. We can easily add recipes to build a >> linux-yocto-deadline kernel and you will get all the benefits of the >> yocto tooling, testing, bugfixing, and free forward porting. > > > Already done. I've had it in linux-yocto-3.8 since I first introduced > it. We just need the supporting userspace to easily change the > scheduler class for a process. > > Yup, two apps that can test sched_deadline is at meta-realtime now. I will prepare some script to make it easier as well. >> >> o Incorporating your tests into (poky|oe-core)/meta/recipes-rt > > > Or if they aren't fully 'core', our new meta-realtime that I'd like > to have created shortly. > I will be playing with meta-realtime at github until you create one. Please let me know if you have any other requested program on this layer. Regards, Insop ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] A question on adding a new program to a new meta layer
On Thu, Mar 7, 2013 at 6:04 AM, Bruce Ashfield wrote: > On 13-03-07 12:05 AM, Insop Song wrote: >> >> Bruce, >> >> That's very good. I will bring linux-yocto-3.8 kernel to meta-dl. >> (https://github.com/insop/meta-dl/tree/linux-yocto-3.8) > > > I have another suggestion to offer here, one I've been wanting to > do for a bit. > > I've added Darren Hart to the thread, since I'd like to hear from > him on this as well. > > I have a use for the scheduling tools and benchmark cases for some > virtualization usecases (meta-virtualization on git.yoctoproject.org). > > We already have "recipes-rt" in oe-core, and the preempt-rt kernel > available from linux-yocto, and as we've been discussing I've added > support for EDF/sched_dealine in linux-yocto-3.8. > > I'm not a fan of having to many layers, but rather than putting these > efforts in github layers, hiding them in meta-virtualiation and they > aren't yet "core" enough to go in oe-core .. I'd rather see them > conslidated in a "meta-realtime" (or whatever name we decide on) > layer on git.yoctoproject.org. > meta-realtime sounds good to me, and this can include schedulers real-time application and testing suits. > There are also ideas around interrupt management, AMP, and alternative > system partitioning that I'd like to drive into such a layer. > Good idea to add these continuously to the "meta-realtime" > A quick scan of the layer index, doesn't show anything that matches > this description. So I'm suggesting that we create a new layer > to consolidate these approaches, and a layer that can be consumed by > some of the other layers that are currently in progress. > > Comments ? In particular, point out a layer that already does this that > I've missed. > > I've took out machine related from my previous meta-dl-qemux86 and put together meta-realtime as a starting point. It has two sched_deadline testing program. It's on github for now for your reference, but I am willing to move or merge to git.yocto. https://github.com/insop/meta-realtime Thank you, Insop ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] A question on adding a new program to a new meta layer
Moved to master and built 3.8 with "standard/edf" branch and all working fine.
Thank you.
Insop
On Thu, Mar 7, 2013 at 5:47 PM, Bruce Ashfield
wrote:
> On 13-03-07 5:02 PM, Insop Song wrote:
>>
>> One observation and question:
>>
>> 1. I can build core-image-minimal/sato with meta-dl (with github 3.8
>> or yocto-3.8 kernel) with yocto on "danny-8.0" tag
>> 2. I cannot build a successfully bootable core-image-minimal (with
>> meta-dl) with yocto on "1.4_M4" tag,
>> the image was stuck during booting..
>>
>> My build machine is Ubuntu 12.04 LTS.
>>
>> Before I debug more, I want to check with you to see if there is any
>> thing that you can think of.
>> Since I am planning to move to the yocto's master, so that I can pick
>> up "linux-yocto_3.8.bb".
>
>
> Nothing comes to mind. It all depends on what target you are using, and
> if you are using the 'defconfig' that you mentioned earlier. Switching
> to the linux-yocto policy and BSP fragments will likely fix your problem.
>
> Bruce
>
>
>>
>> Thank you,
>>
>> Insop
>>
>>
>> On Thu, Mar 7, 2013 at 6:05 AM, Bruce Ashfield
>> wrote:
>>>
>>> On 13-03-07 03:26 AM, Insop Song wrote:
>>>>
>>>>
>>>> Hi Bruce,
>>>>
>>>> One more question on 3.8 kernel.
>>>> Is "meta/recipes-kernel/linux/linux-yocto_3.8.bb" added soon as well in
>>>> 1.4?
>>>
>>>
>>>
>>> It's in master as of a few days ago. So it's available and
>>> ready for use.
>>>
>>> Cheers,
>>>
>>> Bruce
>>>
>>>
>>>>
>>>> I am using 1.4_M4.final now.
>>>>
>>>> Thank you.
>>>>
>>>> Insop
>>>>
>>>> On Wed, Mar 6, 2013 at 9:05 PM, Insop Song wrote:
>>>>>
>>>>>
>>>>> Bruce,
>>>>>
>>>>> That's very good. I will bring linux-yocto-3.8 kernel to meta-dl.
>>>>> (https://github.com/insop/meta-dl/tree/linux-yocto-3.8)
>>>>>
>>>>> The purposes of meta-dl are the following three:
>>>>> 1. easy to use sched_deadline by providing recipes-kernel that includes
>>>>> - git url including github and from yocto-kernel
>>>>>
>>>>> 2. easy to test and validate sched_deadline with automated
>>>>> reproducible test suits
>>>>> - currently, rt-app and schedtool are included in meta-dl
>>>>> - will add test scripts
>>>>>
>>>>> 3. provide and test on different targets/bsps
>>>>> - will prepare and test on different targets (bsp)
>>>>>
>>>>> #1 is done as I've tested with kernel from github from Juri and
>>>>> yocto-kernel-3.8 that you've merged.
>>>>> #2 and #3 are in-progress.
>>>>>
>>>>> I've talked Juri the other day and gather information on testing
>>>>> methods and scripts so I will include this to meta-dl.
>>>>>
>>>>> I agree that it's good to coordinate the effort, so please feel free
>>>>> to let me know if you have any suggestion.
>>>>>
>>>>> Regards,
>>>>>
>>>>> Insop
>>>>>
>>>>> * updated kernel recipes
>>>>> @ -9,12 +9,15 @@ inherit kernel
>>>>>
>>>>>#SRCREV ="031d31cfaa1e0c00122bf52639e340353d3b8360"
>>>>>SRCREV ="${AUTOREV}"
>>>>> -KBRANCH = "sched-dl-V7"
>>>>> -SRC_URI =
>>>>> "git://github.com/insop/sched-deadline;protocol=git;branch=${KBRANCH}
>>>>> \
>>>>> +#KBRANCH = "sched-dl-V7"
>>>>> +#SRC_URI =
>>>>> "git://github.com/insop/sched-deadline;protocol=git;branch=${KBRANCH}
>>>>> \
>>>>> +# file://defconfig "
>>>>> +KBRANCH = "standard/edf"
>>>>> +SRC_URI =
>>>>>
>>>>> "git://git.yoctoproject.org/linux-yocto-3.8;protocol=git;branch=${KBRANCH}
>>>>> \
>>>>> file://defconfig "
>>>>>
>>>>>PV = "3.8"
>>>>> -PR = "dl7"
>>>>> +PR = "dl"
>>>>>
>>>>>KSRC
Re: [yocto] qemu not getting dhcp question.
Hi Khem, > > runqemu already assigns a static IP to instance and it does not use bridging > so dhcp from a server which is not the machine on which qemu is running will > not work > > Right, this testing was from my own meta-dl-qemux86 (custom kernel and recipes). https://github.com/insop/meta-dl The image that I've created did not use static IP but attempted to get dhcp, so that' was the issue. I still have to look at what was the issue within my image (meta layer), but now I've moved to latest yocto-kernel-3.8 and the image uses the static IP. Thank you. Insop ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] A question on adding a new program to a new meta layer
>> >> Could you also add me in the announcement list? > > > I can definitely do that. > > Also if you sign up for the linux-yo...@yoctoproject.org > mailing list, that's where announcements and kernel feature discussions > happen around linux-yocto. It would be a great place (versus this > main yocto mailing list) to talk about sched_deadline in particular. > Thank you and I've signed up for linux-yo...@yoctoproject.org, and will send to that list for the next mail. Insop ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] A question on adding a new program to a new meta layer
One observation and question:
1. I can build core-image-minimal/sato with meta-dl (with github 3.8
or yocto-3.8 kernel) with yocto on "danny-8.0" tag
2. I cannot build a successfully bootable core-image-minimal (with
meta-dl) with yocto on "1.4_M4" tag,
the image was stuck during booting..
My build machine is Ubuntu 12.04 LTS.
Before I debug more, I want to check with you to see if there is any
thing that you can think of.
Since I am planning to move to the yocto's master, so that I can pick
up "linux-yocto_3.8.bb".
Thank you,
Insop
On Thu, Mar 7, 2013 at 6:05 AM, Bruce Ashfield
wrote:
> On 13-03-07 03:26 AM, Insop Song wrote:
>>
>> Hi Bruce,
>>
>> One more question on 3.8 kernel.
>> Is "meta/recipes-kernel/linux/linux-yocto_3.8.bb" added soon as well in
>> 1.4?
>
>
> It's in master as of a few days ago. So it's available and
> ready for use.
>
> Cheers,
>
> Bruce
>
>
>>
>> I am using 1.4_M4.final now.
>>
>> Thank you.
>>
>> Insop
>>
>> On Wed, Mar 6, 2013 at 9:05 PM, Insop Song wrote:
>>>
>>> Bruce,
>>>
>>> That's very good. I will bring linux-yocto-3.8 kernel to meta-dl.
>>> (https://github.com/insop/meta-dl/tree/linux-yocto-3.8)
>>>
>>> The purposes of meta-dl are the following three:
>>> 1. easy to use sched_deadline by providing recipes-kernel that includes
>>> - git url including github and from yocto-kernel
>>>
>>> 2. easy to test and validate sched_deadline with automated
>>> reproducible test suits
>>> - currently, rt-app and schedtool are included in meta-dl
>>> - will add test scripts
>>>
>>> 3. provide and test on different targets/bsps
>>> - will prepare and test on different targets (bsp)
>>>
>>> #1 is done as I've tested with kernel from github from Juri and
>>> yocto-kernel-3.8 that you've merged.
>>> #2 and #3 are in-progress.
>>>
>>> I've talked Juri the other day and gather information on testing
>>> methods and scripts so I will include this to meta-dl.
>>>
>>> I agree that it's good to coordinate the effort, so please feel free
>>> to let me know if you have any suggestion.
>>>
>>> Regards,
>>>
>>> Insop
>>>
>>> * updated kernel recipes
>>> @ -9,12 +9,15 @@ inherit kernel
>>>
>>> #SRCREV ="031d31cfaa1e0c00122bf52639e340353d3b8360"
>>> SRCREV ="${AUTOREV}"
>>> -KBRANCH = "sched-dl-V7"
>>> -SRC_URI =
>>> "git://github.com/insop/sched-deadline;protocol=git;branch=${KBRANCH}
>>> \
>>> +#KBRANCH = "sched-dl-V7"
>>> +#SRC_URI =
>>> "git://github.com/insop/sched-deadline;protocol=git;branch=${KBRANCH}
>>> \
>>> +# file://defconfig "
>>> +KBRANCH = "standard/edf"
>>> +SRC_URI =
>>> "git://git.yoctoproject.org/linux-yocto-3.8;protocol=git;branch=${KBRANCH}
>>> \
>>> file://defconfig "
>>>
>>> PV = "3.8"
>>> -PR = "dl7"
>>> +PR = "dl"
>>>
>>> KSRC ?= ""
>>> S = '${@base_conditional("KSRC", "", "${WORKDIR}/git", "${KSRC}", d)}'
>>>
>>> Thank you.
>>>
>>> Insop
>>>
>>> On Wed, Mar 6, 2013 at 8:00 PM, Bruce Ashfield
>>> wrote:
>>>>
>>>> On 13-03-05 1:54 AM, Insop Song wrote:
>>>>>
>>>>>
>>>>> Hi,
>>>>>
>>>>> I am preparing a new meta layer for testing and promoting a
>>>>> sched_deadline scheduler, called "meta-dl". I am planning to add
>>>>> scheduler testing tools and different kernel versions as well.
>>>>> - http://insop.github.com/meta-dl/
>>>>
>>>>
>>>>
>>>> FYI: I've already merged and staged sched_dl in linux-yocto_3.8:
>>>>
>>>>
>>>> http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-3.8/log/?h=standard/edf
>>>>
>>>> I'll be supporting it there as well, so it makes sense to coordinate
>>>> our efforts around kernels, configurations and benchmarks.
>>>>
>>>> Juri and I talked about this @ ELC a few weeks ago (I've added
>>>> him to the cc as well), and rather than hiding sched_deadline
>>&g
Re: [yocto] A question on adding a new program to a new meta layer
> > Thanks Juri, I was going to add you to my linux-yocto-3.8 announcement > email and due to some last minute debug activities .. it slipped my > mind. So I'm using this thread to let you, and anyone else that is > interested know that sched_deadline support is available to try out > in linux-yocto-3.8. > Could you also add me in the announcement list? > >> >> As I already told to Insop, I don't have any automated test for the >> patchset, but I usually run different scenarios using basically this >> two tools (and giving a look at simple cases through kernelshark): >> >> 1- schedtool-dl: https://github.com/jlelli/schedtool-dl >> the idea here is to let a 'yes' run through SCHED_DEADLINE and >> check through kernelshark that the bandwidth enforcement >> mechanism works. >> >> 2- rt-app: https://github.com/gbagnoli/rt-app >> with this I usually let some tasksets run for several hours on >> a 48-cores machine we have in our lab, I can provide the tasksets >> (json files) and the script to run them. >> >> Please let me know how I can help further. > > > This is a good start. I have some old references to tests that I'll > dig up as well. > You can check this recipes-tool to find out the above programs (configuration and installation) in here, https://github.com/insop/meta-dl/tree/sched-dl-V7/recipes-tools > I'm looking to develop some "real world" examples of the scheduler > class in action, since as we've been saying .. getting those examples > will both help the approach and perhaps help get it merged into the > mainline kernel. > I've been looking application descriptions when I was in Ericsson, and provided cases to Thomas and Juri. I am interested in this as well, and include them in easy-to test/validate form. I will also reply to your other mail shortly. Regards, Insop ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] A question on adding a new program to a new meta layer
Hi Bruce,
> What do you have in your "defconfig" ? I'm about to push patches that
> will make enabling sched_dealine a KERNEL_FEATURE option, which makes
> it even easier to use.
>
Here is my defconfg
https://github.com/insop/meta-dl/blob/sched-dl-V7/recipes-kernel/linux/linux/defconfig
I've asked this to Juri, too. So this is for the config for sched_deadline
"Every defconfig kernel should compile and work
fine (given HZ=1000, NO_HZ not set and HRTIMERS=y)"
And here are the CONFIG that should set (Juri, please let us know if
I miss anything)
--
CONFIG_EXPERIMENTAL = y
CONFIG_CGROUPS = y
CONFIG_CGROUP_SCHED = n
CONFIG_HIGH_RES_TIMERS = y
CONFIG_PREEMPT = y
CONFIG_PREEMPT_RT = y
CONFIG_HZ_1000 = y
# CONFIG_NO_HZ is not set
--
> But in the meantime, if you want to enable the support on a yocto BSP,
> you can change your "defconfig" to be "sched-deadline.cfg" and only
> put the kernel options required to enable the feature.
I will pick up yocto-3.8 bb file from "master" branch and will try
this way shortly.
Regards,
Insop
>
> Cheers,
>
> Bruce
>
>
>>
>> PV = "3.8"
>> -PR = "dl7"
>> +PR = "dl"
>>
>> KSRC ?= ""
>> S = '${@base_conditional("KSRC", "", "${WORKDIR}/git", "${KSRC}", d)}'
>>
>> Thank you.
>>
>> Insop
>>
>> On Wed, Mar 6, 2013 at 8:00 PM, Bruce Ashfield
>> wrote:
>>>
>>> On 13-03-05 1:54 AM, Insop Song wrote:
>>>>
>>>>
>>>> Hi,
>>>>
>>>> I am preparing a new meta layer for testing and promoting a
>>>> sched_deadline scheduler, called "meta-dl". I am planning to add
>>>> scheduler testing tools and different kernel versions as well.
>>>> - http://insop.github.com/meta-dl/
>>>
>>>
>>>
>>> FYI: I've already merged and staged sched_dl in linux-yocto_3.8:
>>>
>>>
>>> http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-3.8/log/?h=standard/edf
>>>
>>> I'll be supporting it there as well, so it makes sense to coordinate
>>> our efforts around kernels, configurations and benchmarks.
>>>
>>> Juri and I talked about this @ ELC a few weeks ago (I've added
>>> him to the cc as well), and rather than hiding sched_deadline
>>> kernel support in a custom kernel layer, I'd like to try and get
>>> more eyes on it via linux-yocto .. so if we can all coordinate our
>>> efforts here, that would be much better.
>>>
>>> Cheers,
>>>
>>> Bruce
>>>
>>>>
>>>> With the help of hands-on kernel lab (thank you Tom and Darren), I am
>>>> able to make kernel with sched_deadline enabled.
>>>>
>>>>
>>>> Now, I am having some trouble of adding testing tools to this meta-dl,
>>>> and hope I can get some help from you.
>>>>
>>>> - problem: adding a new software into my meta-dl layer
>>>>
>>>> - symtom and questions?
>>>> 1. bitbake core-image-minimal (normal image build) won't include the
>>>> additional program that I listed in .bb file below
>>>> 2. If I do "bitbake schedtool-dl -c install" it builds and install,
>>>> but at "i586" location instead of my machine staging rootfs
>>>> (dl-qemux86)
>>>>
>>>>
>>>>
>>>> - Here is my .bb file that pulls an additional program.
>>>>
>>>>
>>>> https://github.com/insop/meta-dl/blob/sched-dl-V7/recipes-tools/schedtool-dl/schedtool-dl.bb
>>>> ===
>>>> DESCRIPTION = "schedtool-dl (scheduler test tool) for deadline
>>>> scheduler"
>>>> HOMEPAGE = "https://github.com/insop/schedtool-dl";
>>>> SECTION = "base"
>>>> LICENSE = "GPLv2"
>>>> LIC_FILES_CHKSUM =
>>>> "file://Makefile;endline=55;md5=e4b4e8ed9c2132e1d727a1bb5e3bd984"
>>>> PR = "r1"
>>>>
>>>> SRC_URI = "git://github.com/insop/schedtool-dl.git;protocol=git"
>>>> SRCREV = "${AUTOREV}"
>>>>
>>>> S = "${WORKDIR}/git"
>>>>
>>>> do_compile() {
>>>> oe_runmake
>>>> }
>>>>
>>>> do_install() {
>>>> oe_runmake install DESTDIR=${D}
>>>> }
>>
Re: [yocto] nested meta layers, how can/should it be done?
Hi, I am not an expert yet, but here is what I've recently done and I think this will give you some hints to what you want to achieve. I've made a new meta layer so that I can use custom kernel and add new programs on top of existing core-image-* targets. I used qemu targets for now, but I also plan to extend this to other bsp so that I can use on different targets. Here is my meta-dl layer - https://github.com/insop/meta-dl Here is the lab that I've referred, see recipes-kernel and recipes-tools dirs - https://www.yoctoproject.org/sites/yoctoproject.org/files/elc2013-kernel-lab.pdf Regards, Insop = Hi. I wish to write a custom meta layer that should add on-top of an existing bsp for eg. kernel and u-boot builds. But I want the custom layer to use .bbappend for some standard packages and also add some custom packages. My guess is that it might cause problems for the standard packages (since they are not unique) due to the MACHINE will be pointed out as the base bsp machine config, and the custom bsp will not define a machine on its own. Does this mean that I will have to define this new custom layer as a distro? I am worried that .bbappend stuff will never be executed since nothing will actually point to my custom layer for package recipes unless they are unique. What is the correct way to handle this use-case? Hans ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] A question on adding a new program to a new meta layer
Hi Bruce,
One more question on 3.8 kernel.
Is "meta/recipes-kernel/linux/linux-yocto_3.8.bb" added soon as well in 1.4?
I am using 1.4_M4.final now.
Thank you.
Insop
On Wed, Mar 6, 2013 at 9:05 PM, Insop Song wrote:
> Bruce,
>
> That's very good. I will bring linux-yocto-3.8 kernel to meta-dl.
> (https://github.com/insop/meta-dl/tree/linux-yocto-3.8)
>
> The purposes of meta-dl are the following three:
> 1. easy to use sched_deadline by providing recipes-kernel that includes
> - git url including github and from yocto-kernel
>
> 2. easy to test and validate sched_deadline with automated
> reproducible test suits
> - currently, rt-app and schedtool are included in meta-dl
> - will add test scripts
>
> 3. provide and test on different targets/bsps
> - will prepare and test on different targets (bsp)
>
> #1 is done as I've tested with kernel from github from Juri and
> yocto-kernel-3.8 that you've merged.
> #2 and #3 are in-progress.
>
> I've talked Juri the other day and gather information on testing
> methods and scripts so I will include this to meta-dl.
>
> I agree that it's good to coordinate the effort, so please feel free
> to let me know if you have any suggestion.
>
> Regards,
>
> Insop
>
> * updated kernel recipes
> @ -9,12 +9,15 @@ inherit kernel
>
> #SRCREV ="031d31cfaa1e0c00122bf52639e340353d3b8360"
> SRCREV ="${AUTOREV}"
> -KBRANCH = "sched-dl-V7"
> -SRC_URI =
> "git://github.com/insop/sched-deadline;protocol=git;branch=${KBRANCH}
> \
> +#KBRANCH = "sched-dl-V7"
> +#SRC_URI =
> "git://github.com/insop/sched-deadline;protocol=git;branch=${KBRANCH}
> \
> +# file://defconfig "
> +KBRANCH = "standard/edf"
> +SRC_URI =
> "git://git.yoctoproject.org/linux-yocto-3.8;protocol=git;branch=${KBRANCH}
> \
> file://defconfig "
>
> PV = "3.8"
> -PR = "dl7"
> +PR = "dl"
>
> KSRC ?= ""
> S = '${@base_conditional("KSRC", "", "${WORKDIR}/git", "${KSRC}", d)}'
>
> Thank you.
>
> Insop
>
> On Wed, Mar 6, 2013 at 8:00 PM, Bruce Ashfield
> wrote:
>> On 13-03-05 1:54 AM, Insop Song wrote:
>>>
>>> Hi,
>>>
>>> I am preparing a new meta layer for testing and promoting a
>>> sched_deadline scheduler, called "meta-dl". I am planning to add
>>> scheduler testing tools and different kernel versions as well.
>>> - http://insop.github.com/meta-dl/
>>
>>
>> FYI: I've already merged and staged sched_dl in linux-yocto_3.8:
>>
>> http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-3.8/log/?h=standard/edf
>>
>> I'll be supporting it there as well, so it makes sense to coordinate
>> our efforts around kernels, configurations and benchmarks.
>>
>> Juri and I talked about this @ ELC a few weeks ago (I've added
>> him to the cc as well), and rather than hiding sched_deadline
>> kernel support in a custom kernel layer, I'd like to try and get
>> more eyes on it via linux-yocto .. so if we can all coordinate our
>> efforts here, that would be much better.
>>
>> Cheers,
>>
>> Bruce
>>
>>>
>>> With the help of hands-on kernel lab (thank you Tom and Darren), I am
>>> able to make kernel with sched_deadline enabled.
>>>
>>>
>>> Now, I am having some trouble of adding testing tools to this meta-dl,
>>> and hope I can get some help from you.
>>>
>>> - problem: adding a new software into my meta-dl layer
>>>
>>> - symtom and questions?
>>> 1. bitbake core-image-minimal (normal image build) won't include the
>>> additional program that I listed in .bb file below
>>> 2. If I do "bitbake schedtool-dl -c install" it builds and install,
>>> but at "i586" location instead of my machine staging rootfs
>>> (dl-qemux86)
>>>
>>>
>>>
>>> - Here is my .bb file that pulls an additional program.
>>>
>>> https://github.com/insop/meta-dl/blob/sched-dl-V7/recipes-tools/schedtool-dl/schedtool-dl.bb
>>> ===
>>> DESCRIPTION = "schedtool-dl (scheduler test tool) for deadline scheduler"
>>> HOMEPAGE = "https://github.com/insop/schedtool-dl";
>>> SECTION = "base"
>>> LICENSE = "GPLv2"
>>> LIC_FILES_CHKSUM =
>>> "file://Makefile;endline=55;md5=e4b4e8ed9c2132e1d727a1bb5e3bd984"
>>> PR = "
Re: [yocto] A question on adding a new program to a new meta layer
Bruce,
That's very good. I will bring linux-yocto-3.8 kernel to meta-dl.
(https://github.com/insop/meta-dl/tree/linux-yocto-3.8)
The purposes of meta-dl are the following three:
1. easy to use sched_deadline by providing recipes-kernel that includes
- git url including github and from yocto-kernel
2. easy to test and validate sched_deadline with automated
reproducible test suits
- currently, rt-app and schedtool are included in meta-dl
- will add test scripts
3. provide and test on different targets/bsps
- will prepare and test on different targets (bsp)
#1 is done as I've tested with kernel from github from Juri and
yocto-kernel-3.8 that you've merged.
#2 and #3 are in-progress.
I've talked Juri the other day and gather information on testing
methods and scripts so I will include this to meta-dl.
I agree that it's good to coordinate the effort, so please feel free
to let me know if you have any suggestion.
Regards,
Insop
* updated kernel recipes
@ -9,12 +9,15 @@ inherit kernel
#SRCREV ="031d31cfaa1e0c00122bf52639e340353d3b8360"
SRCREV ="${AUTOREV}"
-KBRANCH = "sched-dl-V7"
-SRC_URI = "git://github.com/insop/sched-deadline;protocol=git;branch=${KBRANCH}
\
+#KBRANCH = "sched-dl-V7"
+#SRC_URI =
"git://github.com/insop/sched-deadline;protocol=git;branch=${KBRANCH}
\
+# file://defconfig "
+KBRANCH = "standard/edf"
+SRC_URI =
"git://git.yoctoproject.org/linux-yocto-3.8;protocol=git;branch=${KBRANCH}
\
file://defconfig "
PV = "3.8"
-PR = "dl7"
+PR = "dl"
KSRC ?= ""
S = '${@base_conditional("KSRC", "", "${WORKDIR}/git", "${KSRC}", d)}'
Thank you.
Insop
On Wed, Mar 6, 2013 at 8:00 PM, Bruce Ashfield
wrote:
> On 13-03-05 1:54 AM, Insop Song wrote:
>>
>> Hi,
>>
>> I am preparing a new meta layer for testing and promoting a
>> sched_deadline scheduler, called "meta-dl". I am planning to add
>> scheduler testing tools and different kernel versions as well.
>> - http://insop.github.com/meta-dl/
>
>
> FYI: I've already merged and staged sched_dl in linux-yocto_3.8:
>
> http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-3.8/log/?h=standard/edf
>
> I'll be supporting it there as well, so it makes sense to coordinate
> our efforts around kernels, configurations and benchmarks.
>
> Juri and I talked about this @ ELC a few weeks ago (I've added
> him to the cc as well), and rather than hiding sched_deadline
> kernel support in a custom kernel layer, I'd like to try and get
> more eyes on it via linux-yocto .. so if we can all coordinate our
> efforts here, that would be much better.
>
> Cheers,
>
> Bruce
>
>>
>> With the help of hands-on kernel lab (thank you Tom and Darren), I am
>> able to make kernel with sched_deadline enabled.
>>
>>
>> Now, I am having some trouble of adding testing tools to this meta-dl,
>> and hope I can get some help from you.
>>
>> - problem: adding a new software into my meta-dl layer
>>
>> - symtom and questions?
>> 1. bitbake core-image-minimal (normal image build) won't include the
>> additional program that I listed in .bb file below
>> 2. If I do "bitbake schedtool-dl -c install" it builds and install,
>> but at "i586" location instead of my machine staging rootfs
>> (dl-qemux86)
>>
>>
>>
>> - Here is my .bb file that pulls an additional program.
>>
>> https://github.com/insop/meta-dl/blob/sched-dl-V7/recipes-tools/schedtool-dl/schedtool-dl.bb
>> ===
>> DESCRIPTION = "schedtool-dl (scheduler test tool) for deadline scheduler"
>> HOMEPAGE = "https://github.com/insop/schedtool-dl";
>> SECTION = "base"
>> LICENSE = "GPLv2"
>> LIC_FILES_CHKSUM =
>> "file://Makefile;endline=55;md5=e4b4e8ed9c2132e1d727a1bb5e3bd984"
>> PR = "r1"
>>
>> SRC_URI = "git://github.com/insop/schedtool-dl.git;protocol=git"
>> SRCREV = "${AUTOREV}"
>>
>> S = "${WORKDIR}/git"
>>
>> do_compile() {
>> oe_runmake
>> }
>>
>> do_install() {
>> oe_runmake install DESTDIR=${D}
>> }
>>
>> PARALLEL_MAKE = ""
>>
>> BBCLASSEXTEND = "native"
>>
>> COMPATIBLE_MACHINE_dl-qemux86 = "dl-qemux86"
>>
>>
>>
>> - I've updated my conf/layer.conf file to include above file
>> https://github.com/insop/meta-dl/blob/sched-dl-V7/conf/layer.conf
>&g
Re: [yocto] A question on adding a new program to a new meta layer
Hi all,
I've done some more work and figured out what was to be changed to
include a new program to my meta-dl.
This is the change, please let me know if you have any comment.
https://github.com/insop/meta-dl/commit/6f7c4dc9b66e38a1fedb4a9fd80d644d3f37aced
Thank you,
Insop
On Mon, Mar 4, 2013 at 8:04 PM, Insop Song wrote:
> Hi,
>
> I am preparing a new meta layer for testing and promoting a
> sched_deadline scheduler, called "meta-dl". I am planning to add
> scheduler testing tools and different kernel versions as well.
> - http://insop.github.com/meta-dl/
>
> With the help of hands-on kernel lab (thank you Tom and Darren), I am
> able to make kernel with sched_deadline enabled.
>
>
> Now, I am having some trouble of adding testing tools to this meta-dl,
> and hope I can get some help from you.
>
> - problem: adding a new software into my meta-dl layer
>
> - symtom and questions?
> 1. bitbake core-image-minimal (normal image build) won't include the
> additional program that I listed in .bb file below
> 2. If I do "bitbake schedtool-dl -c install" it builds and install,
> but at "i586" location instead of my machine staging rootfs
> (dl-qemux86)
>
>
>
> - Here is my .bb file that pulls an additional program.
> https://github.com/insop/meta-dl/blob/sched-dl-V7/recipes-tools/schedtool-dl/schedtool-dl.bb
> ===
> DESCRIPTION = "schedtool-dl (scheduler test tool) for deadline scheduler"
> HOMEPAGE = "https://github.com/insop/schedtool-dl";
> SECTION = "base"
> LICENSE = "GPLv2"
> LIC_FILES_CHKSUM =
> "file://Makefile;endline=55;md5=e4b4e8ed9c2132e1d727a1bb5e3bd984"
> PR = "r1"
>
> SRC_URI = "git://github.com/insop/schedtool-dl.git;protocol=git"
> SRCREV = "${AUTOREV}"
>
> S = "${WORKDIR}/git"
>
> do_compile() {
> oe_runmake
> }
>
> do_install() {
> oe_runmake install DESTDIR=${D}
> }
>
> PARALLEL_MAKE = ""
>
> BBCLASSEXTEND = "native"
>
> COMPATIBLE_MACHINE_dl-qemux86 = "dl-qemux86"
>
>
>
> - I've updated my conf/layer.conf file to include above file
> https://github.com/insop/meta-dl/blob/sched-dl-V7/conf/layer.conf
>
> # We have a conf and classes directory, add to BBPATH
> BBPATH := "${BBPATH}:${LAYERDIR}"
>
> # We have a recipes directory, add to BBFILES
> BBFILES := "${BBFILES} ${LAYERDIR}/recipes-*/*/*.bb \
> ${LAYERDIR}/recipes-*/*/*.bbappend"
>
> BBFILE_COLLECTIONS += "dl-qemux86"
> BBFILE_PATTERN_dl-qemux86 := "^${LAYERDIR}/"
> BBFILE_PRIORITY_dl-qemux86 = "6"
> =
>
>
>
> Thank you.
>
> Regards,
>
> Insop
>
>
> - ref:
> 1. sched_deadline:
> https://events.linuxfoundation.org/events/linuxcon-europe/song
> 2. sched_deadline:
> http://events.linuxfoundation.org/images/stories/slides/elc2013_kobayashi.pdf?a
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] A question on adding a new program to a new meta layer
Hi,
I am preparing a new meta layer for testing and promoting a
sched_deadline scheduler, called "meta-dl". I am planning to add
scheduler testing tools and different kernel versions as well.
- http://insop.github.com/meta-dl/
With the help of hands-on kernel lab (thank you Tom and Darren), I am
able to make kernel with sched_deadline enabled.
Now, I am having some trouble of adding testing tools to this meta-dl,
and hope I can get some help from you.
- problem: adding a new software into my meta-dl layer
- symtom and questions?
1. bitbake core-image-minimal (normal image build) won't include the
additional program that I listed in .bb file below
2. If I do "bitbake schedtool-dl -c install" it builds and install,
but at "i586" location instead of my machine staging rootfs
(dl-qemux86)
- Here is my .bb file that pulls an additional program.
https://github.com/insop/meta-dl/blob/sched-dl-V7/recipes-tools/schedtool-dl/schedtool-dl.bb
===
DESCRIPTION = "schedtool-dl (scheduler test tool) for deadline scheduler"
HOMEPAGE = "https://github.com/insop/schedtool-dl";
SECTION = "base"
LICENSE = "GPLv2"
LIC_FILES_CHKSUM =
"file://Makefile;endline=55;md5=e4b4e8ed9c2132e1d727a1bb5e3bd984"
PR = "r1"
SRC_URI = "git://github.com/insop/schedtool-dl.git;protocol=git"
SRCREV = "${AUTOREV}"
S = "${WORKDIR}/git"
do_compile() {
oe_runmake
}
do_install() {
oe_runmake install DESTDIR=${D}
}
PARALLEL_MAKE = ""
BBCLASSEXTEND = "native"
COMPATIBLE_MACHINE_dl-qemux86 = "dl-qemux86"
- I've updated my conf/layer.conf file to include above file
https://github.com/insop/meta-dl/blob/sched-dl-V7/conf/layer.conf
# We have a conf and classes directory, add to BBPATH
BBPATH := "${BBPATH}:${LAYERDIR}"
# We have a recipes directory, add to BBFILES
BBFILES := "${BBFILES} ${LAYERDIR}/recipes-*/*/*.bb \
${LAYERDIR}/recipes-*/*/*.bbappend"
BBFILE_COLLECTIONS += "dl-qemux86"
BBFILE_PATTERN_dl-qemux86 := "^${LAYERDIR}/"
BBFILE_PRIORITY_dl-qemux86 = "6"
=
Thank you.
Regards,
Insop
- ref:
1. sched_deadline:
https://events.linuxfoundation.org/events/linuxcon-europe/song
2. sched_deadline:
http://events.linuxfoundation.org/images/stories/slides/elc2013_kobayashi.pdf?a
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] qemu not getting dhcp question.
Hi all, I've built a new meta layer image based on core-image-minimal and core-image-sato. After the successful build, whey I run "runqemu" with the image, my qemu image won't get a dhcp IP. I can manually assign IP after the boot up. Does anyone know why or which log to look at? Here is the message from qemu - Configuring network interfaces... udhcpc (v1.20.2) started Sending discover... Sending discover... Sending discover... No lease, failing [ 20.280668] rc (824) used greatest stack depth: 5632 bytes left INIT: Entering runlevel: 5 Starting syslogd/klogd: done Stopping Bootlog daemon: bootlogd. -- Here is the host side message -- $ runqemu tmp/deploy/images/bzImage-3.8-dl7-dl-qemux86-20130303034712.bin tmp/deploy/images/core-image-minimal-dev-dl-qemux86-20130306045344.rootfs.ext3 Set MACHINE to [qemux86] based on kernel [tmp/deploy/images/bzImage-3.8-dl7-dl-qemux86-20130303034712.bin] Continuing with the following parameters: KERNEL: [tmp/deploy/images/bzImage-3.8-dl7-dl-qemux86-20130303034712.bin] ROOTFS: [tmp/deploy/images/core-image-minimal-dev-dl-qemux86-20130306045344.rootfs.ext3] FSTYPE: [ext3] Setting up tap interface under sudo Acquiring lockfile for tap0... WARNING: distccd not present, no distcc support loaded. Running qemu-system-i386... /home/insop/mybuilds/dl/tmp/sysroots/x86_64-linux/usr/bin/qemu-system-i386 -kernel tmp/deploy/images/bzImage-3.8-dl7-dl-qemux86-20130303034712.bin -net nic,vlan=0 -net tap,vlan=0,ifname=tap0,script=no,downscript=no -hda tmp/deploy/images/core-image-minimal-dev-dl-qemux86-20130306045344.rootfs.ext3 -show-cursor -usb -usbdevice wacom-tablet -vga vmware -no-reboot -m 128 --append "vga=0 root=/dev/hda rw mem=128M ip=192.168.7.2::192.168.7.1:255.255.255.0 oprofile.timer=1 " - Thank you, Insop ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
