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 me
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
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-
inux-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)}'
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-
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 p
;>
>> PV = "3.8"
>> -PR = "dl7"
>> +PR = "dl"
>>
>> KSRC ?= ""
>> S = '${@base_conditional("KSRC", "", "${WORKDIR}/git", "${KSRC}", d)}'
>>
>> Thank you.
>>
>
>
> 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-yoct
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 mas
>>
>> 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 yoc
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-d
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-
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
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
&
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/
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.
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 g
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 gi
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 m
pes-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
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
>> -
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
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-
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
sepa
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
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
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
---
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
in
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 gener
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 d
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
---
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
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
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
0572 (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,
>
>
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
>
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 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:/
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
>> +++
&g
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-re
t-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 @@
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
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
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 a
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
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
&g
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 informa
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 an
- 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
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 a
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 =
gt; 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 upstr
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 "
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 st
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 ag
ments.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
>> "H
gt;> 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
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
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
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 ."
---
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 examp
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
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:
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 m
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 sp
/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
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
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
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
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/pixe
rom 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 |
71 matches
Mail list logo
