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
<bruce.ashfi...@windriver.com> 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<insop.s...@gmail.com> 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
<bruce.ashfi...@windriver.com> 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
====
# 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 mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
